-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 16 Jan 2015, Cliff Hayes wrote:
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
I fixed it by moving the directory from the recommended
/var/lib/dovecot/sieve/after.d/
to
/tmp
If that is not the recommended resolution, please advise.
On 1/16/2015 12:45 PM, Cliff Hayes wrote:
Thanks.
That's exactly what I needed.
However I have a permission problem.
I added the parameter to
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/0JHtauVQfPgA
-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 appli
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-sp
