GSSAPI and replication problem

Cheers all, I tested replication between two computers without problems on FREEBSD 6.2 . Now I tried to move the replica on a good server I got problems with it... Master cannot synchronise on the new replica server. GSSAPI Error: Miscellaneous failure (see text) (No such file or directory) Ju

Re: Emergancy..... db4: PANIC: fatal region error

> On 7/27/07, Simon Matter <[EMAIL PROTECTED]> wrote: >> >> > I have been holding back updating to cyrus 2.2.13 but this afternoon I >> > went >> > ahead and made the major update and really tried to follow ALL the >> points >> > and rules in updating but I really think I messed up the whole system

Re: Emergancy..... db4: PANIC: fatal region error

> I have been holding back updating to cyrus 2.2.13 but this afternoon I > went > ahead and made the major update and really tried to follow ALL the points > and rules in updating but I really think I messed up the whole system now. > I really hope I have not hosed all the email today and have to g

Re: Emergancy..... db4: PANIC: fatal region error

On 7/26/07, eMail Lists <[EMAIL PROTECTED]> wrote: > > I have been holding back updating to cyrus 2.2.13 but this afternoon I > went ahead and made the major update and really tried to follow ALL the > points and rules in updating but I really think I messed up the whole system > now. I really hop

Re: Emergancy..... db4: PANIC: fatal region error

On 7/27/07, Simon Matter <[EMAIL PROTECTED]> wrote: > > > I have been holding back updating to cyrus 2.2.13 but this afternoon I > > went > > ahead and made the major update and really tried to follow ALL the > points > > and rules in updating but I really think I messed up the whole system > now.

cyrdeliver dies with exitcode 65

Hi, I have a problem with a mail, that can't be delivered with cyrdeliver. I need to execute cyrdeliver from procmail, so my procmailrc is: [...] :0w | /usr/sbin/cyrdeliver -r $SENDER $USER I checked the mail that can't be delivered, there is no "^From ". This was the only error I did find on th

Re: User Bulletin implementable with Cyrus

On Thursday 26 July 2007 09:41:13 pm Vincent Fox wrote: > Hello Rick, > > For IMAP users (and clients that support it) there is message of the day > function. > > Example, create one-line bulletin in /var/cyrus/imap/msg/motd > Next time Thunderbird user connects, they should all see message. works

Re: Emergancy..... db4: PANIC: fatal region error

> On 7/27/07, Simon Matter <[EMAIL PROTECTED]> wrote: >> >> > Very nice.. Thank you. It looks like my deliver.db is still a db(x) >> file. >> > Can the files in db/ just be erased and when cyrus starts up it creats >> new >> > files or do the __db* files ned to be converted. I am not sure how to

Re: Emergancy..... db4: PANIC: fatal region error

Well, for one, you would need something along the lines of the following in your imapd.conf file to change over to Skiplist: # File formats annotation_db:skiplist duplicate_db: skiplist mboxkey_db: skiplist mboxlist_db: skiplist quota_db:

Re: Emergancy..... db4: PANIC: fatal region error

On 7/27/07, Frank Richter <[EMAIL PROTECTED] > wrote: [snip] > > Please post the actual imapd.conf and the imapd.conf before the update. > > You have to move the usermailboxes by hand! > > > > > The user dir is not at the location yet. > > > > -Adam > > --

Re: GSSAPI and replication problem

Hi, you can set the allowed mechanism with sasl_mech_list in /etc/imapd.conf Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: Cheers all, I tested replication between two computers without problems on FREEBSD 6.2 . Now I tried to move the replica on a good server I got problems with it... M

Re: Emergancy..... db4: PANIC: fatal region error

On 7/27/07, Simon Matter <[EMAIL PROTECTED]> wrote: > > > On 7/27/07, Simon Matter <[EMAIL PROTECTED]> wrote: > >> > >> > I have been holding back updating to cyrus 2.2.13 but this afternoon > I > >> > went > >> > ahead and made the major update and really tried to follow ALL the > >> points > >> >

Re: Emergancy..... db4: PANIC: fatal region error

> Very nice.. Thank you. It looks like my deliver.db is still a db(x) file. > Can the files in db/ just be erased and when cyrus starts up it creats new > files or do the __db* files ned to be converted. I am not sure how to > tell > if those are db(x) or skiplist. That's something I don't know

Re: Emergancy..... db4: PANIC: fatal region error

On 7/27/07, Simon Matter <[EMAIL PROTECTED]> wrote: > > > Very nice.. Thank you. It looks like my deliver.db is still a db(x) > file. > > Can the files in db/ just be erased and when cyrus starts up it creats > new > > files or do the __db* files ned to be converted. I am not sure how to > > tell

Re: Emergancy..... db4: PANIC: fatal region error

eMail Lists wrote: > > > On 7/27/07, *Simon Matter* <[EMAIL PROTECTED] > > wrote: > > > Very nice.. Thank you. It looks like my deliver.db is still a > db(x) file. > > Can the files in db/ just be erased and when cyrus starts up it > creats new > > fil

Re: Emergancy..... db4: PANIC: fatal region error

I don't know how many users you have, and there might be a cyrus utility for this, I can't recall. The quick and dirty fix is something along the lines of for i in `sudo -u cyrus ./ctl_mboxlist -d | awk -F'\t' '{print $1}' | awk -F'.' '{print $2}' | uniq`; do find /var/spool/cyrus -type d -nam

backend_connect() is broken in 2.3.8

Hi, I'm in the process of upgrading from 2.3.7 to 2.3.8 and I noticed that the sync_client from 2.3.8 can not connect to the replica. After some head scratching I found that while sync_client from 2.3.8 uses the wrong source IP address (the master host has several) when trying to connect to the re

Re: Basic configuration

Simon Matter a écrit : >> Michael Menge a écrit : >> >>> Hi, >>> >>> Wy I can't to use cyradm because it ask me a password ? >>> here may be a Point. >>> >>> 1.) If u use "cyradm -u cyrus localhost" >>> cyradm will ask you for the password of the user cyrus. >>>

Re: backend_connect() is broken in 2.3.8

--On Friday, July 27, 2007 05:50:17 PM +0200 Gabor Gombas <[EMAIL PROTECTED]> wrote: > > It seems that in 2.3.7 backend_connect() contained code to explicitely > set the source IP address but this code was removed in 2.3.8. Why? I asked the developers why the code was there, because on systems w

Re: Emergancy..... db4: PANIC: fatal region error

On Fri, 27 Jul 2007, eMail Lists wrote: > On 7/27/07, Frank Richter <[EMAIL PROTECTED] > wrote: > > [snip] > > >> >> Please post the actual imapd.conf and the imapd.conf before the update. >> >> You have to move the usermailboxes by hand! >> >> >> >>> The user dir is not at the location yet. >>> >

Re: backend_connect() is broken in 2.3.8

On Fri, Jul 27, 2007 at 12:18:14PM -0400, Chaskiel M Grundman wrote: > I asked the developers why the code was there, because on systems where > "servername" points at an alias instead of a single name, the bind tends to > fail and spams the syslog. These extra error messages confused debugging