Webmail, IMAP, POP logins fail

[elleryjh]

This is a new server, with a fresh instlal of cP 10 stable, then upgraded to cP 11. I'm not sure if this problem existed before the upgrade.

Logins to POP and IMAP fail.

A brand new POP account created in cPanel:

Following POP email account was added:
test@xxx.net
(Quota: 20 MB)

Setup your email client using following information:

POP Account: test+xxx.net
Password: test

Logins to POP and IMAP (and webmail -> IMAP) both fail:

Jun 22 05:17:21 l5 pop3d: LOGIN FAILED, user=test+xxx.net, ip=[::ffff:xxx.xxx.xxx.xxx]
...
Jun 22 10:04:34 l5 imapd: LOGIN FAILED, user=test1@xxx.net, ip=[::ffff:127.0.0.1]
Jun 22 10:04:44 l5 imapd: LOGIN FAILED, user=test1+xxx.net, ip=[::ffff:127.0.0.1]
Jun 22 10:04:49 l5 imapd: LOGOUT, ip=[::ffff:127.0.0.1]

This happens for every account (accounts' main mail account, and their created POP accounts).
Logging into webmail, the initial webmail selection and options screen is available. That means the passwords are set correctly. Just IMAP and POP are broken...

Anyone?

[vladi2n]

I have the same problem on new CP11 server.

When I try to login with Hord error:

Notice: Unknown(): Login failed. (errflg=1) in Unknown on line 0
Notice: Unknown(): Login failed. (errflg=1) in Unknown on line 0
Notice: Unknown(): Login failed. (errflg=1) in Unknown on line 0
Notice: Unknown(): Too many login failures (errflg=2) in Unknown on line 0

[cPanelMatt]

vlad, the problem you described is normally what happens when you try to log in to horde after switching to a cpanel account from WHM. If that isn't it, the best I can say is to open a support ticket.

As for you elleryjh, I would try doing a forced reinstall of courier (/scritps/courierup --force), what it looks like to me is that courier is not able to authenticate the accounts for one of several different reasons. If it doesn't work, please open a support ticket and one of the support techs here would be more than happy to look into this for you.

[elleryjh]

Thanks Matt, reinstalling courier worked perfectly.

[vladi2n]

Thanks it works perfectly now

[cev]

Thanks Matt, reinstalling courier worked perfectly.

I had the same problem, reinstalling wouldn't be necessary, restarting of courier is good enough.

[masterpeg]

vlad, the problem you described is normally what happens when you try to log in to horde after switching to a cpanel account from WHM. If that isn't it, the best I can say is to open a support ticket.

As for you elleryjh, I would try doing a forced reinstall of courier (/scritps/courierup --force), what it looks like to me is that courier is not able to authenticate the accounts for one of several different reasons. If it doesn't work, please open a support ticket and one of the support techs here would be more than happy to look into this for you.

hi,

am new and would like to ask how to " I would try doing a forced reinstall of courier (/scritps/courierup --force)," do this.

could you tell me how? tnx

regards

[cPanelMatt]

masterpeg, just login to your server via SSH as root and run:

/scripts/courierup --force

[nathacof]

/etc/init.d/courier-authlib restart

Worked for me and other's who have posted similar topics.

[OliverH]

*sigh* This is ridiculous, but it does work. (WHY!?)

After banging my head against the wall for a couple of hours I found this. Reinstalling Courier and restarting both courier-related services made it work.

[mambovince]

Hi,
Same problem for me too, no idea how it happened but maybe a common issue with latest stable tree?

I also used:
/etc/init.d/courier-authlib restart

Regards,

- Vince

[gribozavr]

I can also confirm it. Same login problems here, and restarting courier-authlib helped.

11.10.0-R16448, fresh installation.

[barnone]

same thing happened here i was going crazy trying to figure it out. restarting courier worked.

[searcher1]

Now this might sound also amazing etc. I followed the thread(s) on all this because I've had exactly the same problems. Having done the 'force' and 'restart' and taken into account a while ago that 'courier' was a problem I must have missed something! Some accounts worked fine but others simply failed even after all the time spent of doing what's been suggested.

I then chose 'Configure Outlook' in cPanel (BTW slowly I'm moving personally over to using it as my current mailer is called 'Turnpike' which I've used from it s conception). I missed the important detail .... look what it says - eg. my log in might be 'abcd' and my mail system '123.com'. I missed that in the config screen (in Outlook) :
Mail Server Username: abcd+123.org
Having used that it damned well worked every time! Sounds silly but how many of us have missed it and such an easy oversight?
Michael

[chae]

Have had several customers over last few days change passwords then find they couldn't login again after the changes. Have run /etc/init.d/courier-authlib restart & after usually the 2nd call the passwords are then authenticated.