amavisd-new crashing

Eric Sheesley esheesle at shadowlair.com
Thu Sep 10 23:23:29 UTC 2009


Here is one sample of the log(level 5 logging on).  not very descriptive
about the problem, at least i don't see it.

Sep 10 19:00:07 rogue postfix/smtpd[77645]: connect from
tx2ehsobe003.messaging.microsoft.com[65.55.88.13]
Sep 10 19:00:07 rogue postfix/smtpd[77645]: NOQUEUE:
client=tx2ehsobe003.messaging.microsoft.com[65.55.88.13]
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) ESMTP::10024
/var/amavis/tmp/amavis-20090910T190007-77712: <fromaddr at fromaddr.com> ->
<myaddr at shadowlair.com> SIZE=7072 BODY=7BIT Received: from
rogue.shadowlair.com ([127.0.0.1]) by localhost (rogue.shadowlair.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP for
<esheesle at shadowlair.com>; Thu, 10 Sep 2009 19:00:07 -0400 (EDT)
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) Checking: SukXX+6vDV2U
[65.55.88.13] <fromaddr at fromaddr.com> -> <myaddr at shadowlair.com>
Sep 10 19:00:08 rogue amavis[77712]: (77712-01) p001 1 Content-Type:
text/plain, size: 3607 B, name:
Sep 10 19:00:08 rogue postfix/smtpd[77645]: warning: lost connection
with proxy 127.0.0.1:10024
Sep 10 19:00:08 rogue amavis[78041]: TIMING [total 5 ms] - bdb-open: 5
(100%)100, rundown: 0 (0%)100
Sep 10 19:00:08 rogue postfix/cleanup[78042]: 4EDE850837:
message-id=<20090910230008.4EDE850837 at rogue.shadowlair.com>
Sep 10 19:00:08 rogue postfix/smtpd[77645]: disconnect from
tx2ehsobe003.messaging.microsoft.com[65.55.88.13]


Per olof Ljungmark wrote:
> Eric Sheesley wrote:
>>
>> For the past week or so I've had 2-3 different emails that, as they
>> are attempting to be delivered end up crashing amavisd-new(just one
>> instance, not the whole daemon) leading the the "error:  queue file
>> write error" from postfix.  Both messages appear to have been 8bitmime
>> encoded from a quick glance, but no other common points.  These emails
>> will continually crash amavis every 15 minutes as the servers attempt
>> delivery.  I've used portmanager to rebuild amavis and all
>> dependencies with no change.  Any ideas on what could be wrong?
> 
> Hi,
> 
> Both amavis and Postfix can be made to provide rather substantial
> logging, that's what I would have done in your case. Or do you already
> have some logs to share?
> 
> Also, did you check that you did not run out of memory?
> 
> HTH,
> 
> -- 
> per


More information about the freebsd-ports mailing list