[CentOS] saslauthd for sendmail SMTP relay

2008-05-25 Thread Bernd Bartmann
Hi, I'm running a Centos 5.1 server that uses saslauthd to allow sendmail SMTP relaying for some clients. saslauthd is configured to use method shadow to lookup the username / password directly from /etc/shadow. This setup has been working for several month now, but is broken since last Monday. I

Re: [CentOS] saslauthd for sendmail SMTP relay

2008-05-25 Thread Ian Blackwell
Bernd Bartmann wrote: /var/log/maillog: AUTH failure (LOGIN): authentication failure (-13) SASL(-13): authentication failure: checkpass failed /var/log/messages: saslauthd[3665]: do_auth : auth failure: [user=username] [service=smtp] [realm=] [mech=shadow] [reason=Unknown] Does someone

Re: [CentOS] saslauthd for sendmail SMTP relay

2008-05-25 Thread Bernd Bartmann
On Sun, May 25, 2008 at 11:42 AM, Ian Blackwell wrote: Bernd Bartmann wrote: /var/log/maillog: AUTH failure (LOGIN): authentication failure (-13) SASL(-13): authentication failure: checkpass failed /var/log/messages: saslauthd[3665]: do_auth : auth failure: [user=username]

Re: [CentOS] saslauthd for sendmail SMTP relay

2008-05-25 Thread Ian Blackwell
Bernd Bartmann wrote: Thanks Ian. That's indeed the reason. service saslauthd status gives saslauthd dead but subsys locked. Now, what could be the reason why saslauthd was not running any more? cu, Bernd. ___ CentOS mailing list CentOS@centos.org

Re: [CentOS] saslauthd for sendmail SMTP relay

2008-05-25 Thread Bernd Bartmann
On Sun, May 25, 2008 at 2:42 PM, Ian Blackwell wrote: Bernd Bartmann wrote: Thanks Ian. That's indeed the reason. service saslauthd status gives saslauthd dead but subsys locked. Now, what could be the reason why saslauthd was not running any more? Hard to say without seeing the logs. Does

Re: [CentOS] saslauthd for sendmail SMTP relay

2008-05-25 Thread Ian Blackwell
Bernd Bartmann wrote: It did start without any problems. Looks like I found the cause. From the logs I see that someone tried a brute force attach on the SMTP relay with several username / password combinations. Then one of the attempts lead to a segfault of saslauth. Which probably means that