Sieve

[Marc G. Fournier]

IMHO, the biggest thing missing from sieve is the ability to easily use 
anti-spam software like Spamassassin ... but, not sure if I can consider 
that a failing of sieve itself, or the lmtp protocol ... there used to be 
software with Spamassassin called spamcheck.py that acted as an lmtp 
proxy, and altho I'm using it, it doesn't fully handle the error codes 
that lmtp puts out ...

Some sort of 'plug in' for either lmtp, or sieve itself, would be nice, 
that allows for a 'clean' per user filtering ... amavisd is doing a 
quasi-per-user, but as far as I can tell, it only parses/processes the 
message once, so not 100% certain "which user" its basing its rules on ;(



On Mon, 25 Apr 2005, Derrick J Brashear wrote:

> On Mon, 25 Apr 2005, NM Public wrote:
>
>> * I use Tuffmail.com and they support the ManageSIEVE protocol.
>>  I'd like to be able to update my Sieve greenlist (aka
>>  whitelist) from Pine. E.g., In Pine I pipe a message to a
>>  script and the script extracts the From: header and uses
>>  ManageSIEVE to update my remote Sieve script. Where can I find
>>  a ManageSIEVE script that will give me clues about how to do
>>  this? I run Pine on Mac OS X, FreeBSD, and Debian Linux so a
>>  Unix-type shell script would be great. BTW, I know how to
>>  extract the address from the From: header because I've been
>>  doing this for years for my Procmail recipes.
>
> You mean a script that uses the perl modules? We have one around which I just 
> had some fun debugging (there's a debug in the "new protocol" support which 
> we found Thursday, it will be fixed in 2.2.13). I'll find it.
>
>
>> * Is it possible for Sieve to use "include" files so I can
>>  compartmentalize the various sections of my Sieve script? This
>>  seems like it would be especially useful in ensuring that I
>>  don't corrupt my entire Sieve script using the ManageSIEVE
>>  script that I describe above.
>
> No (well, yes, but only starting in 2.3 versions)
>
>> * Are there Sieve syntax checking tools that will tell me if I
>>  have specified exactly the right "require" items?
>
> I know of none.
>
>>  If so, where
>>  can I find them? Does it make much of difference if I specify
>>  more than is needed.
>
> No
>
>> * I've read some Sieve examples on the Web and I don't understand
>>  why some people use 'header :contains' when 'address :all
>>  :comparator "i;ascii-casemap" :contains' seems to be more
>>  correct. Why would someone use 'header' when they are looking
>>  for an 'address'? Is this an example of cluelessness on the
>>  part of the Sieve scripter or is there something I'm not
>>  getting?
>
> Sieve is an evolving language. Some syntax didn't exist at the beginning.
>
> Of course, if you claim to prefer minimalism, why would you explicitly 
> specify the default comparator? ;-)
>
>> * I've seen some recipes that have this:
>> 
>>    fileinto "foo"
>>    stop;
>> 
>>  Is the 'stop;' redundant here? In procmail, delivery means stop
>>  (unless the 'c' flag is used). What's the story in Sieve?
>
> It means no later rules will apply (so you won't have multiple copies filed)
> ---
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>
>

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org           Yahoo!: yscrappy              ICQ: 7615664
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html