I'm looking to implement a (crude?) attachment filter. So far, I've been
matching with something like this for file extensions:
I'm not actually blocking .tar.gz's, but I'd like to block files with
double extensions of .pif, .com, etc...
I feel like I'm missing some attachments - are
*^Content-type: (multipart/mixed) &&
enough, or can attachments slide past in additional ways? Would it be
worth the pain of chewing through an RFC for this?
Any suggestions are appreaciated in advance.
Mark T. Valites
Unix Systems Analyst
1 College Circle - 124b1 South Hall
Geneseo, NY 14454
procmail mailing list