Re: "Content/Error_report_too_long,_sorry."

Sam,


On 2024-10-19 23:51, Sam Varshavchik wrote:
> Philip Rhoades via Courier-maildrop writes:
> 
>>> 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 . .
> 
> That's just a matter of being granular enough. Instead of only a date, 
> also include the time, and the current pid. That should produce a 
> unique filename for each message. Something like:
> 
> | maildrop 2>/tmp/`date +'%Y%m%d%H%M%S' | tr -d '\012'; echo $$`


Ah! - perfect!  I will experiment with the VERBOSITY levels . .

Thanks,

Phil.
-- 
Philip Rhoades

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