sieve-filter failure problems

[Stephan Bosch]

Op 8/13/2015 om 4:33 PM schreef Jost Krieger:
> I use sieve-filter for postprocessing misclassified mail.
> For false positives I use the following script:
>
> 	require [ "variables", "include", "fileinto" ];
>
> 	global [ "FORCENOSPAM", "ext", "ext1" ];
>
> 	set "FORCENOSPAM" "YES";
>
> 	fileinto "JUNK-PRENOUCE";
>
> 	if header :matches "Delivered-To" "*+*@*" {
> 	   set "ext" "${2}";
> 	   set "ext1" "${2}";
> 	}
>
> 	include :personal "production";
>
> FORCENOSPAM suppresses the spam handling and the Delivered-To stuff
> tries to regenerate envelope info.
>
> This is my crontab entry:
> 	1-57/4 * * * * cd ~kriegjcb; /usr/local/dovecot/bin/sieve-filter -v -e -W -u kriegjcb -m Spam/U0-failed ~kriegjcb/sieve/nospamfilter.sieve Spam/U0
>  
> Most things work fine, but a few of my rules will try to forward mail.
> This will fail and my idea was I handle this manually from the folder
> Spam/U0-failed.
>
> Unfortunately the mail will arrive there but will also be left in the source folder
> Spam/U0 and will be processed again every 4 minutes ...
>
> This is probably not intentional?

Fixed:

http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/469f9794408b

Regards,

Stephan.