Re: NO Login failed: generic failure

2014-03-26 Thread Mogens Melander
Marc, On Wed, March 26, 2014 22:04, Marc Fournier wrote: > > On Mar 26, 2014, at 12:54 , Marc Fournier wrote: > >> Mar 26 19:47:17 xxx imap[1448]: Could not open db >> Mar 26 19:47:17 xxx imap[1448]: sql plugin Parse the username >> sa...@xxx.info >> Mar 26 19:47:17 xxx imap[1448]: sql plugin doi

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
On Mar 26, 2014, at 16:27 , Mogens Melander wrote: > Dude, check again: > > > In your login, cmusaslsecretPLAIN coloumn is missing ?? Already fixed the issue … had nothing to do with the SQL query … for some reason, even with auxprop set to sql, its trying to access sasldb2.db, whch didn’t

Re: NO Login failed: generic failure

2014-03-26 Thread Mogens Melander
Dude, check again: In your login, cmusaslsecretPLAIN coloumn is missing ?? On Wed, March 26, 2014 19:05, Marc Fournier wrote: > > Yes, they are all the same … data isn’t, obvously, but the structure > hasn’t changed … in fact, the mail systems on all three servers that I’m > currently working wi

Re: NO Login failed: generic failure

2014-03-26 Thread Mogens Melander
You got your answer in: sql plugin: no such column: cmusaslsecretPLAIN I've been there.. Edit your SQL to match your DB layout. 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

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
On Mar 26, 2014, at 16:15 , Mogens Melander wrote: > 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

Re: NO Login failed: generic failure

2014-03-26 Thread 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

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
On Mar 26, 2014, at 14:40 , Dan White wrote: > 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 > confirm). Hrmmm … this is all ‘pluginviewer -a’ shows … shouldn’t sql be listed? Installed and pr

Re: NO Login failed: generic failure

2014-03-26 Thread Dan White
On 03/26/14 11:45 -0700, Marc Fournier wrote: > >On Mar 26, 2014, at 11:25 , Dan White 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

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
On Mar 26, 2014, at 12:54 , Marc Fournier wrote: > > > Mar 26 19:47:17 xxx imap[1448]: Could not open db > Mar 26 19:47:17 xxx imap[1448]: sql plugin Parse the username sa...@xxx.info > Mar 26 19:47:17 xxx imap[1448]: sql plugin try and connect to a host > Mar 26 19:47:17 xxx imap[1448]: sql

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
On Mar 26, 2014, at 12:54 , Marc Fournier wrote: > But, if it can’t open the db (or is that for a different db?), then how does > it know that the first query works fine, but the second one is missing a > column? It has to open the db to do that … unless, again, the ‘Could not > open’ is try

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
On Mar 26, 2014, at 11:25 , Dan White wrote: >> > > Add 'sasl_log_level: 7' to imapd.conf, and verify your syslog daemon is > logging 'auth.*’. With sasl_log_level set to 7, master restarted: Mar 26 19:47:17 xxx imap[1448]: Could not open db Mar 26 19:47:17 xxx imap[1448]: sql plugin Parse

Re: NO Login failed: generic failure

2014-03-26 Thread Dan White
On 03/26/14 11:45 -0700, Marc Fournier wrote: > >On Mar 26, 2014, at 11:25 , Dan White wrote: > >> >> What does your imapd.conf config look like? In particular the sasl_*, >> virtdomain, defaultdomain, allowplaintext, and loginrealms options. > > >configdirectory: /var/spool/imap >partition-defaul

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
On Mar 26, 2014, at 11:25 , Dan White 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: /v

Re: NO Login failed: generic failure

2014-03-26 Thread Dan White
On 03/26/14 09:27 -0700, Marc Fournier wrote: >cyrus-imapd24-2.4.17_4/ cyrus-sasl-2.1.26_5 >/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

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
Yes, they are all the same … data isn’t, obvously, but the structure hasn’t changed … in fact, the mail systems on all three servers that I’m currently working with have been running / configured for 5+ years now … only change was upgraded OS from FreeBSD 9 -> 10 and upgraded ports to the lates

Re: NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
Never has been, nor is there on the working system … I don’t even know where that query is coming from, as my imapd.conf has: pwcheck_method: auxprop auxprop_plugin: sql sasl_sql_engine: sqlite sasl_sql_database: /var/db/sqlite/mailsys sasl_sql_select: SELECT %p FROM sasl_auth WHERE userid = '%

NO Login failed: generic failure

2014-03-26 Thread Marc Fournier
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 ot

problem with xfer from 2.3.15 to 2.4.17

2014-03-26 Thread gavin . gray
Hi there, We are have been running a cyrus imap 2.3.15 murder for some time, we have intoduced some new cyrus 2.4.17 backends into that murder and would like to migrate users to these new machines, however xfer's are failing for this reason: Mar 24 12:16:22 backend.server imap[2370]: [ID 16098

Re: Outlook 2013

2014-03-26 Thread Vladislav Kurz
Hi all, I have a customer with Outlook 2013. A year ago I have upgraded their cyrus and put the XList options in imapd.conf: ## XLIST xlist-archive: Archive xlist-drafts: Drafts xlist-junk: Junk xlist-sent: Sent xlist-trash: Deleted They upgraded to outlook2013 themselves later so I asked about