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.
-- 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 do
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?
>
> so
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
> 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
Joe Hrbek wrote:
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 fro
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 ca
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 tru
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
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
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
I posted a patch a few weeks ago that allows you to do this Search
the archives...
It is fast enough for my very low volume server ;-).
On Tue, 2001-12-11 at 01:09, Jeremy Howard wrote:
> I'd love to set some site-wide policies using a Sieve script. Is it possible
> to create a Sieve script
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 an
13 matches
Mail list logo