dovecot - Jan 2015 - pigeonhole - how to whitelist

Hello,

When new users are added we start them with a spam rule that routes spam 
to their junk folder.  I don't see a way to assign priority ... so how 
does a user whitelist a spam-flagged email?  Are the rules applied in 
some order?  Alphabetically perhaps?  If so I can name the spam rule z-spam.
Thanks in advance.

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

On Thu, 15 Jan 2015, Cliff Hayes wrote:
> When new users are added we start them with a spam rule that routes spam to
> their junk folder.  I don't see a way to assign priority ... so how
does a
> user whitelist a spam-flagged email?  Are the rules applied in some order? 
> Alphabetically perhaps?  If so I can name the spam rule z-spam.
rules do have exactly one order, in which they appear in the Sieve script.

But you certainly mean something different. Maybe a particular Sieve 
front-end, that assembles the Sieve script together?

See, http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#multiscript

There is one personal script the user may change and you can define one or 
more scripts to be executed before or after the personal script. So, if 
this would be pigeonhole problem, you define the spam processing in an 
"after" global script and let have the user whitelist a message, the 
personal script must file the message somewhere and stop script 
processing, see the paragraphe after "sieve_after = ".

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVLi+yHz1H7kL/d9rAQL7VwgAnJyDcjCccum3681zpRl7wwm7BWgJq/9D
jYGTOg162a/MO1nCcJTV+D0jETe4eaLe7QLLbYrhHyjdOoeHk32w9fMmNtrFsDQS
PnddE8o0xIxEquuabBbY5grx9KWKBoriZvaN6XbBh+kC+GxAQWkZ8P+4WA5NHZCc
/FbwD/3Nf5C7rZbujgkxLdhaGD+pb9EfE9+fq6WZD8+/avU/Gfm91N1H0a/I5vGf
OgeErUwBH35iA0Z++cCv7tT7i4stwHAyF12LVnr9uQQE4XtDXAgQjzzeC/eY008b
iyB0+i3edeR6peCh+MJ7NIn3ptNEilf8jHAfv5WrnCtRM9uSZvJPmQ==8CZj
-----END PGP SIGNATURE-----

Thanks.
That's exactly what I needed.
However I have a permission problem.
I added the parameter to 90-sieve.conf and created the directory but now 
I get the following permissions errors in maillog even though I have the 
file and directory wide open with 777 permissions:

Error: yY/0JHtauVQfPgAAU+Cu/Q: sieve: failed to open sieve dir: 
stat(/var/lib/dovecot/sieve/after.d/) failed: Permission denied 
(euid=526(cliffhayes) egid=12(mail) missing +x perm: /var/lib/dovecot, 
euid is not dir owner)


On 1/16/2015 1:33 AM, Steffen Kaiser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, 15 Jan 2015, Cliff Hayes wrote:
>
>> When new users are added we start them with a spam rule that routes
>> spam to their junk folder.  I don't see a way to assign priority
...
>> so how does a user whitelist a spam-flagged email?  Are the rules
>> applied in some order? Alphabetically perhaps?  If so I can name the
>> spam rule z-spam.
>
> rules do have exactly one order, in which they appear in the Sieve script.
>
> But you certainly mean something different. Maybe a particular Sieve
> front-end, that assembles the Sieve script together?
>
> See, http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#multiscript
>
> There is one personal script the user may change and you can define one
> or more scripts to be executed before or after the personal script. So,
> if this would be pigeonhole problem, you define the spam processing in
> an "after" global script and let have the user whitelist a
message, the
> personal script must file the message somewhere and stop script
> processing, see the paragraphe after "sieve_after = ".
>
> - -- Steffen Kaiser
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEVAwUBVLi+yHz1H7kL/d9rAQL7VwgAnJyDcjCccum3681zpRl7wwm7BWgJq/9D
> jYGTOg162a/MO1nCcJTV+D0jETe4eaLe7QLLbYrhHyjdOoeHk32w9fMmNtrFsDQS
> PnddE8o0xIxEquuabBbY5grx9KWKBoriZvaN6XbBh+kC+GxAQWkZ8P+4WA5NHZCc
> /FbwD/3Nf5C7rZbujgkxLdhaGD+pb9EfE9+fq6WZD8+/avU/Gfm91N1H0a/I5vGf
> OgeErUwBH35iA0Z++cCv7tT7i4stwHAyF12LVnr9uQQE4XtDXAgQjzzeC/eY008b
> iyB0+i3edeR6peCh+MJ7NIn3ptNEilf8jHAfv5WrnCtRM9uSZvJPmQ=> =8CZj
> -----END PGP SIGNATURE-----
>