ok, if i can impose on the list yet again (for something that
doesn't appear to be something *i* did for a change), a fully-updated
lenny mail server suddenly started to generate the above error when
its corporate users try to send email from home through that mail
server.
i've been assured that that was working for a long, long time and
only went south just over a week ago. and since i've also been
assured that it affected everyone simultaneously, i'm concluding that
it's a server issue.
the system is using postfix and, to the best of my knowledge, *i*
wasn't messing with the mail system when it broke so i'm guessing
someone else was doing some configuration. i've found a number of web
pages referring to that error and i'm perusing them right now, but if
anyone has any hints, i'm listening.
a couple more things. i have a backup copy of the entire /etc
directory from before the breakage so i can quickly diff any relevant
files (/etc/postfix/main.cf appears to be unchanged). also, any
attempts to try to email from outside the internal network *appears*
to coincide with the following messages in /var/log/mail.warn:
Sep 15 23:12:38 main postfix/smtpd[20633]: warning: SASL
authentication failure: cannot connect to saslauthd server: No such
file or directory
Sep 15 23:12:38 main postfix/smtpd[20633]: warning: SASL
authentication failure: Password verification failed
Sep 15 23:12:38 main postfix/smtpd[20633]: warning:
unknown[24.114.232.37]: SASL PLAIN authentication failed: generic
failure
but i've verified that saslauthd is running. so ... is there
something trivially obvious that would have changed on the server side
that could cause this? i'll take everyone's word here that they
haven't messed with their t-bird settings, so i'm looking at what on
the server might have been tweaked. thanks.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
