Possibly something in the SASL arena... like maybe the gssapi library for SASL was installed during the portupgrade... SASL *favours* GSSAPI above anything else, because GSSAPI is the most secure password protocol available, as far as I'm aware. On Fri, June 1, 2007 10:27, Amarendra Godbole wrote: > On 5/31/07, Patrick Ben Koetter <p@xxxxxxxxxxxxxxxx> wrote: > >> Use smtp_sasl_mechanism_filter to filter GSSAPI away. >> > [...] > > > That did not work, and postfix came back saying no valid auth > mechanisms found. But these entries in main.cf did work: > > smtp_sasl_security_options = noanonymous, noplaintext > smtp_sasl_mechanism_filter = login, ntlm > > Now it negotiates login or ntlm with the server, and the auth works > fine. Thanks for all the help. My next stop is to figure out *what* changed > during portupgrade (as my postfix config files were the same as before) that > created this issue. > > -Amarendra > > >
