David Turley <dturley(_at_)pobox(_dot_)com> wrote:
http://www.rosat.mpe-garching.mpg.de/mailing-lists/procmail/2002-11/msg00239.html
It seems these base64 encoded messages the pond scum are sending can
be trapped base on the headers, no need to decode. I've not had any
false positives.
Your last remark is a different kettle of fish from that discussed in the
URL you offer. In the URL, it says:
lp> I am thinking of writing a script to throw out the multipart/mixed from all
lp> messasges where there is only one part, but I suspect someone must
lp> already have done that. Can anyone give me a pointer?
lp> / Lars Poulsen - lars(_at_)beagle-ears(_dot_)com -
http://www.beagle-ears.com/lars/
As for that, I have this:
:0 # 021216 () where's the "multipart"? There's just one encoded part
* ^Content-Type:(.*\<)?multipart/mixed
* 2^0 B ?? ^Content-Transfer-Encoding:(.*\<)?base64
* -1^1 B ?? ^Content-Type:
{ RX = "${RX:+$RX, }UBE.B.BASE64" }
As for the entire message being encoded, per your last remark, I have this:
# concept: Paul Chvostek <paul(_at_)it(_dot_)ca>
:0 # 021109 () base-64-encoded html head is shrouding more than charset
* ^Content-Type:(.*\<)?text/(html|plain)^^
* ^Content-Transfer-Encoding:(.*\<)?base64
{ RX = "${RX:+$RX, }UBE.CT.HTML+BASE64" }
Both work fine. A version of the latter is found in the list archives.
--
dman
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail