Re: "Content/Error_report_too_long,_sorry." - FYI . .

Philip Rhoades via Courier-maildrop <[email protected]> Mon, 21 Oct 2024 16:45:57 +1100
Newsgroups gmane.mail.maildrop
Message-ID <[email protected]>
Sam,


On 2024-10-20 13:53, Philip Rhoades via Courier-maildrop wrote:
> 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 . .


This exercise was useful for a few reasons - inc finding some trivial 
folder delivery errors in my .mailfilter file . .

Also, I found that:

With .qmail:

   | maildrop 2>/home/phr/Maildir/maildrop_logs/`date +'%Y%m%d_%H%M%S_' | 
tr -d '\012'; echo $$`

I get zero bytes in the log files

but with:

   | /usr/bin/maildrop /home/phr/.mailfilter 2> 
/home/phr/Maildir/maildrop_logs/`date +'%Y%m%d_%H%M%S_' | tr -d '\012'; 
echo $$`

I get 3MB+ in each of the log files when VERBOSE >=3.

At first I thought it was because I had one version (the latest) 
installed on the Fedora 40 Linux Host machine and an old one (dated: Jul 
26 2019!) that I have been using for years (and forgotten about) with 
the Fedora 40 Podman VM running Indimail and somehow the different 
versions of maildrop were being used - but that wasn't correct.  I found 
I _have_ to use the old maildrop because of some lib conflict problems 
with the also old version of the Qmail-derived IM on the VM.  I need to 
update IM on that VM soon so I will talk to the author and try and sort 
out this issue at the same time . .

Anyhow, why does specifying full paths give different results in my 
.qmail file? . . weird . .

Regards,

Phil.


Thanks,

Phil.

-- 
Philip Rhoades

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