Re: replication and db files

2005-12-29 Thread Ken Murchison
Patrice wrote: Hello, I would like to know that if I use replication mecanism with cyrus-imap 2.3.1 should I have to worry about db files( seen.db, mailboxes.db, deliver.db ...) and sieve scripts No. All *necessary* dbs are handled by the replication code. deliver.db and tls_sessions.db ar

Re: Upgrading from v1.5.19 to v2.3.x

2005-12-29 Thread Ken Murchison
Rosenbaum, Larry M. wrote: We are currently running Cyrus IMAP v1.5.19 on Solaris 6, which has not been upgraded because I thought the server would be going away soon. I have recently found out that it is not going away, and that we are moving it to new and better hardware (and Solaris 9), so th

Re: Global admin fails via saslauthd and ldap

2005-12-29 Thread imap
> >> We have the following set in the imapd.conf for 2.3.1 install: > >> virtdomains: on > >> admins: globaladmin [EMAIL PROTECTED] > >> defaultdomain: xyz.com > >> > >> and in saslauthd.conf: > >> ldap_default_realm: xyz.com > >> > >> Following cyradm logins fail for the 'globaladmin', whether or

Re: Global admin fails via saslauthd and ldap

2005-12-29 Thread Igor Brezac
On Thu, 29 Dec 2005 [EMAIL PROTECTED] wrote: We have the following set in the imapd.conf for 2.3.1 install: virtdomains: on admins: globaladmin [EMAIL PROTECTED] defaultdomain: xyz.com and in saslauthd.conf: ldap_default_realm: xyz.com Following cyradm logins fail for the 'globaladmin', whethe

Re: Cyrus IMAP cluster

2005-12-29 Thread Mathieu Arnold
+-Le 29/12/2005 14:52 -0500, Dave McMurtrie a dit : | Nikola Milutinovic wrote: | |> |> Are we talking about cyrus murder? I'll definitely take a look. | | He's actually talking about the replication code that David Carter wrote. | Murder only offers scalability, and does not give you any type

Re: Global admin fails via saslauthd and ldap

2005-12-29 Thread imap
> We have the following set in the imapd.conf for 2.3.1 install: > virtdomains: on > admins: globaladmin [EMAIL PROTECTED] > defaultdomain: xyz.com > > and in saslauthd.conf: > ldap_default_realm: xyz.com > > Following cyradm logins fail for the 'globaladmin', whether or not > FQDN is passed as a

Re: Cyrus IMAP cluster

2005-12-29 Thread Nikola Milutinovic
Igor Brezac wrote: On Wed, 28 Dec 2005, Nikola Milutinovic wrote: Hello all. How would one go about building a Cyrus cluster? Suppose you wanted to make two servers a failover IMAP cluster. The way I imagine it, the MTA can forward messages to two servers. Problem is, deleting from one se

Re: Cyrus IMAP cluster

2005-12-29 Thread Dave McMurtrie
Nikola Milutinovic wrote: Are we talking about cyrus murder? I'll definitely take a look. He's actually talking about the replication code that David Carter wrote. Murder only offers scalability, and does not give you any type of replication of the backend mailstore. Thanks, Dave C

Upgrading from v1.5.19 to v2.3.x

2005-12-29 Thread Rosenbaum, Larry M.
We are currently running Cyrus IMAP v1.5.19 on Solaris 6, which has not been upgraded because I thought the server would be going away soon. I have recently found out that it is not going away, and that we are moving it to new and better hardware (and Solaris 9), so this would be an excellent time

solution to "sasldb2: permission denied" issue on Fedora

2005-12-29 Thread Edward Zarecor
If you are running Fedora and having problems with getting auxprop/sasldb to work, the issue may be selinux -- I believe this is a default install option since FC3? If you see the following message: Dec 29 10:43:13 example.com imap[24170]: unable to open Berkeley db /etc/sasldb2: Permission d

Re: Cyrus IMAP cluster

2005-12-29 Thread Sven Mueller
Nikola Milutinovic schrieb: > How would one go about building a Cyrus cluster? > > Suppose you wanted to make two servers a failover IMAP cluster. The way > I imagine it, the MTA can forward messages to two servers. Problem is, > deleting from one server will not reflect on the other. I'd like to