From time to time I have 2 machines that have a segfault in the saslauthd process and of course no further email can be sent.

Running

/etc/rc.d/rcsaslauthd stop
/etc/rc.d/rcsaslauthd start

solves the issue for the next few days or weeks. One machine is 13.1 and the other is 13.0.

Here is an example of the issue:

Aug 27 20:30:56 mail kernel: saslauthd[3248]: segfault at ffffffffe7aee1a0 ip 00007fade73af790 sp 00007ffffcf8def8 error 4 in libc-2.9.so[7fade732f000+167000]
Aug 27 20:31:03 mail kernel: saslauthd[3249]: segfault at ffffffffe7aee1a0 ip 00007fade73af790 sp 00007ffffcf8def8 error 4 in libc-2.9.so[7fade732f000+167000]
Aug 27 20:31:11 mail kernel: saslauthd[3250]: segfault at ffffffffe7aee1a0 ip 00007fade73af790 sp 00007ffffcf8def8 error 4 in libc-2.9.so[7fade732f000+167000]
Aug 27 20:31:19 mail kernel: saslauthd[3247]: segfault at ffffffffe7aee1a0 ip 00007fade73af790 sp 00007ffffcf8def8 error 4 in libc-2.9.so[7fade732f000+167000]
Aug 27 20:31:26 mail kernel: saslauthd[3251]: segfault at ffffffffe7aee1a0 ip 00007fade73af790 sp 00007ffffcf8def8 error 4 in libc-2.9.so[7fade732f000+167000]

One machine has all patches applied while the other does not have the latest kernel update.

Any ideas welcome.

The problem appears to be quite regular now - I have 2 x 13.37 machines doing the same thing. While I can use monit to monitor and restart, I'd like to find the underlying cause. Any help appreciated.

I had the same problem in Slackware64 14.0.

saslauthd[6689]: segfault at ffffffffbee8d1e0 ip 00007f4dbe7042e1 sp 00007fff56639de8 error 4 in libc-2.15.so[7f4dbe67c000+1b5000]

This is saslauthd 2.1.23 which comes with Slackware64 14.1

After downloading and compiling saslauthd 2.1.25 the problem was solved.

Yes I have the issue across all versions from 12.0 to 13.37 - I've resorted to using monit to auto-restart the service.

saslauthd 2.1.25 has worked for several days on my server. I downloaded cyrus-sasl-2.1.25.tar.gz and compiled it (configure and make). Then I just replaced the binary file saslauthd (located in the saslauthd directory).

Oh, it's probably not the way to do it... The ideal solution would be the Slackware team upgraded saslauthd.

Anyway... You could download the cyrus-sasl-2.1.23-x86_64-4 (in case you're running Slackware64 14.0) source code from slackware.com and check the build script. It's pretty easy to understand. Then build cyrus-sasl-2.1.25 the same way.