Stroller wrote: > Hi Brian, > > I'll comment on your remarks regarding reject_unverified_sender later, > when I've had the opportunity to read / test thoroughly. > > > On 21 Oct 2008, at 17:24, Brian Evans - Postfix List wrote: >> ... >> BTW.. btopenworld.com use yahoo MXs: >> [EMAIL PROTECTED] ~ $ host btopenworld.com >> btopenworld.com has address 213.121.143.193 >> btopenworld.com mail is handled by 30 mx2.bt.mail.yahoo.com. >> btopenworld.com mail is handled by 20 mx1.bt.mail.yahoo.com. >> >> The original message issue, that caused the bounce, can be solved by >> using SASL on the smtp client to begin with. >> See http://www.postfix.org/SASL_README.html#client_sasl for details. > > > Unfortunately there's more to it than this. > > SASL is already configured on the host: > > $ sudo grep btopenworld.com /etc/postfix/* > /etc/postfix/main.cf:relayhost = [mail.btopenworld.com] > /etc/postfix/sasl_passwd:mail.btopenworld.com > [EMAIL PROTECTED]:password > Binary file /etc/postfix/sasl_passwd.db matches > $ > mail.btopenworld.com does not necessarily match [mail.btopenworld.com] >From the docs: # The "[" and "]" prevent Postfix from looking up the MX (mail exchanger) records for the enclosed name. If you use this form in main.cf, then you must use the same form also in the smtp_sasl_password_maps file. #
What happens if you make them match with the brackets? BTW, Postfix 2.1 is quite old. You may consider moving to the latest version 2.5.5 (currently) Brian
