Loading ...
Sorry, an error occurred while loading the content.

Re: Postfix + stunnel SMTPS = address rewriting issue

Expand Messages
  • Jack Browning
    ... Live and learn. Since the fix suggested earlier in this thread -- keying the remote username:password entries to the users local addresses -- produces the
    Message 1 of 7 , Jun 1, 2010
    • 0 Attachment
      On Tue, Jun 1, 2010 at 6:17 PM, Wietse Venema <wietse@...> wrote:
      > Jack Browning:

      >> No address rewriting is occurring even though Postfix is invoking its
      >> SMTP client to deliver the mail to the remote host, and my generic map
      >> (after postmap and a reload) contains an entry like this:
      >>
      >> zzzzzz@...    xxxxxx@...
      >
      > Sorry this is very incorrect.
      >
      > The from= line, logged by the queue manager, is not subject to SMTP
      > generic mapping. It never was, and it never will.
      >
      > SMTP generic mapping is implemented in the Postfix SMTP client.
      > This mapping is done only for information that is sent over the
      > network.  This also explains why:
      >
      > 1) SMTP generic mapping has no effect on SASL password lookup.  It
      > never did, and it never will.
      >
      > 2) SMTP generic mapping does not change with the destination host.
      > It never did, and it never will.
      >
      >        Wietse

      Live and learn. Since the fix suggested earlier in this thread --
      keying the remote username:password entries to the users' local
      addresses -- produces the desired result, the issue didn't involve
      generic mapping at all. No generic mapping was done until the message
      was actually sent to the remote server, and the message was not being
      sent because the mis-keyed password lookup table resulted in bad (or
      no) credentials being presented to the remote server, which rejected
      the authentication attempt and terminated the session before the
      message itself was transmitted. No transmission = no rewriting.

      Anyway, that's my story, and I'm sticking to it.

      JEB
    • Wietse Venema
      ... Are you sticking with your subject line Postfix + stunnel SMTPS = address rewriting issue ? All I have seen sofar is that sender-dependent SASL password
      Message 2 of 7 , Jun 2, 2010
      • 0 Attachment
        Jack Browning:
        > Live and learn. Since the fix suggested earlier in this thread --
        > keying the remote username:password entries to the users' local
        > addresses -- produces the desired result, the issue didn't involve
        > generic mapping at all. No generic mapping was done until the message
        > was actually sent to the remote server, and the message was not being
        > sent because the mis-keyed password lookup table resulted in bad (or
        > no) credentials being presented to the remote server, which rejected
        > the authentication attempt and terminated the session before the
        > message itself was transmitted. No transmission = no rewriting.
        >
        > Anyway, that's my story, and I'm sticking to it.

        Are you sticking with your subject line "Postfix + stunnel SMTPS
        = address rewriting issue"? All I have seen sofar is that
        sender-dependent SASL password lookups are working as promised.

        Wietse
      Your message has been successfully submitted and would be delivered to recipients shortly.