RFC-2047 [was: New spam trick]

[David Relson]

At 04:43 PM 7/23/03, Nick Simicich wrote:
>At 09:35 AM 2003-07-21 -0400, David Relson wrote:
>
>>At 09:05 AM 7/21/03, Boris 'pi' Piwinger wrote:
>>>David Relson wrote:
>>>Ah!!! That stuff.  I, too, have noticed occasional messages like those.
>>
>>Looks like bogofilter doesn't know about RFC-2047.  I guess it's time to 
>>add RFC-2047 compliance to the TODO list.
>
>Just as a point:  I understand that you do not plan on decoding the mail 
>and forwarding it, if this is a typical bogofilter use, it is only to 
>"examine in eyespace" what would be presented to the user.  I have looked 
>into this a fair amount for demime, and this is a really hard piece to get 
>correct.  Only certain header fields may be encoded, and so 
>forth.  Furthermore, it is possible to encode newlines and cr's, such that 
>if you reparse a decoded header, the header is no longer a good 
>header.  The RFC warns that the header should only be decoded for keeps, 
>as it were, by the MUA of the recipient.  This is for good reason.

Hi Nick,

How go things with you?  Its been a while...

You raise some interesting points.  I much appreciate your comprehensive 
knowledge of email and the RFC's.  I'm still learning :-)

Anyhow, sounds like further experimentation is needed.  I'll create some 
"funny" headers and see what happens, specifically whether bogofilter's 
processing is reasonable, or not.

If you have some "interesting" sample messages that I should test with, 
feel free to wrap them in a .tgz file and send them.

Cheers!

David