Re: [maildropl] Re: Command output: maildrop: signal 0x19)
Brought to you by:
mrsam
Menu
▾
▴
Re: [maildropl] Re: Command output: maildrop: signal 0x19)
|
From: Devin R. <de...@th...> - 2004-07-29 17:48:27
|
On Thu, Jul 29, 2004 at 09:39:48AM -0700, Robin Lynn Frank wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > On Thursday 29 July 2004 04:14, Sam Varshavchik wrote: > > Robin Lynn Frank writes: > > > Happened to spot this in the queue. Anyone have a thought on how to > > > determine the cause. This is the second time I've seen this, and it is > > > always a large email that is involved. > > > > > > # mailq > > > - -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- > > > DC1C37AD23 3254266 Wed Jul 28 16:02:49 ro...@pa... > > > (temporary failure. Command output: maildrop: signal > > > 0x19) vo...@pa... ro...@pa... > > > > Signal 25 is usually SIGXFSZ -- obviosly you are accepting mail that > > exceeds the maximum file size. > > Well, now it gets interesting. I removed that email from the queue and all > went normally until this morning: > > BC4B57AD56 5170 Thu Jul 29 07:35:11 ne...@pa... > (temporary failure. Command output: maildrop: signal 0x19) > vo...@pa... > ro...@lo... [SNIP] Just a question. What kind of mailbox do the recipients have? I am betting on mbox format and the mailbox has exceeded the maximum ulimit filesize. Either that or your OS or filesystem may have a maximum file size limit (usually 2G) that is exceeded. -- Devin |