Hello,
I'm hitting this issue too. I'll try to summarize what I think it's happening, please let me know if you disagree.
* With the correct user/password everything works fine.
* If the user does not exists at all, you get a "Login Failed" error. As expected.
* If the user exists and you try to log in an incorrect password the returned error from courier is NOT "Login Failed" as expected. But a temporary server error.
* This incorrect error causes some email clients to get confused and do all kinds of crazy things (Horde) or handle it more nicely (Roundcube) which displays the following error "Connection to storage server failed.".
* This incorrect error WILL confuse the user for sure. The end user should get a nice "Login Failed" message instead of "There is something broken with the server, no idea what" message.
* This problem is caused by the authpsa module, this module is doing it's job but it's not correctly communicating the result back to the courier-authdaemon and so the daemon response is not accurate.
* This should be fixed ASAP.
At the end if this page http://www.courier-mta.org/authlib/README.authdebug.html there is some scarce docs about the process.
My plesk version:
Parallels Plesk Panel v11.5.30_build115130819.13 os_CentOS 6
Error log with DEBUG=2, credentials and names have been modified:
Feb 18 12:09:52 myserver courier-pop3d: Connection, ip=[::ffff:127.0.0.1]
Feb 18 12:09:56 myserver courier-authdaemon: received auth request, service=pop3, authtype=login
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: trying this module
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: authentication request with service='pop3' authtype='login' authdata='[email protected].'
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: auth_psa_common(user='[email protected]', pass='123')
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: password for '[email protected]' is plain '123456'
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: password for account '[email protected]' is wrong
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: sysusername=popuser, sysuserid=110, sysgroupid=31, homedir=<null>, address=<null>, fullname=<null>, maildir=<null>, quota=<null>, options=<null>
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: clearpasswd=<null>, passwd=<null>
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: TEMPFAIL - no more modules will be tried
Feb 18 12:09:56 myserver courier-pop3d: LOGIN FAILED, [email protected], ip=[::ffff:127.0.0.1]
Feb 18 12:09:56 myserver courier-pop3d: authentication error: Input/output error
I'm hitting this issue too. I'll try to summarize what I think it's happening, please let me know if you disagree.
* With the correct user/password everything works fine.
* If the user does not exists at all, you get a "Login Failed" error. As expected.
* If the user exists and you try to log in an incorrect password the returned error from courier is NOT "Login Failed" as expected. But a temporary server error.
* This incorrect error causes some email clients to get confused and do all kinds of crazy things (Horde) or handle it more nicely (Roundcube) which displays the following error "Connection to storage server failed.".
* This incorrect error WILL confuse the user for sure. The end user should get a nice "Login Failed" message instead of "There is something broken with the server, no idea what" message.
* This problem is caused by the authpsa module, this module is doing it's job but it's not correctly communicating the result back to the courier-authdaemon and so the daemon response is not accurate.
* This should be fixed ASAP.
At the end if this page http://www.courier-mta.org/authlib/README.authdebug.html there is some scarce docs about the process.
My plesk version:
Parallels Plesk Panel v11.5.30_build115130819.13 os_CentOS 6
Error log with DEBUG=2, credentials and names have been modified:
Feb 18 12:09:52 myserver courier-pop3d: Connection, ip=[::ffff:127.0.0.1]
Feb 18 12:09:56 myserver courier-authdaemon: received auth request, service=pop3, authtype=login
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: trying this module
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: authentication request with service='pop3' authtype='login' authdata='[email protected].'
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: auth_psa_common(user='[email protected]', pass='123')
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: password for '[email protected]' is plain '123456'
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: password for account '[email protected]' is wrong
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: sysusername=popuser, sysuserid=110, sysgroupid=31, homedir=<null>, address=<null>, fullname=<null>, maildir=<null>, quota=<null>, options=<null>
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: clearpasswd=<null>, passwd=<null>
Feb 18 12:09:56 myserver courier-authdaemon: authpsa: TEMPFAIL - no more modules will be tried
Feb 18 12:09:56 myserver courier-pop3d: LOGIN FAILED, [email protected], ip=[::ffff:127.0.0.1]
Feb 18 12:09:56 myserver courier-pop3d: authentication error: Input/output error