[Dovecot] broken message header parsing (was Re: forwarded message is broken in 2.2.10 with pigeonhole-0.4.2)

[Axel Luttgens]

Le 15 janv. 2014 à 23:29, Axel Luttgens a écrit :

> [...]
> 
>> Pigeonhole stops parsing headers at nokeyword, OK.
> 
> Well, yes and no...
> 
> I've just retried with a redirect to "her at some.domain", still through a telnet against lmtp:
> 
> 	lmtp -> mailbox (with sieve redirect)
> 
> And it appears that the message headers are now mangled, with exactly the same pattern as in the case of:
> 	
> 	postfix -> dovecot's lmtp -> mailbox (without sieve redirect)
> 
> Not sure how to interpret such results...

I must have been very tired when writing the last sentence.

The message went back thru postfix, and has thus been submitted to postfix' parsing rules (depending on its settings).


> But it seems that pigeonhole isn't neutral, and doesn't stop its parsing at the bogus header.

Or maybe could it be said that it is very neutral, in the sense that the bogus message is passed as is?

Axel