Thanks everyone for the musings and ideas. Last attempt I made,
I added both our firewall pass-through and our local LAN IP
range into the Received test. Since that point (the 6th), our
office has received only one piece of mail violating this
rule (they forged an inner office email address name and the
spam filter said "Oh, it's in the whitelist! -100!").
The rules caught it and separated it. No other inner office
emails have been trapped by this rule, so I think it's working
just fine.
I like Google Kreme's thoughts of kinda reversing my thought
process, and if I have any problems with the existing setup,
I'll prolly give his suggestion a try, which follows:
Google Kreme wrote:
:0fw
* H ?? ^From:(_dot_)*(_at_)apid\(_dot_)net
* H ?? ^Received:.*65\.17\.84\.226
|formail -I"X-mydomain-FWCheck: PASS"
# If the previous recipe was not executed, then do this:
:E:
# Bad message
bad.messages
Mr Duck
____________________________________________________________
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