The following bug has been SUBMITTED.
==
http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=126
==
Reported By:Wolfram
Assigned To
Sounds like you're confusing the MTA (sendmail/postfix) with the
storage/pop3/imap tool, in this case, DBMail. DBMail works with both sendmail
and postfix.
To make things even more confusing, there is a sendmail program that is
installed with sendmail (the MTA). This is utilized by PHP to send
Sean Chittenden <[EMAIL PROTECTED]> said:
>>> Heh, my logs are *filled* with crashed dbmail backends at the
>>> moment.
>>> In the last week, things have gotten worse in that regard, though I
>>> haven't had the time to figure out why. -sc
>>
>> So nothing to worry about, eh? ;-)
>
> That's what
SIGABRT is not handled explicitely by the code. No handler is
installed. This could be os-specific. What are
you running on?
FreeBSD 5.3 Stable, dbmail_2_0_branch cvs checkout a few days
before the 2.0.1 release. Sidenote: I replaced the default
dbmail CFLAGS "-g -O2" with "-O -pipe", but didn't
> >> SIGABRT is not handled explicitely by the code. No handler is
> >> installed. This could be os-specific. What are
> >> you running on?
> > FreeBSD 5.3 Stable, dbmail_2_0_branch cvs checkout a few days
> > before the 2.0.1 release. Sidenote: I replaced the default
> > dbmail CFLAGS "-g -O2" wit
SIGABRT is not handled explicitely by the code. No handler is
installed. This could be os-specific. What are
you running on?
FreeBSD 5.3 Stable, dbmail_2_0_branch cvs checkout a few days
before the 2.0.1 release. Sidenote: I replaced the default
dbmail CFLAGS "-g -O2" with "-O -pipe", but didn't
> SIGABRT is not handled explicitely by the code. No handler is
> installed. This could be os-specific. What are
> you running on?
FreeBSD 5.3 Stable, dbmail_2_0_branch cvs checkout a few days
before the 2.0.1 release. Sidenote: I replaced the default
dbmail CFLAGS "-g -O2" with "-O -pipe", bu
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 doub
Signal handling is identical for pop3d,imapd,lmtpd afaik. They all share the same signalhandling code from
server.c and serverchild.c
SIGABRT is not handled explicitely by the code. No handler is installed. This could be os-specific. What are
you running on? I've never seen a kernel logline lik
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?
syslog messages:
> dbmail/pop3d[8151]: PerformChildTask(): incoming connection from [...]
> /boot/kernel/kernel: pid 8151 (dbmail-p
10 matches
Mail list logo
