On 1/29/2014 4:55 PM, Viktor Dukhovni wrote: > On Wed, Jan 29, 2014 at 04:14:16PM -0500, Dennis Putnam wrote: > >> I have made yet another discovery. Perhaps this is the problem. When the >> EHLO command is send, should there not be the line: >> >> 250-AUTH LOGIN DIGEST-MD5 CRAM-MD5 PLAIN > To repeat what I posted previously: > > Save everyone some time and post unedited output of: > > postconf -n smtp_sasl_auth_enable \ > smtp_sasl_mechanism_filter smtp_sasl_password_maps \ > smtp_sasl_security_options smtp_sasl_tls_security_options \ > smtp_sasl_tls_verified_security_options smtp_sasl_type | cat -ev > > Perhaps you're not configured to use SASL without TLS, and IIRC you > don't seem to have used TLS. > > You should also post the complete output of "postconf -n". The > reason I asked for the above variant is that it less likely to > craete misleading output when you cut/paste the output and change > how lines are folded. > Thanks for the reply. Keep in mind this is not a new installation. This has been working until recently and still works for servers requiring authentication other then smtp.att.yahoo.com. Clearly something must have changed for that particular server.
I thought I posted postconf output earlier but here it is again: $ postconf -n smtp_sasl_auth_enable ... smtp_sasl_auth_enable = yes$ smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd$ smtp_sasl_security_options = $ TLS is indeed set via $ postconf -n smtp_tls_policy_maps smtp_tls_policy_maps = hash:/etc/postfix/tls_policy The entry in that file is set to: smtp.att.yahoo.com may
signature.asc
Description: OpenPGP digital signature
