On Sun, Mar 17, 2019 at 10:40:23PM +1100, li...@sbt.net.au wrote:
> Mar 17 22:10:53 postfix/smtpd[11975]: warning:
> 111-222-333-444.static.tpgi.com.au[111.222.333.444]: SASL LOGIN
> authentication failed: UGFzc3dvcmQ6
Try to avoid pasting SASL-generated base64-encoded strings from
verbose logs, these often contain easily decoded passwords. In
this case "UGFzc3dvcmQ6" just decodes to "Password:", which I hope
is not the actual password for the account.
> Mar 17 22:14:42 postfix/smtpd[12089]: 5425745329A0:
> client=111-222-333-444.static.tpgi.com.au 111.222.333.444],
> sasl_method=PLAIN, sasl_username=m...@tld.com.au
> Mar 17 22:14:43 amavis[11177]: (11177-17) Passed CLEAN {RelayedOutbound},
> ORIGINATING LOCAL [111.222.333.444]:54608 [111.222.333.444] <m...@tld.com>
> -> <dddd...@yahoo.com>, Queue-ID: 5425745329A0, Message-ID:
> <7252a376-030e-0a85-cede-d204206bf...@autopack.com>, mail_id:
> WUkk9VvorFcd, Hits: 0.076, size: 1111, queued_as: BAE5645329A6, 1303 ms
The SASL login name is "m...@tld.com.au". The envelope
sender email address is: "m...@tld.com".
> the sasl username is 'm...@tld.com.au' BUT on next line they have
> 'm...@tld.com' (both domains are valid, tld.com as well as tld.com.au) -
> could that be a problem?
No. The SASL login name need not be, and often isn't, the same as
the envelope sender address.
--
Viktor.
