Again - problem with multipart messages

David Relson relson at osagesoftware.com
Tue Dec 28 14:12:56 CET 2004


On Tue, 28 Dec 2004 12:52:19 +0300
Evgeny Kotsuba wrote:

> Hi,
> 
> I have just find  the reason of this problem:
> 
> If the message contain extra emty string like
> ---------------8<---------------------------------
> Subject: 
> =?windows-1251?B?z87EwNDI0sUg0cXBxSDIy8ggwcvIx8rIzCDK0MDRyMLT3iDUyMPT0NMhISE=?=
> 
> Date: Wed, 14 Jan 2004 22:56:37 +0300
> ---------------8<---------------------------------
> Than  possibly all text after empty string  is treated as pure text but 
> not as mutipart.
> If this is not RFC-compilant, than  for what it is ?  Or some clients 
> still handle it or it is done by spammerz to (beep) filters ?
> 

Hi Evgeny,

Correct.  The message is not RFC compliant.  The RFC specifies that an
empty line ends the message header.  A MUA _could_ scan past an empty
line to see if the following lines look like header lines, i.e.
(keyword, ':', value).  I suspect such checking would be difficult --
likely more trouble than it's worth.

HTH,

David



More information about the bogofilter-dev mailing list