Thanks for the reply Scott...
Removing the extra lib files has removed the error from auth.log,
however the imapd daemon is still present and as such I cannot
relogin.
Here's the mail.log again with the removed library files:
Dec 28 16:28:31 soapbox cyrus/imapd[22256]: badlogin:
soapbox[127.0.0
Hi JB, I think your problem is you're including plugins you do not need.
If you'd like my 10cents, you should 'rm' the plugins or 'mv' them so
that SASL no longer finds them.
cd /usr/lib/sasl2;ls
desolation ~ # cd /usr/lib/sasl2
desolation sasl2 # ls
libanonymous.la libdigestmd5.la
One last thing I've noted... after logging in succesfully I
noticed that an imapd daemon spawned and stayed alive even when logging
out of cyradm.
When the daemon eventually dies (around a minute) I can then relogin successfully into the server.
I have tested this on another box and the daem
Hello,
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 an option of
Thanks for your reply Andreas,
testsaslauthd works flawlessly everytime. I have indeed have the
"sasl_mech_list: plain login" line in my imapd.conf also...
It's quite strange as it works the first time I start the cyrus server up, and then any subsequent times results in failure.
For instance, h
Hi,
The replication feature available in Cyrus IMAPd 2.3.x is very exciting!
Before starting testing it I would like to know if replication protocol
supports virtual domains?
I also look for solution to allow me to have two email servers - one in
the office and one hosted off the office in a ISP