>>>>> On Wed, 30 May 2001 11:11:41 -0400,
>>>>> Jen Wu <[EMAIL PROTECTED]> (jw) writes:
jw> I read in "Managing IMAP" that Cyrus can be configured to keep
jw> only one copy of a message that would otherwise be duplicated
jw> many times. For example, if 10 people are on the same mailing
jw> list, only one copy of each mailing list message would be kept.
jw> How does this work? And how well does it work? The book said
jw> that Sieve was involved, but I'm not sure why that would be the
jw> case. For example, if someone copies a message from one
jw> folder to another, that would result in a duplicate message, too,
jw> and Sieve wouldn't be able to handle that, would it?
you might check in the doc directory:
$ grep -i 'duplicate delivery' *
changes.html: <li> The duplicate delivery database expiration (deliver -E) was
changes.html: <li> Fixed bugs in deliver relating to duplicate delivery
changes.html: <li> deliver now will not use Sieve if duplicate delivery
changes.html: duplicate delivery database to be checked even if dupelim was
changes.html: <li> Duplicate delivery changes:
changes.html: Split out duplicate delivery elimination to multiple
changes.html: directory, nothing bad will happen (other than duplicate delivery
changes.html:<li>Redo duplicate delivery elimination in <tt>deliver</tt>.
install-perf.html:duplicate delivery suppression, each time a mail message is delivered
install-upgrade.html:<li>Create some extra directories and remove the duplicate
delivery
install-upgrade.html:<p>Duplicate delivery suppression is now required for Sieve.
overview.html:<li><a href="#duplicate">Duplicate Delivery Suppression</a>
overview.html:<LI><TT>INFO</TT> - Mailbox openings, duplicate delivery suppression
overview.html:<h3>Duplicate Delivery Suppression</h3><a name="duplicate"></a>
--
Amos
