Ken Murchison wrote:
Sergio Devojno Bruder wrote:
Attila Nagy wrote:
Hello,
(...) The unified approach seems to be simple. The client no longer
has to be redirected to the given backend using the proxyd, or
lmtpproxyd (previously called frontend), instead it can turn to any
of the backends and t
Sergio Devojno Bruder wrote:
Attila Nagy wrote:
Hello,
(...) The unified approach seems to be simple. The client no longer
has to be redirected to the given backend using the proxyd, or
lmtpproxyd (previously called frontend), instead it can turn to any of
the backends and the backend will know
Attila Nagy wrote:
Hello,
(...)
The unified approach seems to be simple. The client no longer has to be
redirected to the given backend using the proxyd, or lmtpproxyd
(previously called frontend), instead it can turn to any of the backends
and the backend will know how to deal with that connec
Thomas Vogt wrote:
Am Mittwoch, den 03.11.2004, 16:20 -0500 schrieb Ken Murchison:
IMAP2, so IMAP3 can't access mailboxes on STOR1. Does this work?
No. You're talking about two levels of synchronization here, the
current Murder code only handles the following scenarios.
Standard/Unified Murder:
Attila Nagy wrote:
Ken Murchison wrote:
In a standard config, the mailboxes.db on each IMAP server only
contains In a unified config, the master mailboxes.db is located on
the MUPDATE In a replicated config, the master mailboxes.db is located
on the
Thanks a lot, this enlightened my mind.
Repli
Thomas Vogt wrote:
{mail.domain.com}
+-+ +-+ +-+ +-+
|IMAP1| |IMAP2| |IMAP3| |IMAP4|
+--+--+ +--+--+ +--+--+ +--+--+
||||
+--+--+ +--+--+ +--+--+ +--+--+
|STOR1| |STOR2| |STOR3| |STOR4|
+-+ +-+ +-+ +-+
Lets say,
Ken Murchison wrote:
In a standard config, the mailboxes.db on each IMAP server only contains
In a unified config, the master mailboxes.db is located on the MUPDATE
In a replicated config, the master mailboxes.db is located on the
Thanks a lot, this enlightened my mind.
Replicated Murder seems t
Am Mittwoch, den 03.11.2004, 16:20 -0500 schrieb Ken Murchison:
> > IMAP2, so IMAP3 can't access mailboxes on STOR1. Does this work?
>
> No. You're talking about two levels of synchronization here, the
> current Murder code only handles the following scenarios.
>
>
> Standard/Unified Murder:
>
Attila Nagy wrote:
Ken Murchison wrote:
Is replicated murder consists of multiple backend server groups which
has the same mailboxes? So murder will say that user.jsmith is on
server1 AND server2, instead of just saying it's on server1 OR server2?
Yes. Any machine in the Murder has local access
Ken Murchison wrote:
Is replicated murder consists of multiple backend server groups which
has the same mailboxes? So murder will say that user.jsmith is on
server1 AND server2, instead of just saying it's on server1 OR server2?
Yes. Any machine in the Murder has local access to any mailbox.
Hmm
Attila Nagy wrote:
Hello,
There are the following lines in the changelog:
"Added support for "unified" and "replicated" Murders. A Murder no
longer has to have discrete frontend and backend servers; any one
"unified" server can both proxy and serve local mailboxes (proxy
functionality in proxyd
Hello,
There are the following lines in the changelog:
"Added support for "unified" and "replicated" Murders. A Murder no
longer has to have discrete frontend and backend servers; any one
"unified" server can both proxy and serve local mailboxes (proxy
functionality in proxyd and lmtpproxyd has
12 matches
Mail list logo