Re: Problems with murder on debian

On 02/07/10 20:55 -0400, Oscar Nuñez wrote: >Hi folks, > >I have an Cyrus murder (on Debian Lenny) that is very small: 1 mupdate, 1 >frontend and 1 backend. > >The backend and mupdate is ok. The problem is the frontend. Are you using the stock Debian versions or something different? >When I try t

Problems with murder on debian

Hi folks, I have an Cyrus murder (on Debian Lenny) that is very small: 1 mupdate, 1 frontend and 1 backend. The backend and mupdate is ok. The problem is the frontend. When I try to access through SELECT INBOX to a user account from frontend to backend the follow error appear: . NO Server(s) una

Re: Benachrichtung zum Übe rmittlungsstatus (Fehlgeschlagen)

On 02/07/10 14:43 -0300, D G Teed wrote: >2010/7/2 D G Teed >> Subject: Authentication problems since Redhat 5.5 updates >>> >>> We had a nice trouble free cyrus running until it was updated with >>> updates from Redhat today. >>> >>> I've tested with testsaslauthd (no service name given) and it w

Re: migrating Cyrus IMAPd from i386 to amd64 system

Jukka Salmi --> info-cyrus (2010-06-25 02:30:49 +0200): > Hi > > I'm currently running Cyrus IMAPd 2.2.13p1 on NetBSD/i386 without any > problems. During the next few days I need to move the users' mailboxes > to a NetBSD/amd64 system which will run Cyrus IMAPd 2.3.16. Some hints > about this wo

Re: Benachrichtung zum Übermittlungsstatus (Fehlges chlagen)

2010/7/2 D G Teed > > > Subject: Authentication problems since Redhat 5.5 updates >> >> We had a nice trouble free cyrus running until it was updated >> with updates from Redhat today. >> >> I've tested with testsaslauthd (no service name given) and it works OK, >> so I'd think things are fine on

Authentication problems since Redhat 5.5 updates

We had a nice trouble free cyrus running until it was updated with updates from Redhat today. I've tested with testsaslauthd (no service name given) and it works OK, so I'd think things are fine on the pam, AD and ldap end. In the cyrus server's maillog I'm seeing messages like this from attempts

Re: mupdate cpu, thread timeouts

>> Jul 1 15:16:51 imap mupdate[18204]: Thread timed out waiting for >> listener_lock >> Jul 1 15:16:51 imap mupdate[18204]: Worker thread finished, for a >> total >> of 2 (2 spare) >> Jul 1 15:16:52 imap mupdate[18206]: New worker thread started, for a >> total of 3 >> Jul 1 15:16:52 imap mupda