-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2005-09-03 at 12:21 -0500, Patrick Shanahan wrote:
Good idea, I had forgotten about formail. I'll try.
Please give your results. gud luk,
Here goes the report. I used this procmail file: VERBOSE=on DEFAULT=$HOME/tmp/Mail/OutDefault LOGFILE=$HOME/tmp/Mail/procmail.log LOG=`echo -n "+++----> ";date --iso-8601=seconds ; echo` LOG="" :0 * ^Received: from correo.foo.es { :0 * ^Received: from (ruebert.ieee.org|engine.ieee.org|hormel3.ieee.org|boldfish.ieee.org|aries3.ieee.org) $HOME/tmp/Mail/OutIEEE :0 * ^FROM_DAEMON $HOME/tmp/Mail/Out_daemon :0 $HOME/tmp/Mail/Out_foo } and run using this line: time formail -ds procmail -m procmailrc < IN_foo (it run in about 22 seconds) Result was this: 64288119 2005-09-05 19:31 IN_foo 87043 2005-09-05 20:01 OutDefault 64193756 2005-09-05 19:57 Out_foo 8591 2005-09-05 19:58 Out_daemon 461624 2005-09-05 19:52 procmail.log 695 2005-09-05 19:51 procmailrc Then I read the mailboxes and saw that IN_foo had 401 messages, and Out_foo just 400, one missing. But then, OutDefault had 11, and Out_daemon 1. They don't add, the entry mbox had 401. Funny. The entry mbox had 64,288,119 bytes and the three output mboxes, have, added together 64,289,390. The byte count matches, at least. The OutDefault mbox has 5 "funny" emails, broken inside. One, for example, contains only this (looking at the full headers in Pine): Content-Type: text/html; name=3D"text2.html"; format=3Dflowed Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename=3D"text2.html" All those 5 "funnies" belong to the same email, received last mail. The email itself I can read and seems to be normal (considering outlook to be normal :-p ). A file corruption, maybe. I will put back all those emails (except the funnies) in the main mailbox where they came from, and see if things work correctly now or not. I'll leave this email in the drafts mbox till I know. [...] (Next day) No, it wasn't that. I got another email redirected to the inbox. The above procedure did not catch the problem. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDHXHPtTMYHG2NR9URAqsGAJ4xfMPH72qGGq6WtVL9mkZqiZIO/wCfYPIV xIK0u4Rl7gC4G1dRZpVG+B4= =RX1i -----END PGP SIGNATURE-----