dovecot - Jun 2009 - sieve vacation messages trouble

Hi,

sieve vacation replies are rejected by gmail with a "555 5.5.2 Syntax  
error".
The return path is set to "<>", I think this is why this error
is
triggered by gmail.
The rest of the vacation message seems ok.

I'm using dovecot 1.1.11 (waiting for final 1.2 to upgrade) ,  
delivering with "/usr/lib/dovecot/deliver -d email at domain"

St?phane Cottin

After looking at the source, I saw that the return path is not set by  
dovecot.
Seems to be a qmail related issue, sorry for the noise.

Le 30 juin 09 ? 16:06, St?phane Cottin a ?crit :
> Hi,
>
> sieve vacation replies are rejected by gmail with a "555 5.5.2  
> Syntax error".
> The return path is set to "<>", I think this is why this
error is
> triggered by gmail.
> The rest of the vacation message seems ok.
>
> I'm using dovecot 1.1.11 (waiting for final 1.2 to upgrade) ,  
> delivering with "/usr/lib/dovecot/deliver -d email at domain"
>
> St?phane Cottin
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 30 Jun 2009, St?phane Cottin wrote:
> sieve vacation replies are rejected by gmail with a "555 5.5.2 Syntax
error".
This looks like a SMTP error. What does your local SMTP server logs?
Sieve uses the local "sendmail" binary to transmit the message.
> The return path is set to "<>", I think this is why this
error is triggered
> by gmail.
Hmm, you mean gmail as in Google Mail server?
If so, I doubt it. <> is the RFC null sender for DSNs to prevent mail 
looping. However, many MTAs block DSNs to non-local recipients right away.

Anyway, <> should not cause a syntax error.

Bye,

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSkogsnWSIuGy1ktrAQI1qggApvFU8SteLSa9Vln2iYo6FfrvjVQTRZup
okUXP+FiWOyTBpCgR695bcB0+kq4Q5BHXtelXek6O5+mkcdZGrXX64gP4LseBZEa
N+rwRzFIME0JrfX+04O4zgIPA2ZsRJhDO/5TWSZJNVpLnu6KPBDBG3x+RBQqIgR0
ldawLYz/7AYgWbLXUocyFmJLPBwE+5SYr8lu03dm2gPHtkcJxCUeH685R4vaCzEb
Nqi3wCwM0AxlTUon5yy1YawZGMoG86fDOUFrqqesEfstQcTlK1eRkHmce2cnb8a9
nA0dLTJm9dS0zG80W0upGAgnYp8qk6GnLgUwDbOL4rqtpOmN4KZhqw==N2u3
-----END PGP SIGNATURE-----