On Sat, 8 Jun 2002, Ruud H.G. van Tol wrote:
garydjones(_at_)altavista(_dot_)de skribis:
:0:
* ^Content-Type:.*multipart/digest
* TO(_dot_)*cygwin(_at_)cygwin(_dot_)com
| formail -n +1 -ds procmail
If the Content-Type header is inherited by the split messages,
this recurses.
What would make you think the content-type was inherited by the split
messages? Formail doesn't know anything useful about MIME, at least not
yet, and even if it did it would violate the MIME spec to have it push
the top-level type down into the encapsulated messages.
Also, precisely because formail doesn't know anything about MIME, if there
does happen to really be a digest-within-a-digest, the outermost formail
will heuristically take apart all levels of digesting -- so at worst you
invoke one extra formail to discover that you have a multipart/digest
header with the encapsulated body parts missing.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail