global sieve script?

[Earl R Shannon]

Hello,

My two cents worth on how to make it work.

It would have to go through lmtpd twice. Terribly inefficient I'm sure, 
and I'll bet some people are cringing as we read.

The first pass through is for the global sieve script(s). Handled on
a per domain basis, or maybe for the server if you truly want it
to be global, as for say, SPAM filtering or Virus checking, etc.

If it makes it to the second pass it's just normal lmtpd delivery.

There is no interaction per se, but there is a precedence, which
really should go to the global filter, IMHO.

That said, is this really something that postmasters want to start
doing? You are messing with peoples email with a sieve script and
have the potential to delete or redirect email that should be
allowed to go to the user who may then decide. I'd bet that's been
a reason that global filtering hasn't happened yet.

Regards,
Earl Shannon

Edward Rudd wrote:
> nope.. It's not in there.
> Not sure when it will be either, as it's a little more involved than
> just adding it in to cyrus imapd.. one has to figure out how a global
> script will interact with a users local script, including having one
> override another. Which AFAIK is not documented in the RFC..
> 
> On Thu, 2004-03-04 at 17:22, Joe Hrbek wrote:
> 
>>This was posted in reference to a global sieve script:
>>
>>http://www.irbs.net/internet/info-cyrus/0112/0133.html
>>
>>It dates back to 2001.  Is this capability now present in the latest cyrus
>>package?  I use simon matter's RPM.
>>
>>If so, this would be very cool.
>>
>>-j
>>
>>---
>>Home Page: http://asg.web.cmu.edu/cyrus
>>Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
>>List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html