12 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: Command output: maild...
FromSent OnAttachments
Robin Lynn FrankJul 28, 2004 5:10 pm 
Sam VarshavchikJul 29, 2004 4:14 am 
Robin Lynn FrankJul 29, 2004 9:40 am 
Devin RubiaJul 29, 2004 10:48 am 
Robin Lynn FrankJul 29, 2004 12:03 pm 
Devin RubiaJul 29, 2004 1:33 pm 
Robin Lynn FrankJul 29, 2004 2:02 pm 
Sam VarshavchikJul 29, 2004 3:38 pm 
Robin Lynn FrankJul 29, 2004 8:22 pm 
Matthew D. FullerJul 30, 2004 12:07 am 
Robin Lynn FrankJul 30, 2004 9:09 am 
Devin RubiaJul 30, 2004 9:31 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Re: Command output: maildrop: signal 0x19)Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jul 29, 2004 3:38:46 pm
List:net.sourceforge.lists.courier-maildrop

Robin Lynn Frank writes:

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@paradigm-omega.net (temporary failure. Command output: maildrop: signal 0x19) vorl@paradigm-omega.net ro@localhost.paradigm-omega.net

Then you need to double-check exactly what signal 25 is on your platform. It is usually SIGXFSZ, but it may be something else.

Without knowing what that signal is, everything else is mere speculation.

The signal(7) man page (not signal(2) though) usually lists the signals.