Josip Rodin wrote: > I think I couldn't reproduce this with maildrop proper the last time around, > and then I marked it as moreinfo. I'll try again to be sure, but can you > try, too? Just generate a long file that is almost as large, and then log to > it with a maildrop using a temporary mailfilter file.
[EMAIL PROTECTED]:~>head -3 .mailfilter #!perl # not really, but close enough for vim VERBOSE=1 logfile "$HOME/.maildrop-log" [EMAIL PROTECTED]:~>ls -l .maildrop-log -rw-r--r-- 1 joey joey 104857600 Feb 28 14:08 .maildrop-log [EMAIL PROTECTED]:~>maildrop fofofo [EMAIL PROTECTED]:~>ls -l .maildrop-log -rw-r--r-- 1 joey joey 104857725 Feb 28 14:11 .maildrop-log So it has logged, this is used the maildrop package. Now I switch to courier-maildrop: [EMAIL PROTECTED]:~>head -2 .mailfilter [EMAIL PROTECTED]:~>dd if=/dev/zero of=.maildrop-log bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 0.733954 seconds, 143 MB/s [EMAIL PROTECTED]:~>ls -l .maildrop-log -rw-r--r-- 1 joey joey 104857600 Feb 28 14:15 .maildrop-log [EMAIL PROTECTED]:~>maildrop fofofo [EMAIL PROTECTED]:~>ls -l .maildrop-log -rw-r--r-- 1 joey joey 104857725 Feb 28 14:15 .maildrop-log Ok, that's unexpected. If courier-maildrop doesn't choke on long log files on its own, it must have to do with how it's being run, which on my mail server is from postfix. -- see shy jo
signature.asc
Description: Digital signature
