Bernhard - thank you very much I good it.
12 hours hard work to catch the solution.
tomorrow I will write a small how to.
thx!!!
--On Montag, Juli 21, 2003 02:13:26 +0200 Manfred Friedrich
<[EMAIL PROTECTED]> wrote:
Hi,
now the fog is a litle bit gone a way. :-)
[EMAIL PROTECTED] be]$ /opt/
Hi,
now the fog is a litle bit gone a way. :-)
[EMAIL PROTECTED] be]$ /opt/cyrus/bin/sieveshell localhost
connecting to localhost
Please enter your password:
> put .sieve default
> activate default
> list
default <- active script
> quit
Ok I have done this. so now there is a new directory /v
In the moment I'm not shure witch the better solution. So let's talk
about both.
Mainly, it depends on if your Cyrus users have shell logins to the same
box the Cyrus server is running on or if Cyrus acts as a "sealed server".
Ok fine, but I have a .sieve file in $home
-rwxr-xr-x1 mf ma
Hi,
Thank you bernhard.
In the moment I'm not shure witch the better solution. So let's talk
about both.
> a) ~/.sieve and "sieveusehomedir: true": each user can modify his own
> sieve script, no need for using timsieved to upload them to the cyrus
> server, ~/.sieve must be readable for the c
