NO Login failed: generic failure

Dan White dwhite at
Wed Mar 26 17:40:40 EDT 2014

On 03/26/14 11:45 -0700, Marc Fournier wrote:
>On Mar 26, 2014, at 11:25 , Dan White <dwhite at> wrote:
>> What does your imapd.conf config look like? In particular the sasl_*,
>> virtdomain, defaultdomain, allowplaintext, and loginrealms options.
>configdirectory: /var/spool/imap
>partition-default: /var/spool/mail
>duplicatesuppression: 1
>sievedir: /var/spool/sieve
>sendmail: /usr/sbin/sendmail
>hashimapspool: yes
>lmtpsocket: /var/run/socket/lmtp
>unixhierarchysep: 0
>quotawarn: 90
>virtdomains: 1
>allowplaintext: 1
>pwcheck_method: auxprop
>auxprop_plugin: sql

This *should* prevent sasldb from initializing.

On 03/26/14 14:04 -0700, Marc Fournier wrote:
>‘k, think I got it … tracing “Could not open db” to where it is in the
>code, turns out it is generated by cyrus-sasl -> sasldb -> db_ndbm.c …
>but, we don’t *use* sasldb, so why is that error being generated?
>Looking on my ‘working system’, there is a /usr/local/etc/sasldb2.db file
>there, which is why that error isn’t being  generated … so, I just created
>a ‘dummy’ sasldb2.db file on both of my non-workign systems, and suddenly,
>it looks like everything is authenticating properly …
>Still have to do more testing but … is there some way to *disable* it
>checking for that file?  I created and then disabled an account in it, so
>that its got the right structure, so its not too painful of a solution,
>just not sure why it came up in the first place … when I upgraded the
>code, the version of cyrus-sasl didn’t change (2.1.16 in both the pre and
>post upgrade systems, just confirmed), but cyrus-imap went from 2.3 -> 2.4
>… so a stricter requirement in 2.4 that I hadn’t seen before … ?

If your cyrus sasl was compiled as shared libraries, you can delete the
library from your disk to prevent it from loading (pluginviewer -a should

Dan White

More information about the Info-cyrus mailing list