Thanks Sean, it works. Regarding your note, the spamers like
this fashion because it helps to avoid filters like, hummm..
procmail to figure out the "MILLION DOLLAR OFFER".
Thanks,
Udi
On Mon, 20 Oct 2003, Professional Software Engineering wrote:
At 19:12 2003-10-20 +0200, Udi Mottelo wrote:
I'm looking for a tool/solution to deciphering the iso-8859 in
the Subject line, to check it by procmailrc. Things like the
following:
Subject: =?iso-8859-1?B?T3JkZXIgQ2FuY2VsbGF0aW9u?=
That B? to ?= is base 64 encoded:
:0
* ^Subject:[ ]*=\?iso-8859-1\?B\?\/[^\?]*
{
DECODE_SUBJ=`echo $MATCH | mimencode -u`
}
Quoted printable (where you can basically read the subject already):
:0
* ^Subject:[ ]*=\?iso-8859-1\?Q\?\/[^\?]*
{
DECODE_SUBJ=`echo $MATCH | mimencode -q -u`
}
I don't use that recipe, but just mixed it up to answer your inquiry. It
may need adjusting. I've been considering thwacking subject lines though,
in a fashion simliar to this:
:0fhW
* ^Subject:[ ]*=\?iso-8859-1\?B\?\/[^\?]*
| formail -i "Subject: `echo $MATCH | mimencode -u`"
Personally, if it's ISO-Latin to start with, I don't see a need to encode
it in this fashion in the first place, since it breaks systems which for
[...]
over two decades have worked on the expectation that English and many
Western European languages are transmitted as such. It's my experience
that mail clients which normally transmit in some non-latin encoding tend
to be responsible for sending messages in this encoding.
---
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(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
--
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail