RFC-2047 & encoded QP text

[Boris 'pi' Piwinger]

Matthias Andree wrote:

>> The "\?" is not only standards compliant but necessary.  Junior has
>> email that kills bogofilter without it because the lexer keeps on
>> reading an encoded attachment and runs out of buffer space.  With the
>> "\?", the lexer works much better.
> 
>> Regarding spaces, if necessary we could try something like "[^\t\r\n\?]"
>> and see what happens.  Let's wait until there's a clear need.

No, there MUST NOT be any non-ASCII-character.

> An encoded word does not continue past the end of the line, this must be
> accounted for.

Exactly. I think this would save us from any danger.

> We will also need to take care that we remove linear
> white space between two encoded words, so that:
> 
> Summary: =?ISO-8859-1?Q?Regen?=
>   =?ISO-8859-1?Q?w=FCrmer=3F?=
> 
> yields {Summary; Regenwürmer} rather than {Summary; Regen; würmer}.

Yep.

> This is necessary so spammers can't split up their tokens at will to
> hide them from bogofilter's view.

Actually, many normal readers also split words like this.
Sometimes this is necessary.

pi