NO Login failed: generic failure

[Mogens Melander]

Guys, please ..

Can someone please filter out those HTML messages, and only pass the
plain text. Most HTML get sniped on arrival, the rest just annoy me.

I do understand, this guy went a long way to present hi problem, but
inline css, other stuff, will not bring more information.

It's late, and I'm grumpy, but really ?

On Wed, March 26, 2014 17:27, Marc Fournier wrote:
>
> I have two servers, both with identical configurations, right down to
> their imapd.conf files … both use sqlite to store auth information …
>
> Both running on FreeBSD 10.x, and versions of imapd/sasl are the same:
>
> cyrus-imapd24-2.4.17_4/ cyrus-sasl-2.1.26_5
>
> One works great, nary a problem … the other, I get the above message when
> I try and authenticate.  And I can’t find anything different … I’ve
> checked permissions on the various files, etc …
>
> /var/log # telnet localhost imap
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE STARTTLS AUTH=SCRAM-SHA-1
> AUTH=DIGEST-MD5 AUTH=CRAM-MD5 AUTH=LOGIN AUTH=PLAIN SASL-IR] xxx.xxx Cyrus
> IMAP v2.4.17 server ready
> . login xxx at xxx.xxx xxx
> . NO Login failed: generic failure
> . logout
> * BYE LOGOUT received
> . OK Completed
> Connection closed by foreign host.
>
> /var/log/debug.log shows:
>
> ==
> Mar 26 16:09:08 xxx imap[67279]: SQL backend defaulting to engine 'sqlite'
> Mar 26 16:09:08 xxx imap[67279]: executed
> Mar 26 16:09:08 xxx imap[67279]: sql auxprop plugin using sqlite engine
> Mar 26 16:09:08 xxx imap[67279]: IOERROR: opening
> /var/spool/imap/user_deny.db: No such file or directory
> Mar 26 16:09:08 xxx imap[67279]: accepted connection
> Mar 26 16:09:36 xxx imap[67279]: accepted connection
> Mar 26 16:09:49 xxx imap[67279]: sql plugin Parse the username xxx at xxx.xxx
> Mar 26 16:09:49 xxx imap[67279]: sql plugin try and connect to a host
> Mar 26 16:09:49 xxx imap[67279]: sql plugin trying to open db
> '/var/db/sqlite/mailsys' on host ''
> Mar 26 16:09:49 xxx imap[67279]: begin transaction
> Mar 26 16:09:49 xxx imap[67279]: sql plugin create statement from
> userPassword xxx xxx.xxx
> Mar 26 16:09:49 xxx imap[67279]: sql plugin doing query SELECT
> userPassword FROM sasl_auth WHERE userid = 'xxx at xxx.xxx';
> Mar 26 16:09:49 xxx imap[67279]: sql plugin create statement from
> cmusaslsecretPLAIN xxx xxx.xxx
> Mar 26 16:09:49 xxx imap[67279]: sql plugin doing query SELECT
> cmusaslsecretPLAIN FROM sasl_auth WHERE userid = 'xxx at xxx.xxx';
> Mar 26 16:09:49 xxx imap[67279]: sql plugin: no such column:
> cmusaslsecretPLAIN
> Mar 26 16:09:49 xxx imap[67279]: commit transaction
> Mar 26 16:09:49 xxx imap[67279]: sql plugin Parse the username xxx at xxx.xxx
> Mar 26 16:09:49 xxx imap[67279]: sql plugin try and connect to a host
> Mar 26 16:09:49 xxx imap[67279]: sql plugin trying to open db
> '/var/db/sqlite/mailsys' on host ''
>
> /var/log/messages shows:
>
> Mar 26 16:09:49 rdfund imap[67279]: badlogin: xxx [200.46.208.227]
> plaintext xxx at xxx.xxx SASL(-1): generic failure: checkpass failed
>
> I’ve even tried su’ng to the cyrus user and running the sql command
> against the database, and it returns the right database:
>
> % echo "SELECT userPassword FROM sasl_auth WHERE userid = ‘xxx at xxx.xxx';"
> | sqlite /var/db/sqlite/mailsys
> rightPW
> %
>
> I’ve double checked the imapd.conf files, and they are identical except
> different admins: and one has tls_* lines in it … but I’m having the
> identical issue with *another* server, and it doesn’t have the tls_* lines
> …
>
> I figure I have to be overlooking *something* stupid, but I’m at a loss as
> to what it could be … I’ve even checked md5 on imapd between both working
> / non-working … identical …
>
> Is there any way of getting more debug information out of the backend
> without modifying the code itself?
>
> Thanks ...
>

-- 
Mogens Melander
+66 8701 33224

BTW. I would prefere (prefere, not being a proper English word,
substitute with: like ) to receive e-mail in plain text.
Please look for an option, to associate, mail to
me, with plain text. Thank you.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.