So it may not be FROM_DAEMON, but something in that rather
complicated regexp is snaring the email.
The difficulty is that regexp is looking at a bunch of header
information so without the full headers of the test message(s) it
isn't possible to even start to determine what is getting caught.
From your expansion of the FROM_DAEMON headers like Resent-from:,
Sender:, X-Envelope-From:, etc. are all getting looked at not just
the From: address.
The place to start is with the full email of something that always
gets caught, then break the above rule into two individually scored
ones (FROM_DAEMON as one, the rest is the other) to see which one
triggers. That should get you closer.
RIch
Thanks for the helping hand. I eliminated all but the FROM_DAEMON and
ran some tests thru this recipe.
:0 h
* -100^0 ^FROM_DAEMON
* 1^0
{ }
:0 Ehwi : log.lock
| echo -e "$TODAY\t$FROM\t$SENDER" >>log_from_daemon_dropped
And when the header contains parenthesis in the Friendly Name, like this
From: "LP CORPORATE SERVICES (LPCS)" <header(_at_)aol(_dot_)com>
the FROM_DAEMON seems to trip irregardless of the actual email address.
and when I send in email with -mail in the envelope sender and From
header, without any parenthesis, like this
From env91010-mail(_at_)yahoo(_dot_)com Tue Apr 14 18:42:30 2009
Date: Tue, 14 Apr 2009 20:42:00 +0200
From: "Friendly Name" <head91010-mail(_at_)yahoo(_dot_)com>
Then FROM_DAEMON is tripped up by the envelope sender, not the From:
header as in the previous example.
So FROM_DAEMON looks at both envelope sender and From: header in
making it determination.
I'm still banging away, but that's what I've learned so far.
mark
____________________________________________________________
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