Hi, we have the same problem here. We run cPanel 11.24.4-S33345 - WHM 11.24.2 and the users which reported the problem are not mac users.
Even my own email account is presenting this problem randomly along the entire day.
I've noticed that this happens between 12 and 17 hs, hours in which the activity is in the topmost. This problem started since we upgraded to S33345. I've upgraded/reinstalled exim and courier but nothing changed. I've increased the number of auth daemons and nothing changed.
There are almost 300 email users and the login failure occurs randomly to different account all days and in different domains...
Looking at the logs, exim stated that they are just login failures! As if Outlook would tried an incorrect password, but you all know that is not true.
What's happening? what changes introduced cPanel 11.24 to exim? maybe a still missed change in Stable but that it is present in Current or Release?
I also can recall that immediately after upgrading to last Stable, I've received 4 emails from the server with the following subjects:
Code:
- Certificate for cpanel on xxxxxxxxxx.com was expired and a self signed one was created to replace it.
- Certificate for exim on xxxxxxxxxx.com was expired and a self signed one was created to replace it.
- Certificate for courier-pop3d on xxxxxxxxxx.com was expired and a self signed one was created to replace it.
- Certificate for courier-imapd on xxxxxxxxxx.com was expired and a self signed one was created to replace it.
The body of one of them, i.e.:
Code:
Certificate for courier-pop3d on xxxxxxxxxx.com was expired and a self signed one was created to replace it. You should install a new certifcate as soon as possible to replace the self signed one that was installed to replaced the expired one. You can install a new certificate in WHM under "Manager Service SSL Certificates", or by clicking this link: https://xxxxxxxxxx.com:2087/scripts2/manageservicecrts
But, when you go to that section under WHM, the certificates states a validity until 2010. I don't understand what's happening.
May this have any relation with the main login problem reported in this thread??
Thanks