At 10:11 2009-10-29 -0500, Harry Putnam wrote:
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:
Something to keep in mind is whether the recipes that deliver to the "wrong
folder" are being processed BEFORE the recipe in question.
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>
Are you viewing this information from within a MUA (which may be decoding
the MIME encapsulation), or is this how the raw mailbox file looks, say as
viewed using 'more'? The latter is how you should view the message to see
how procmail is seeing it.
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
Well, uhm THAT tells you it's an encoding issue, doesn't it?
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.
So? Your recipe requires that BOTH the conditions match.
Are you new to MIME encoding, or just unaware that it can be used to encode
subjects (and name text even) in the header?
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
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