AW: sieve - does not work

Manfred Friedrich m.friedrich at t-o-c.biz
Sun Jul 20 20:45:12 EDT 2003


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 
<m.friedrich at t-o-c.biz> wrote:

> Hi,
>
> now the fog is a litle bit gone a way. :-)
>
>> [be at ente 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 /var/lib/sieve/m/mf
> within my script:
>
> ---
> require "fileinto";
> require "reject";
> require "vacation";
> require "regex";
>
> if header :contains "Subject" "test" {
>     reject "No spam please";
> }
>
> ---
>
> So I send a testmail  with the Subject test but sieve does nothing! The
> mail is normal delifered.  Also the logfile has no sieve entry?
>
>
>
>
>
> --On Sonntag, Juli 20, 2003 23:38:38 +0200 Bernhard Erdmann
> <be at berdmann.de> wrote:
>
>>> 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-x    1 mf       mail          209 2003-07-21 00:56 .sieve
>>
>> That's not enough for ~/.sieve being readable by the cyrus user. Your
>> $HOME and all the directories in the path above have to be accessible for
>> the cyrus user, too. And there is no need for .sieve being executable.
>>
>>> How do I tell the system that sieve should not use timsieved?
>>
>> By stating "sieveusehomedir: true". Cyrus will look in your $HOME for
>> sieve scripts and if someone tries to use timsieved, it will refuse to
>> work. In addition, you should disable sieve/timsieved in /etc/cyrus.conf.
>>
>>> How do the user store the scripts in the cyrus server?
>>
>> By means of sieveshell:
>>
>> [be at ente be]$ /opt/cyrus/bin/sieveshell localhost
>> connecting to localhost
>> Please enter your password:
>>  > put .sieve default
>>  > activate default
>>  > list
>> default  <- active script
>>  > quit
>> [be at ente be]$
>>
>>
>
>
>
>
>








More information about the Info-cyrus mailing list