Hi All
we are planning a migration from 2.15 to 2.3.3 to a new box. Synced over
/var/imap and and ran the conversion for .seen files as suggested in
install-upgrade using cvt_cyrusdb. But all the mail in the inbox on the
new servers are reset to unread. Is there anything else I need to do?
Hi all
I'm experimenting with cyrus 2.2.12 configured to support UNIX namespaces and
virtual domains.
Using cyradm as administrative user I issued:
localhost.localdomain cm group/[EMAIL PROTECTED]
that resulted OK, and mailbox is listed with lm.
localhost.localdomain lam group/[EMAIL
hi,
i´m looking for a strategy to synchronize the primary mailserver to a
backup/fallback server. i´ve read an article about backup strategy in the
cyrus wiki. but is there any other way to do this? e.g. with an internal
component of cyrus?
scenario:
a mail is stored in inbox on primary server.
Hi Phillipe!
Your question is very valid in the first place; a lot of people are looking for
that scenario. (Including one of the sites which I work on right now.)
I think you will have to become clear of some things:
1. An MX is a Mail eXchanger, i.e. Exim, Postfix or the like. The MX does
Torsten Schlabach schrieb:
Does anyone have a redundant IMAP config up and running where failure of a
mailbox server would not mean any service disruption? It might be worth
documenting such a setup in the Cyrus Wiki.
you are searching for heartbeat and drbd
--
Gruß Michael
...der auch
you are searching for heartbeat and drbd
But this will just provide the HA filesystem, won't it?
Isn't there a technology available in Cyrus IMAPd which will replicate
changes to a mailbox to two different servers?
Michael Grundmann schrieb:
Torsten Schlabach schrieb:
Does anyone have a
For those with medium to large scale murders or other glued together
clusters of cyrus servers, what's the general strategy for upgrading?
Do you take downtime for the entire cluster and upgrade, or do you
roll through upgrades of the parts?
The latter would be prudent, except that I
Hi,
A client of mine has come upon what seems to be the limit of mailboxes
for one letter. They use student numbers for mailbox names. When a
mailbox is numerical, Cyrus puts the mailboxes under the letter q in
/var/spool/imap (ex: /var/spool/imap/q/user/12345/ )
My client can't create any
You'll need to upgrade primary and replica backends together for a
2.3.7 to 2.3.8 upgrade. Other than that, you can upgrade just one
backend pair in a 2.3.7 cluster, no problem. Once you have
confidence in the correctness of 2.3.8, upgrade the rest of the
backends. It's also pretty
Torsten Schlabach wrote:
you are searching for heartbeat and drbd
But this will just provide the HA filesystem, won't it?
Isn't there a technology available in Cyrus IMAPd which will replicate
changes to a mailbox
to two different servers?
Search for rolling replication. Though I
you are searching for heartbeat and drbd
But this will just provide the HA filesystem, won't it?
Isn't there a technology available in Cyrus IMAPd which will replicate
changes to a mailbox to two different servers?
Firstly, hello to the list.
drbd is a file system replication program.
Toschi Pietro wrote:
localhost.localdomain cm group/[EMAIL PROTECTED]
that resulted OK, and mailbox is listed with lm.
localhost.localdomain lam group/[EMAIL PROTECTED] returns:
anyone lrs (isn't it strange? I didn't issue any sam command on that
mailbox)
Now I'm wandering what
On Tue, 15 May 2007, ledouxe wrote:
Hi,
A client of mine has come upon what seems to be the limit of mailboxes for
one letter. They use student numbers for mailbox names. When a mailbox is
numerical, Cyrus puts the mailboxes under the letter q in /var/spool/imap
(ex:
Search for rolling replication. Though I failed to get it working
reliably ...
Do you mean this stuff here:
http://nfs-uxsup.csx.cam.ac.uk/~dpc22/cyrus/replication.html
Regards,
Torsten
Ulrich Spoerlein schrieb:
Torsten Schlabach wrote:
you are searching for heartbeat and drbd
But this
The config you would need is to use drbd to mirror the data
directories
Is this officially supported / endorsed?
I learned that Cyrus IMAPd (for whatever reason) is quite picky on
filesystems. From the FAQ:
--- SNIP ---
# Using NFS We don't recommend it. If you want to do it, it may
Torsten Schlabach wrote:
The config you would need is to use drbd to mirror the data
directories
Is this officially supported / endorsed?
Not that I know of but someone else may have a better idea than me
I learned that Cyrus IMAPd (for whatever reason) is quite picky on
filesystems. From
Search for rolling replication. Though I failed to get it working
reliably ...
The only problem with rolling replication is that if you fail over to
the replica and mail gets delivered to it. When you bring the master
back up unless you are carefull (i.e. switch which is master and which
Torsten Schlabach wrote:
The config you would need is to use drbd to mirror the data
directories
Is this officially supported / endorsed?
Not that I know of but someone else may have a better idea than me
I learned that Cyrus IMAPd (for whatever reason) is quite picky on
filesystems.
18 matches
Mail list logo
