| From | Sent On | Attachments |
|---|---|---|
| Kevin Murphy | Feb 18, 2007 11:40 am | |
| Sam Varshavchik | Feb 18, 2007 3:16 pm | |
| Kevin Murphy | Feb 18, 2007 5:47 pm | |
| Sam Varshavchik | Feb 18, 2007 6:13 pm | |
| Kevin Murphy | Feb 18, 2007 6:25 pm |
| Subject: | Re: [courier-users] chdir: permission denied with MySQL Auth backend | |
|---|---|---|
| From: | Sam Varshavchik (mrs...@courier-mta.com) | |
| Date: | Feb 18, 2007 3:16:58 pm | |
| List: | net.sourceforge.lists.courier-users | |
Kevin Murphy writes:
Hello,
I built and installed courier 0.54.2 RPMs on Fedora Core 6. I then setup the authentication system to use MySQL, and setup a virtual domain with the maildirs living in /home/mail/[domain.com]/[username]
I created a courier user (503) and a courier group (503), chowned the entire /home/mail structure to courier:courier. I also configured the record in the passwd table for uid=503 and gid=503. Despite all of this, when I attempt to login to any of these accounts, I get the following entries in the log:
Feb 18 14:08:27 mountaineer imapd: Connection, ip=[::ffff:<filtered IP address>] Feb 18 14:08:31 mountaineer imapd: kev...@bumpahead.net: chdir(/home/mail/<filtered domain name>/kevin) failed!! Feb 18 14:08:31 mountaineer imapd: error: Permission denied Feb 18 14:08:31 mountaineer imapd: LOGIN FAILED, user=kevin@<filtered domain name>, ip=[::ffff:<filtered IP address>] Feb 18 14:08:31 mountaineer imapd: authentication error: Permission denied
I have filtered out the IP address and domain, but rest assured that I have verified that the paths exist as configured, and the permissions are appropriate.
What on earth could I be missing?
You're missing any indication that your authentication database is set up correctly. You paraphrased how you think you've set up your mysql-based authentication, but you did not post your actual authentication data. There's a likely disconnect between what you think has happened, and what actually happened.
Use the authtest utility in the courier-authlib package to verify that your authentication configuration is set up properly.





