Re: Global Sieve Script

2006-12-15 Thread Luca Olivetti

En/na Federico Sevilla III ha escrit:

Hi,

I would like to create a global sieve script that will be active for
all users, regardless of the presence of a per-user sieve script or not.
This is so that all spam marked by amavis with the X-Spam-Status header
can be segregated into spam folders.


I just configure amavis (actually amavisd-new) to add the spam extension 
($addr_extension_spam = 'spam'), and then give anonymous the p 
permission to the users' spam subfolders (the worst that can happen is 
if someone discovers the trick he can send mail directly to the spam 
folder).


Bye
--
Luca Olivetti
Wetron Automatización S.A. http://www.wetron.es/
Tel. +34 93 5883004  Fax +34 93 5883007

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


Re: Global Sieve Script

2006-12-14 Thread Sebastian Hagedorn
-- Federico Sevilla III [EMAIL PROTECTED] is rumored to have mumbled on 15. 
Dezember 2006 01:44:54 +0800 regarding Global Sieve Script:



I would like to create a global sieve script that will be active for
all users, regardless of the presence of a per-user sieve script or not.


Can't be done.


I have already created and activated a script placed in the global
namespace, but this doesn't seem to be run for all users (actually, it
doesn't seem to be run for any users).

Is my understanding of what a global script is correct?


No.


Or do global
scripts still need to be included


Yes.
--
Sebastian Hagedorn - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
Universität zu Köln / Cologne University - Tel. +49-221-478-5587

pgpfQsMfLSaDE.pgp
Description: PGP signature

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

Re: Global sieve script

2004-10-27 Thread Sascha Wuestemann
On Mon, Oct 25, 2004 at 12:32:26PM -0500 or thereabouts, Adi Linden wrote:
 Is it possible to have a global sieve script, like /etc/procmailrc, which
 is run before any users sieve scripts? If so, where does it live?
 

Hi,

sorry that I can't answer this question I only wanted to mention that I
am very interested in this, too.

One very important example would be this:

placing emails' subject: or to: matching a couple of rules into one shared
folder.

I hope somebody can lighten this darkness :-)

cu
Sascha
-- 
GNU Linux | Opinions are like assholes, everyone's got one, but nobody
2.6.7 | wants to look at the other guy's. -- Hal Hickman  
on a  |  
i586  | 
  | 
  | 
---
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


Re: Global sieve script

2004-10-27 Thread Joe Rhett
On Wed, Oct 27, 2004 at 06:55:01PM +0200, Sascha Wuestemann wrote:
 On Mon, Oct 25, 2004 at 12:32:26PM -0500 or thereabouts, Adi Linden wrote:
  Is it possible to have a global sieve script, like /etc/procmailrc, which
  is run before any users sieve scripts? If so, where does it live?
 
 sorry that I can't answer this question I only wanted to mention that I
 am very interested in this, too.
 
Search the archives.  Rob has documented this a few times.

There's no easy way for users to edit it, but you can do this manually
yourself.

-- 
Joe Rhett
Senior Geek
Meer.net
---
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


Re: global sieve script?

2004-03-05 Thread 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


RE: global sieve script?

2004-03-05 Thread Joe Hrbek
I won't attempt to suggest any ideas to implement a global rule, but I do
have some ideas about the use of such a feature.

The reason I originally asked was to make my life a little easier. :) I have
a group of users, about 250 that are restricted in who they can receive
email from and who they can send email to.  It's easy enough to restrict who
they can email at the mta level, but the rest is more trouble than I'm
willing to put up with, so I use sieve to filter who can receive what.  It
generates more email traffic, but I don't care, we don't have that much
volume.

I wrote some php scripts via php-cyradm that goes through the user mailboxes
and updates the scripts automatically when I make a change, but I thought it
would be awesome to have a file that held a list of mailboxes, and whenever
a message was delivered to that mailbox, do some action.  Of course, taking
priority over whatever script the user had installed in his mailbox.  This
way I only need to edit one file instead of 250. :)

Granted, my scripts work just fine for me, but it could be better. :)

-j

 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


RE: global sieve script?

2004-03-05 Thread Joe Hrbek
 Sounds like the Sieve Include extension is what you want.  You could
 just have each users script include your admin script and go from
 there.  The Include draft is pretty close to being done, and I already
 have an implementation floating around somewhere which will probably get
 put into CVS when the draft os finalized.

That sounds awesome! I'll have to wait for it to get to the stable branch
though.

Thanks! :)

-joe

---
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


Re: global sieve script?

2004-03-04 Thread Sergio Devojno Bruder
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
Sieve scripts are indeed stored in bytecode, compiled, form in Cyrus 2.2.3 
(2.2.2 too? I dont recall), but the capability of a site-side Sieve script.. I 
will be interested in such a beast :)

--
Sergio Devojno Bruder[EMAIL PROTECTED]
http://haxent.com.br  41 362-5930, 41 9127-6620
---
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


Re: Global sieve script

2003-06-20 Thread Rob Siemborski
On Fri, 20 Jun 2003, Ramprasad A Padmanabhan wrote:

 Is it possible to execute in sieve a global script that will be common
 for all mailboxes. The default script for that mailbox should be
 executed after this common script

Not currently.  The sieve spec doesn't define how two scripts should
interact together (especially in cases where, for example, one decides
keep and one decides reject).

There is currently a draft that discusses an include keyword to sieve,
which can make this easier to comprehend, and perhaps possible to
implement.

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper



Re: Global Sieve script?

2001-12-10 Thread Rob Siemborski

On Tue, 11 Dec 2001, Jeremy Howard wrote:

 I guess at the moment that would be kinda slow, because scripts are reparsed
 on every delivery. Has anyone made any progress on that idea of parsing
 scripts once and storing a byte code?

I'm currently working on this, but I probabally won't have anything
finalized for another week or two.

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski | Andrew Systems Group * Cyert Hall 235 * 412-CMU-TREK
   | Cyrus SASL Developer, /usr/contributed Gatekeeper