At 15:20 2009-07-02 -0400, Daryl Styrk wrote:
I'm still slightly confused in how to construct a recipe that will simply
dump html to /dev/null. I am still not even totally sure this is what I
should be doing.
Ah, you were asking how to identify HTML messages.
Here's some conditions (not complete recipes - though flags and a delivery
would do it):
# html only message
* ^Content-Type:.*text/html
# regular multipart/alternative (html or richtext)
* ^Content-Type:.*multipart/alternative
You can also scan the message body for Content headers (when
multipart). I'd suggest NOT dumping messages to /dev/null immediatley -
file them to a mailbox where you can check to make sure things are working
as planned.
What I don't like is the size of the messages.
# condition for messages exceeding 20K (or so) in size.
* > 20000
I never delete anything and the size of the mails can rack up quickly.
I don't purge mail either - but I do archive it to DVD periodically.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
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