Hi everyone,
simple question: is there a fancy method to migrate all the Cyrus IMAP
mailboxes and databases from a box to a new one?
I'm planning this because the current box is running out of resources
(very bad).
The old box runs cyrus-imapd-2.2.6-5 and db4-4.1.25-8.1 while new one
has cyrus-i
On Thu, 6 Jul 2006, Phil Pennock wrote:
> From: Phil Pennock <[EMAIL PROTECTED]>
> To: info-cyrus@lists.andrew.cmu.edu
> Date: Thu, 6 Jul 2006 02:02:01 +0200
> Subject: Mapping users (either KerberosV or TLS certs)
...
Can't answer any of your questions, which I've deleted. Although
I'm using C
Is anyone running a Cyrus Murder without using Kerberos?
I am trying to build a Murder using DIGEST-MD5 authentication, but I
am running into weird problems and would like to know if it has been
done before. I am particularly keen to know what SASL options are
needed in this environment.
Thanks
On 2006-07-06 at 12:58 +0100, Dennis Davis wrote:
> Can't answer any of your questions, which I've deleted.
:^)
> I can't find a "keytab" option in the imapd.conf manual page.
> There's a srvtab option, but that applies to Kerberos4 which you
> aren't using.
Indeed. All my Kerberos _normal_ acc
Fabio Corazza wrote:
simple question: is there a fancy method to migrate all the Cyrus IMAP
mailboxes and databases from a box to a new one?
Just hot copying the folder /var/spool/imap from the old box to the new
one? And in case, how can I rebuild the databases in /var/lib/imap to
sync with th
David S. Madole wrote:
> My limited experience is that you can simply copy both /var/spool/imap
> and /var/lib/imap to the new machine if you are trying to migrate
> everything.
>
> One way to do this to minimize downtime if you have a lot of data is to
> make a live copy while the old server is s
Hello,
I'm reading here (on the list) a lot about mailboxes file and deliver database
in skiplist format.
What is it exactly and what are the reasons to convert to this format?
What are the steps to make a conversion to skiplist?
Any reference/howtos would be very welcome.
Best Regards,
Leon
On 05 Jul 2006, at 20:02, Phil Pennock wrote:
can anyone
please explain how to configure Cyrus so that a KerberosV /admin
principal can be treated as a Cyrus admin user? I've tried inserting
various entries into sasldb to back this up, putting things into
/etc/krb5.equiv as well as various value
we're running Cyrus 2.2.12 on RHEL3U7. about once a day (typically peak
hours), we have a problem with lmtpd just "hanging":
Jul 6 13:36:27 mail-imap3 lmtpunix[1578]: executed
Jul 6 13:55:08 mail-imap3 lmtpunix[1578]: accepted connection
Jul 6 13:55:08 mail-imap3 lmtpunix[1578]: lmtp connectio
We use PLAIN to authenticate between all the machines in our murder.
What version of Cyrus are you using?
do you have a
sasl_mech_list:
line in your imapd.conf?
Can you auth using imtest and DIGEST-MD5?
Do you support other mechanisms for users?
-Patrick
On Jul 6, 2006, at 8:54 AM, Andrew Fi
On Mon, 2006-07-03 at 22:10 +0800, Wouter van Marle wrote:
> I've a rather peculiar issue. I have a rather large archive of e-mails
> in the cyrus imap format. But due to copy errors while migrating to the
> cyrus server, I now have ended up with many many duplicate e-mails. And
> I'd like to take
On Thu, Jul 06, 2006 at 11:43:50AM -0400, Patrick Radtke wrote:
> We use PLAIN to authenticate between all the machines in our murder.
That is very interesting. I found that I had to enable MD5 because
the backends (and mupdate?) would not accept lower-strength
authentication. PLAIN would be pref
On Thu, 6 Jul 2006 17:36 , Kjetil Torgrim Homme <[EMAIL PROTECTED]> said:
>we're running Cyrus 2.2.12 on RHEL3U7. about once a day (typically peak
>hours), we have a problem with lmtpd just "hanging":
>
>Jul 6 13:36:27 mail-imap3 lmtpunix[1578]: executed
>Jul 6 13:55:08 mail-imap3 lmtpunix[1578
I haven't tried it with 2.3.6, but PLAIN should work.
I would suggest starting with
sasl_mech_list: PLAIN
in all your imapd.conf files (make sure it says only PLAIN).
and make sure there is no
force_sasl_client_mech
lines anywhere.
Then make sure you can use imtest (with -m PLAIN and -t "" (
On Thu, 2006-07-06 at 20:53 +0100, Alan Thew wrote:
> On Thu, 6 Jul 2006 17:36 , Kjetil Torgrim Homme <[EMAIL PROTECTED]> said:
> >we're running Cyrus 2.2.12 on RHEL3U7. about once a day (typically peak
> >hours), we have a problem with lmtpd just "hanging":
> >
> >Jul 6 13:36:27 mail-imap3 lmtpu
I was tracking a very similar issue with xfer between 2.2 and 2.3.6.
xfer'ing vanilla 2.2.12 mailboxes to 2.3.6 seems to work fine, and
xfer'ing a 2.3.6 mailbox to 2.2.12 also more or less works
(permissions are broken since 2.3.6 blindly uses rfc 4314 ACLs rather
than paying attention to
On 05 Jul 2006, at 02:54, Bron Gondwana wrote:
If you're running replication on any post 2.3.3 cyrus, your replica
contains indexes with '0' as the modseq value. This means that your
messages will not be fetchable until you either fix that value or
patch Cyrus. Reconstruct from 2.3.6+ is one o
Is it possible to run cyrus 2.2 on Debian Etch with LDAP auth and allow
something other than plaintext auth methods? I am using saslauthd (thus
limiting myself to plaintext), but I see something called pts in the
imapd.conf man page that seems to be able to use ldap. However, I am not
really su
Looks like that changes the replication protocol incompatibly, so
deployments need to update both replicas and primaries at the same time.
:wes
On 06 Jul 2006, at 17:17, David S. Madole wrote:
I submitted a patch that does actually replicate the modseq value,
although unfortunately my first e
On Thu, 6 Jul 2006 16:56:45 -0400, "Wesley Craig" <[EMAIL PROTECTED]> said:
> I was tracking a very similar issue with xfer between 2.2 and 2.3.6.
> xfer'ing vanilla 2.2.12 mailboxes to 2.3.6 seems to work fine, and
> xfer'ing a 2.3.6 mailbox to 2.2.12 also more or less works
> (permissions
On Thu, 06 Jul 2006 17:17:39 -0400, "David S. Madole" <[EMAIL PROTECTED]> said:
> On 05 Jul 2006, at 02:54, Bron Gondwana wrote:
>
> >If you're running replication on any post 2.3.3 cyrus, your replica
> >contains indexes with '0' as the modseq value. This means that your
> >messages will not be
Bron Gondwana wrote:
One downside of your patch - it changes the network protocol of
replication so that 2.3.6 and 2.3.7 won't be able to replicate
to each other in either direction - you'll have to upgrade both
your machines at once.
I considered that and thought about making it compatible, b
22 matches
Mail list logo