ions.
>
> - Original Message -
> From: "Hein Roehrig" <[EMAIL PROTECTED]>
> To: "Mike Grommet" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, April 23, 2002 9:06 AM
> Subject: Re: prevention of forwarding loops in
Sorry, my advice/information is based on Cyrus 2.1.3. AFAIK the
duplicate suppression has been there for a long time but possibly not
the configuration option. Probably somebody in the group will comment on
that in a second :-)
Regards,
Hein
On Tue, 2002-04-23 at 16:52, Mike Grommet wrote:
> Is
CTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, April 23, 2002 9:06 AM
Subject: Re: prevention of forwarding loops in sieve
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Cyrus (by default) prevents repeated delivery of the same message by
> storing the message id of inco
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cyrus (by default) prevents repeated delivery of the same message by
storing the message id of incoming messages and discarding any message
with a previously seen id (to the same user.) See duplicatesuppression
in imapd.conf(5)
- -Hein
"Mike Gromme
Mike Grommet wrote:
>
> I'm sure someone has handled this one in the past, so I ask for a canned
> example if possible.
>
> Sieve and Cyrus are happily working together, but reading the sieve rfc, it
> mentions that I need to handle the prevention of fowarding loops...
>
> mailbox1 --> mailbo
I'm sure someone has handled this one in the past, so I ask for a canned
example if possible.
Sieve and Cyrus are happily working together, but reading the sieve rfc, it
mentions that I need to handle the prevention of fowarding loops...
mailbox1 --> mailbox2
but
mailbox2 --> mailbox1
or even
m
