12 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: Command output: m...
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:Re: [maildropl] Re: Command output: maildrop: signal 0x19)Actions...
From:Matthew D. Fuller (full@over-yonder.net)
Date:Jul 30, 2004 12:07:47 am
List:net.sourceforge.lists.courier-maildrop

On Thu, Jul 29, 2004 at 07:55:23PM -0700 I heard the voice of Robin Lynn Frank, and lo! it spake thus:

Of course, this now leaves me somewhat confused since I can not find anything related to file size, but only to a specific user. While this all presented itself with the failure to deliver a 3.4MB email, a larger file was delivered to a different user today and nothing gets delivered to the user in question.

Any thoughts on a methodology of tracking this down would be appreciated.

Check for a maildrop logfile.

When mine hits 50 megs, mail starts backing up in the queue until I move the logfile.

-- Matthew Fuller (MF4839) | full@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/

"The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet"