Part of the problem you encounter in the real world is UAs which try to be
helpful by interpreting "where you want to go". Otherwise it wouldn't be
possible, say, for an alleged multimedia presentation e-mail containing a
purported "wave" sound attachement to launch as an .exe simply because it
ends with .exe.
Real world? Do you think I'm not dealing with the real world?
Really you should read 2557. File a class action lawsuit, will ya?
For those interested:
http://www.faqs.org/rfcs/rfc2557.html
HTML is not good. Did you think about JavaScript? You should. VBScripting?
Awwyep.
Yes, I did. Perhaps you missed the word "crude" from the original post.
Still no problem statement. More minutae. My kinda peeps, Amazon,
Do I have to spell it out for you letter by letter? It doesn't seem like
anyone else here has had a problem understanding what I'd like to do. But
for those struggling to understand such an abstaract concept:
I would like to create a crude filter to drop e-mails that appear to
contain attachments with certain file extensions. Call me the BOFH, but I
really don't care if they rename the file or if it's not actually what the
extension suggests it is.
Oh. Cool. So, don't even screw with anything but the Content-Disposition
header somewhere in the body of the mails. Sounds like you're the trusting
type, that oughta work fine! No problemo.
Headers don't live in the body ace.
It's one thing to give constructive criticism, but it's another to act
like an ass. If you don't have anything nice to say...
--
--))> >--))>
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