Date: Fri, 01 Jun 2007 10:05:32 -0500 From: Paul Schmehl <pauls@utdallas.edu> To: freebsd-questions@freebsd.org Subject: Re: Wierd postfix/cyrus SASL error... Message-ID: <57A2A306011B7344B4DDE55C@utd59514.utdallas.edu> In-Reply-To: <294439d20706010225p2bfff3ebp41019dcb7b311ad2@mail.gmail.com> References: <294439d20705310218q5a8f65c0jb6b30c6dfc9a51a7@mail.gmail.com> <4215074055BD1BFDD24D2509@utd59514.utdallas.edu> <294439d20706010225p2bfff3ebp41019dcb7b311ad2@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
--On Friday, June 01, 2007 14:55:23 +0530 Amarendra Godbole <amarendra.godbole@gmail.com> wrote: > > Okay, after a lot of digging around, I got the error. Somehow > something messed up during the portupgrade, and postfix started > negotiating GSSAPI authentication with the smtp server. Since GSSAPI > needs krb (kerberos) support, which was not configured, the auth > failed. Adding the following lines to main.cf solved the problem, and > postfix now happily chugs along: > > 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. > Since Postfix is such a critical app, you might want to consider presetting the config you want in /usr/local/etc/pkgtools.conf to avoid surprises during portupgrade. -- Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57A2A306011B7344B4DDE55C>