=- Dallman Ross wrote on Thu 21.Dec'06 at 17:06:43 +0100 -=
# concept: Paul Chvostek <paul(_at_)it(_dot_)ca>
:0 # base-64-encoded html head is shrouding more than charset
* ^Content-Transfer-Encoding:(.*\<)?base64
* ^Content-Type:(.*\<)?text/(plain|html)
$BASE64
This is not what I'm looking for. :)
=- Google Kreme wrote on Thu 21.Dec'06 at 9:20:24 -0700 -=
:0
* ^content-type:.*text/plain
* B ?? ^content-transfer-encoding:
* ! B ?? ^content-transfer-encoding: *[^ b][^a][^s][^e]
This is neither what I'm looking for. :)
=- Bart Schaefer wrote on Thu 21.Dec'06 at 8:53:15 -0800 -=
That's not what he wants, though, because it won't match a
top-level base64 part.
Exactly!
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.
Not quite exactly:
a) single part, top-lvl check for base64 == true -> spam.
b) multipart, 1 text/plain exists (among possibly others, but even
if alone), yet each of the existing parts has only base64.
=> spam!
So it needs to check both header & body,
but not the same text/plain part: just all are base64 only.
(if specified at all!)
It is _not_ enough that there is either any base64 at all or that
just the text/plain is base64.
Now clearer?
--
© Rado S. -- You must provide YOUR effort for your goal!
Even if it seems insignificant, in fact EVERY effort counts
for a shared task, at least to show your deserving attitude.
____________________________________________________________
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