courier-imap server suddenly not authenticating
This is what I hate about this operating system. Change something, and it doesn't work. Change it back to how it used to work.... and it STILL doesn't fscking work.
I tried to change the listening address for courier-imapd. I edited /etc/courier/imapd. It didn't work for some reason, so I changed it back. Now, suddenly, I can't authenticate. No reason. No error message. Just no service. THANKS A LOT IAMP@!!!?!??! Jan 6 21:42:49 raskolnikov imapd: LOGIN FAILED, user=davek, ip=[::ffff:192.168.1.4] that's it. Anyone else know where THE HELL else to look? It worked with the EXACT same configuration 20 minutes ago, using regular linux authentication (PAM, I think is the term). -dave |
well, I found how to turn on debugging for courier-authdaemon in the config file. Here's what it now says for no reason:
Jan 6 21:59:39 raskolnikov authdaemond: authpam: trying this module Jan 6 21:59:39 raskolnikov authdaemond: authpam: username 'davek@6thstreetradio.org' not found in password file Jan 6 21:59:39 raskolnikov authdaemond: authpam: REJECT - try next module Jan 6 21:59:39 raskolnikov authdaemond: FAIL, all modules rejected ???????????????????????????????????????????????????????????????????????????????????????????????????? ??????/ still have no idea what its doing or whats going wrong |
My guess is that it's trying to authenticate davek@6thstreetradio.org whereas before it was authenticating the user davek. Are you sure nothing else was changed that could have caused this? (or would you expect to find a user davek@6thstreetradio.org?)
|
lost another million hairs over this one. The annoying thing is it was my fault to begin with.
There's a line in /etc/courier/imapd: #DEFDOMAIN="@6thstreetradio.org" I had changed this to 6thstreetradio.org from the default, and uncommented it. I didn't really read the comments around it explaining what it was. I figured "default domain, that's my domain!" But no. Apparently, this part is appended to the username when users try to log in using imap. Add to that the fact that I didn't restart the server when I made the change. Therefore, when I _did_ restart the server, that bug crept in and wasn't found for many many hours. Classic. The moral of the story is don't touch DEFDOMAIN in /etc/courier/imapd unless you have a complex setup where you're serving mail for multiple domains. |
Well, hopefully my comment helped. Another set of eyes and all that
|
All times are GMT -5. The time now is 10:35 AM. |