On 12/21/06, Google Kreme <gkreme(_at_)gmail(_dot_)com> wrote:
Never never NEVER put the default H flag in the header line.
(Because some versions of procmail have a bug that's tripped by that.)
:0
* ^content-type:.*text/plain
* B ?? ^content-transfer-encoding:
* ! B ?? ^content-transfer-encoding: *[^ b][^a][^s][^e]
or something like that
That's not what he wants, though, because it won't match a top-level
base64 part. What he really wants is to tie together the content-type
and c-t-e headers so that this only matches when the SAME body part
(including the top-level one) has both text/plain and base64.
The only way to do that is something like:
# First do the header only, where Content- lines may not be consecutive
:0:
* ^Content-Type: *text/plain
* ^Content-Transfer-Encoding: *base64
$BASE64
# Now do the body, grouping blocks of embedded Content- lines
:0 B:
* H ?? ^Content-Type: *(multipart|message)
* ()\/(^Content-.*($))*
* MATCH ?? (.*($))*Content-Type: *text/plain
* MATCH ?? (.*($))*Content-Transfer-Encoding: *base64
$BASE64
I'm not entirely sure even that will work.
____________________________________________________________
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