Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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).
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
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.