Walt Shekrota: > On Friday 25 March 2011 11:32:01 Brian Evans - Postfix List wrote: > > > smtp.frontier.com wshekro...@frontier.com:xxxxxxxxx > > > relayhost = 199.224.64.207 > > > > smtp.frontier.com != 199.224.64.207 > > > > As documented, they MUST be equal > > yes I read that last night and fixed it. Something I alternatively read > suggested an IP address be used. That is the problem with the internet you > have to avoid reading too many other folks posts they are not always useful. > They are now exactly the same 'smtp.frontier.com'
Instead of scraping random blogs, why not go to the auhtoritative source: http://www.postfix.org/SASL_README.html#client_sasl_enable Enabling SASL authentication in the Postfix SMTP/LMTP client This section shows a typical scenario where the Postfix SMTP client sends all messages via a mail gateway server that requires SASL authentication. Trouble solving tips: * If your SASL logins fail with "SASL authentication failure: No worthy mechs found" in the mail logfile, then see the section "Postfix SMTP/LMTP client policy - SASL mechanism properties". * For a solution to a more obscure class of SASL authentication failures, see "Postfix SMTP/LMTP client policy - SASL mechanism names". To make the example more readable we introduce it in two parts. The first part takes care of the basic configuration, while the second part sets up the username/password information. /etc/postfix/main.cf: smtp_sasl_auth_enable = yes relayhost = [mail.isp.example] # Alternative form: # relayhost = [mail.isp.example]:submission smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd * The smtp_sasl_auth_enable setting enables client-side authentication. We will configure the client's username and password information in the second part of the example. * The relayhost setting forces the Postfix SMTP to send all remote messages to the specified mail server instead of trying to deliver them directly to their destination. * In the relayhost setting, the "[" and "]" prevent the Postfix SMTP client from looking up MX (mail exchanger) records for the enclosed name. * The relayhost destination may also specify a non-default TCP port. For example, the alternative form [mail.isp.example]:submission tells Postfix to connect to TCP network port 587, which is reserved for email client applications. * The Postfix SMTP client is compatible with SMTP servers that use the non-standard "AUTH=method...." syntax in response to the EHLO command; this requires no additional Postfix client configuration. * The Postfix SMTP client does not support the obsolete "wrappermode" protocol, which uses TCP port 465 on the SMTP server. See TLS_README for a solution that uses the stunnel command. * With the smtp_sasl_password_maps parameter, we configure the Postfix SMTP client to send username and password information to the mail gateway server. As discussed in the next section, the Postfix SMTP client supports multiple ISP accounts. For this reason the username and password are stored in a table that contains one username/password combination for each mail gateway server. /etc/postfix/sasl_passwd: # destination credentials [mail.isp.example] username:password # Alternative form: # [mail.isp.example]:submission username:password Important Keep the SASL client password file in /etc/postfix, and make the file read+write only for root to protect the username/password combinations against other users. The Postfix SMTP client will still be able to read the SASL client passwords. It opens the file as user root before it drops privileges, and before entering an optional chroot jail. * Use the postmap command whenever you change the /etc/postfix/sasl_passwd file. * If you specify the "[" and "]" in the relayhost destination, then you must use the same form in the smtp_sasl_password_maps file. * If you specify a non-default TCP Port (such as ":submission" or ":587") in the relayhost destination, then you must use the same form in the smtp_sasl_password_maps file.
