Vincent Fox wrote:
I really don't have a strong enough grasp of Cyrus terminology at this
point. Sorry about that, perhaps duplicate suppression is not the right
term. What I meant was you send a message to 30 inboxes at once, as I
understood it Cyrus only stores one copy and references the other
Ooops, found the correct term I was looking for. "Single instance store" is
what I was intending to ask about.
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
I really don't have a strong enough grasp of Cyrus terminology at this
point. Sorry about that, perhaps duplicate suppression is not the right
term. What I meant was you send a message to 30 inboxes at once, as I
understood it Cyrus only stores one copy and references the other 29. At
least with
Well, I'm guessing here, because I never tried a murder setup.
But as I understand: This feature suppresses duplicate mails to the
_same mailbox_. So I do not see the sense in a duplicate database which
spans over multiple backends. Du you want that if user A on one backend
gets an email and t
