dovecot - Dec 2011 - Sieve too rfc compliant ;-)

It seems we have a few email addresses that are not RFC 5322 compliant,
and now that we've started using sieve these are failing. The problem is
that we have a few addresses with leading, trailing or double dots in
the local part:

	jan..frode at tanso.net
	.janfrode at tanso.net
	janfrode. at tanso.net

I believe these has been working fine with everything else in dovecot
(lda, lmtp, imap, pop), but that sieve is more strict. I think it's fair
enough that it's strict with messages generated by sieve scripts, but it
would be nice if it could be more tolerant with messages addressed for
the sieve script.

So, is there any setting for making it more tolerant ?


  -jf

On 12/20/2011 3:38 PM, Jan-Frode Myklebust wrote:
> It seems we have a few email addresses that are not RFC 5322 compliant,
> and now that we've started using sieve these are failing. The problem
is
> that we have a few addresses with leading, trailing or double dots in
> the local part:
>
> 	jan..frode at tanso.net
> 	.janfrode at tanso.net
> 	janfrode. at tanso.net
>
> I believe these has been working fine with everything else in dovecot
> (lda, lmtp, imap, pop), but that sieve is more strict. I think it's
fair
> enough that it's strict with messages generated by sieve scripts, but
it
> would be nice if it could be more tolerant with messages addressed for
> the sieve script.
>
> So, is there any setting for making it more tolerant ?
Could you indicate exactly in what situations these examples cause 
trouble? What does Sieve log?

Then I'll give it a look.

Regards,

Stephan.