In contrast to dbmail-imapd, a child process of dbmail-pop3d exits on
signal 6 (SIGABRT) if the client unexpectedly drops the connection.
Is this behavior intended?
This is a FreeBSD machine. Dime to dollar the person is using FreeBSD
5.X and has their malloc(3) flags setup to abort(3) on double
free(3)'s, etc.
http://www.freebsd.org/cgi/man.cgi?query=malloc
FreeBSD does this as a debugging aid and as a way to prevent security
problems from programs that aren't handling their memory management
correctly. As a workaround, try running:
# ln -sf '' /etc/malloc.conf
Or, upgrade to a release that's 5.3 or later, where malloc(3)'s flags
have been turned off.
dbmail/pop3d[8151]: PerformChildTask(): incoming connection from [...]
/boot/kernel/kernel: pid 8151 (dbmail-pop3d), uid 65534: exited on
signal 6
^^^^^^^^^^^^^^^^^^^
That was the giveaway for the OS. -sc
--
Sean Chittenden
