Hurray! I've now got sieving on my public folders... It was a little bit
trickier than I thought - but not too bad. I want to test things a bit
more thoroughly and think about the issues a bit first...
Basically, I using a 'security context' of anyone for the filtering...
I'm also working on the
I have quite a large number of shared/public folders to which mail is
sent/posted directly using the [EMAIL PROTECTED] convention.
I want to sieve mail sent to these folders (to remove spam and other
nasties).
Currently (2.0.16 and CVS HEAD) only mail sent to a user's folders is
sieved.
The
On 05 Nov 2001 14:39:44 +,
Ian Castle [EMAIL PROTECTED] (ic) writes:
ic I have quite a large number of shared/public folders to which mail is
ic sent/posted directly using the [EMAIL PROTECTED] convention.
ic I want to sieve mail sent to these folders (to remove spam and other
ic
On Mon, 05 Nov 2001 11:02:59 -0500,
Ken Murchison [EMAIL PROTECTED] (km) writes:
km I don't really remember where we left off. I *think* that Ian's idea is
km what we were talking about -- checking sieveusehomedir==false and if
km postuser!= using postuser as the owner of the script.
When
Amos Gouaux wrote:
On Mon, 05 Nov 2001 11:02:59 -0500,
Ken Murchison [EMAIL PROTECTED] (km) writes:
km I don't really remember where we left off. I *think* that Ian's idea is
km what we were talking about -- checking sieveusehomedir==false and if
km postuser!= using postuser as the
On Mon, 2001-11-05 at 16:02, Ken Murchison wrote:
I don't really remember where we left off. I *think* that Ian's idea is
what we were talking about -- checking sieveusehomedir==false and if
postuser!= using postuser as the owner of the script.
Or maybe having a
Date: Mon, 05 Nov 2001 11:02:59 -0500
From: Ken Murchison [EMAIL PROTECTED]
I don't really remember where we left off. I *think* that Ian's idea is
what we were talking about -- checking sieveusehomedir==false and if
postuser!= using postuser as the owner of the script.
I think
