I see something in procmail.log I don't understand.
This rule:
:0
* ^Subject:.*Retrospect
* ^Message-Id:(_dot_)*(_at_)reader\(_dot_)local\(_dot_)lan
retrospect.in
Appears to fail on a message that satisfies both regex. At least the
message that turns up in the wrong folder appears to:
From the actual message:
From: reader(_at_)newsguy(_dot_)com
Subject: Retrospect notification from BJP (10/27/2009)
To: reader(_at_)reader(_dot_)local(_dot_)lan
Date: Tue, 27 Oct 09 14:04:35 -0500
Message-Id:
<200910271904(_dot_)n9RJ4dqm018031(_at_)reader(_dot_)local(_dot_)lan>
This is being sent by a backup tool from a windows XP box and I think
maybe something to do utf8 is happening. At any rate, this is what I
see in the log:
procmail: No match on "^Subject:.*Retrospect"
[...]
procmail: Assigning "LASTFOLDER=local.in"
procmail: Opening "local.in"
procmail: Acquiring kernel-lock
procmail: Notified comsat: "reader(_at_)0:/home/reader/spool/local.in"
From reader(_at_)newsguy(_dot_)com Tue Oct 27 14:04:39 2009
Subject:
=?utf-8?B?UmV0cm9zcGVjdCBub3RpZmljYXRpb24gZnJvbSBCSlAgKDEwLzI3LzIwMDk
Folder: local.in 692
procmail: Assigning "EXITCODE=0"
procmail: Executing "formail -XMessage-Id: && date +"%b %d %T%nSTOP""
Message-Id:
<200910271904(_dot_)n9RJ4dqm018031(_at_)reader(_dot_)local(_dot_)lan>
Oct 27 14:04:39
STOP
Look what procmail saw as subject line. But yet the Message-Id is the
one from the Retrospect mail that turns up in wrong folder.
Anyone have a clue what may cause this?
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail