Hi, this is Debian issue #299743, with its history available on http://bugs.debian.org/299743. Some preliminary chit-chat about the configuration being in use is in http://bugs.debian.org/299732.
Without having too much clue about SASL, I understand the reporter that a SASL client is able to specify which mechanisms to use, and exim doesn't specify that list, meaning that it uses "all", which can clutter up the logs of the SASL server. The issue report for #299743 has a patch. Please consider this patch. Greetings Marc ----- Forwarded message from Juergen Kreileder <[EMAIL PROTECTED]> ----- > From: Juergen Kreileder <[EMAIL PROTECTED]> > Subject: exim4: Only try configured mechs in cyrus_sasl authenticator > To: Debian Bug Tracking System <[EMAIL PROTECTED]> > Date: Wed, 16 Mar 2005 05:16:44 +0100 > User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) > > Package: exim4 > Version: 4.50-4 > Severity: normal > > I've configured cyrus_sasl like described in #299732, ie. I'm using > three mechs: PLAIN, LOGIN and CRAM-MD5. > > But something is trying to use OTP. /var/log/auth.log get's flooded with: > > ,---- > | Mar 16 04:33:47 server exim4: OTP unavailable because can't read/write key > database /etc/opiekeys: No such file or directory > | Mar 16 04:33:47 server last message repeated 2 times > | Mar 16 04:41:17 server send-mail: OTP unavailable because can't read/write > key database /etc/opiekeys: No such file or directory > | Mar 16 04:41:17 server last message repeated 2 times > `---- > > I think the authenticator should only try mechs which are actually > specified in the configuration. > > > Juergen > > -- > Juergen Kreileder, Blackdown Java-Linux Team > http://blog.blackdown.de/ > > ----- End forwarded message ----- -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
