Bob Holtzman posted,
| procmail: Match on
| !
"(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?)holtzm(_at_)primenet(_dot_)com
Well, yes. There was a match on NOT (notice the exclamation point) ^TO_
your address; in other words, ^TO_holtzm(_at_)primenet(_dot_)com was not in the
headers.
(I'll echo another respondent's advice to use \. to match a literal period.)
I'd like to see what the procmail code is in that INCLUDERC. There has to be
something in a verbose logfile after "Match on" -- a report that procmail is
testing the next condition, or that it is executing the action, or that it is
turning verbosity off. The next thing you had below that "Match on" was a
logabstract.
| I noticed one of the headers shows "for <holtzm(_at_)localhost>". Would this
| qualify?
No; ^TO_ does not include matching on Received:.*for; you would have to add
a provision for that if you wanted it (but it appears that you don't).
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail