• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

IMAP Email Authentication is Now Failing - Could Use Some Assistance

Marc_Ta

New Pleskian
Running Plesk 10.3.1 on Linux installation....

Had 10 different email addresses all setup and working great for the last couple of days. I noticed issues where using the same email client to access more than one of these email addresses at a time was causing problems, so I followed the instructions in this link --> http://kb.parallels.com/en/113841

No issues updating the file. But once I restarted the courier-imap, authentication doesn't work now for any of the email address (accessing through webmail or through other email client). Passwords have been verified via mail_auth_view and are correct.

The errors I'm getting look like this:

May 7 06:19:47 0398462 pop3d: Connection, ip=[::ffff:108.9.34.134]
May 7 06:19:49 0398462 pop3d: Connection, ip=[::ffff:108.9.34.134]
May 7 06:19:49 0398462 pop3d: IMAP connect from @ [::ffff:108.9.34.134]IMAP connect from @ [::ffff:108.9.34.134]INFO: LOGIN, [email protected], ip=[::ffff:108.9.34.134]
May 7 06:19:50 0398462 pop3d: 1399461590.138023 LOGOUT, [email protected], ip=[::ffff:108.9.34.134], top=0, retr=19817, time=1, rcvd=50, sent=24511, maildir=/var/qmail/mailnames/myclient.com/user/Maildir
May 7 06:19:50 0398462 pop3d: Connection, ip=[::ffff:108.9.34.134]
May 7 06:19:54 0398462 pop3d: IMAP connect from @ [::ffff:108.9.34.134]ERR: LOGIN FAILED, ip=[::ffff:108.9.34.134]
May 7 06:19:58 0398462 pop3d: LOGIN FAILED, ip=[::ffff:108.9.34.134]



The courier-imap service appears to be running just fine:

[root@0398462 ~]# /etc/init.d/courier-imap status
couriertcpd (pid 1827 1818) is running...

PIDAscending %CPU %MEM Command Nice Pri RSS Stat Time User
1818 0.0 0.0 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -stderrloggername=pop3d -maxprocs=40 -maxperip=4 -pid=/var/run/pop3d.pid -nodnslookup -noidentlookup 110 /usr/sbin/pop3login /usr/lib/courier-imap/authlib/authpsa /usr/bin 0 24 616 S 00:00:00 root
1820 0.0 0.0 /usr/sbin/courierlogger pop3d 0 23 560 S 00:00:00 root
1827 0.0 0.0 /usr/lib/courier-imap/couriertcpd -address=0 -stderrlogger=/usr/sbin/courierlogger -stderrloggername=pop3d-ssl -maxprocs=40 -maxperip=4 -pid=/var/run/pop3d-ssl.pid -nodnslookup -noidentlookup 995 /usr/bin/couriertls -server -tcpd /usr/sbin/pop3login /usr 0 21 608 S 00:00:00 root


I followed the steps in this article trying to debug --> http://kb.parallels.com/en/6781 but everything looks fine. Any other ideas of what I might be able to check?
 
I just rebuilt the mail server settings, restarted and authentication still isn't working:

[root@0398462 ~]# /usr/local/psa/admin/sbin/mchk --without-spam
==> Checking for: mailsrv_conf_init... ok
==> Checking for: mailsrv_entities_dump... ok
==> Checking for: mail_admin_aliases... ok
==> Checking for: mail_auth_dump... ok
==> Checking for: mailman_lists_dump... ok
==> Checking for: mail_kav8_restore... ok
==> Checking for: mail_mailbox_restore... ok
==> Checking for: mail_responder_restore... ok
==> Checking for: mail_drweb_restore... not exists
==> Checking for: mail_spf_restore... ok
==> Checking for: mail_dk_restore... ok
==> Checking for: mail_grey_restore... ok
 
Back
Top