>What I'm looking for are subject headers as shown below:
>
>Subject: =?us-ascii?B?MCBNZW4sIGl0IHJlYWxseSB3b3JrcyEgZnA=?= iwsgfb
>
I've posted some examples. You need to do it thus:
header T_SBJT_ENC ALL =~ /\nSubject:.[etc.]/i
It works for me, but not always (I don't use + or *, I always limit
In a post by Jmason back on Sept. 9 2003, try this:
header MK_CHARSET_IN_SUBJECT Subject:raw =~ /ISO\-8859/i
Change the chrset part to whatever you want, this should allow you access to
un-decoded subject.
Frederic Tarasevicius
Internet Information Services, Inc.
http://www.i-is.com/
810-794-440
At 07:13 AM 12/9/03 -0500, Scott Sprunger wrote:
I wanted to test a theory so I've been trying to come up with a rule that
will catch encoded strings in the subject of a message. So far I've tried
the rules below, but none of them are hitting. Any suggestions?
rawbody type rules have already had
Hello Folks,
I wanted to test a theory so I've been trying to come up with a rule that
will catch encoded strings in the subject of a message. So far I've tried
the rules below, but none of them are hitting. Any suggestions?
rawbody T_SBJT_ENC /^Subject:
?=\?(us\-ascii|iso\-8859\-1|windows\-12
