-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
... Simply slapping the whole includerc into a
braced copy and discarding anything which survives the filter won't
have the desired effect because nothing the first set of recipes
MIGHT do the messages is there when the second includefile is
processed.
So I _shouldn't_ do this?
:0
{
INCLUDERC=/etc/procmail/html-trap.procmail
INCLUDERC=/etc/procmail/spam
}
It seems to work ok??
Thus, I said, "SPECIFICALLY what those recipes does has a LOT to do
with how you make changes."
The first includerc is a procmail filter called sanitizer:
http://www.impsec.org/email-tools/sanitizer-configuration.html
Essentially, it mangles attachments with .exe or .vbs type
extenstions into file.66758DEFANGEDexe.
The second one just does this:
:0fw
| spamc -u mike
:0fw
* ^X-Spam-Report: \/.*;
| formail -I "X-message-flag: $MATCH" -I "X-Spam-Status: Yes"
This just runs the email through a filer checking against a long list
of spam type characteristics and if found scores them.
Obviously I want all emails subjected to the filters in the sanitizer
as well as the spam filter. So, regardless of whether an email is
full of attachments with .exe or not, it should still be scanned for
spam.
Mike Loiterman
mike(_at_)ascendency(_dot_)net
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
Comment: Message digitally signed by Mike Loiterman
iQA/AwUBPI7Uh6St969JPeAoEQIigQCfZ9QAdufvDPjyhlaoohj4yL8S7ZUAoJXe
VLORH+LtLvhdevnaUrtgtT1J
=ruW4
-----END PGP SIGNATURE-----
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail