I'm looking to implement a (crude?) attachment filter. So far, I've been
matching with something like this for file extensions:
:0 H
*^Content-type: (multipart/mixed)
{
:0 B
*^Content-Disposition: (attachment|inline)
*filename=".*\.tar\.gz"
/path/to/Maildir/
}
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) &&
*^Content-Disposition: (attachment|inline)
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
--
--))> >--))>
Mark T. Valites
Unix Systems Analyst
1 College Circle - 124b1 South Hall
SUNY Geneseo
Geneseo, NY 14454
585-245-5577
585-259-3471 (Cell)
585-245-5579 (Fax)
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail