Re: "Content/Error_report_too_long,_sorry."

Philip Rhoades via Courier-maildrop <[email protected]> Sat, 19 Oct 2024 23:43:01 +1100
Newsgroups gmane.mail.maildrop
Message-ID <[email protected]>
Sam,


On 2024-10-19 23:04, Sam Varshavchik wrote:
> Philip Rhoades via Courier-maildrop writes:
> 
>>> If everything is set up correctly you only need a
>>> 
>>> | maildrop
>>> 
>>> This actually runs maildrop in proper delivery mode, reading 
>>> $HOME/.mailfilter, and completely ignoring the VERBOSE setting.
>> 
>> 
>> Ok, now I am only getting this:
>> 
>>   deferral: ezmlm-weed:_fatal:_out_of_memory/
>> 
>> which I think I have asked about before but I don't remember getting a 
>> response to . .
> 
> I am not familiar with that. I don't see why maildrop's invocation 
> would be a factor there.
> 
>> Anyway, would it be possible to generate separate delivery messages 
>> for each email to a nominated directory? - then each log file could be 
>> as long as necessary for debugging purposes and I can just remove them 
>> as necessary based on their time-stamps . . possible?
> 
> maildrop writes log message to standard error, so it's up to you to 
> handle it however you wish. If you want to redirect standard error 
> somewhere else, you could even get fancy and find something that will 
> write its input to a dated filename, and then use logrotate, or 
> something, to purge old log files.


I probably wasn't clear - I would like to have a separate log file for 
each separate email - instead of one long log file . .

Thanks,

P.
-- 
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  [email protected]