[Dovecot] Return-Patch new Sieve plugin
Hi,
I switched today to the 1.2 alpha4 release and the new Sieve plugin. This plugin doesn't recognize the Return-Path header. Is this correct ? The cmusieve do recognizes it.
Thanks,
Diederick
Diederick van Dijk wrote:
Hi,
I switched today to the 1.2 alpha4 release and the new Sieve plugin. This plugin doesn't recognize the Return-Path header. Is this correct ? No, but I cannot reproduce this problem at my end, meaning that I get back reject messages from the following script while deliver is executed (from exim4) without command line parameters:
require "reject";
reject "Not acceptable";
It would help if you could paste any relevant log lines to see what exactly fails: i.e., what action is failing (reject or vacation) and with what reason?
Regards,
Stephan.
Stephan Bosch wrote:
Diederick van Dijk wrote:
Hi,
I switched today to the 1.2 alpha4 release and the new Sieve plugin. This plugin doesn't recognize the Return-Path header. Is this correct ? No, but I cannot reproduce this problem at my end, meaning that I get back reject messages from the following script while deliver is executed (from exim4) without command line parameters:
require "reject";
reject "Not acceptable";
It would help if you could paste any relevant log lines to see what exactly fails: i.e., what action is failing (reject or vacation) and with what reason?
Regards,
Stephan. Here is a part .dovecot.sieve.log file
sieve: info: started log at Dec 10 09:58:30. main script: line 24: error: specified header 'Return-Path' is not allowed for the address test. main script: line 32: error: specified header 'Return-Path' is not allowed for the address test. main script: line 44: error: specified header 'Return-Path' is not allowed for the address test.
elsif allof (address :contains "Return-Path" "<ipw2100-devel-bounces@lists.sourceforge.net>") { fileinto "INBOX.Mailinglists.ipw2100";
}
main script: error: validation failed.
Diederick van Dijk schreef:
Here is a part .dovecot.sieve.log file
sieve: info: started log at Dec 10 09:58:30. main script: line 24: error: specified header 'Return-Path' is not allowed for the address test. main script: line 32: error: specified header 'Return-Path' is not allowed for the address test. main script: line 44: error: specified header 'Return-Path' is not allowed for the address test.
elsif allof (address :contains "Return-Path" "<ipw2100-devel-bounces@lists.sourceforge.net>") { fileinto "INBOX.Mailinglists.ipw2100";
} main script: error: validation failed.
Ah, that sheds some light on the issue. This new behaviour is a direct result of the new Sieve RFC (5228). The RFC now states on what headers the address test is allowed, which does not include the Return-Path header. I was not entirely sure of the intention of this new limitation and I started a discussion on this. As it turns out many implementations relax this and my interpretation is a bit harsh: the current implementation throws a hard compile error when a disallowed header is used. I intend to change this to allow all headers that are parseable as an address. Errors are then only encountered at runtime and a warning is logged if the address test fails due to an invalid address. Currently, you are unfortunately forced to use the header test or use the envelope test (which should yield the same information).
Regards,
-- Stephan Bosch stephan@rename-it.nl
participants (3)
-
Diederick van Dijk
-
Stephan Bosch
-
Stephan Bosch