• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

IMAP/POP dead after upgrade to Plesk 7.5.4

madsere

Regular Pleskian
After upgrading Plesk to 7.5.4 suddenly it was impossible to login to Horde.

Checking around I found there was no IMAP on port 141 as required by IMP (according to https://server/horde/imp/test.php)

Checking Plesk -> Server -> Services shows POP/IMAP to be stopped. Clicking the [>] start button fails to produce any result.

/var/log/messages report:
Sep 4 11:08:28 vps101 imapd.rc: bind: Address already in use
Sep 4 11:08:28 vps101 imapd.rc: ll_daemon_start: Resource temporarily unavailable
Sep 4 11:08:28 vps101 courier-imap: Starting imapd succeeded
Sep 4 11:08:28 vps101 imapd-ssl.rc: bind: Address already in use
Sep 4 11:08:28 vps101 imapd-ssl.rc: ll_daemon_start: Resource temporarily unavailable
Sep 4 11:08:28 vps101 courier-imap: Starting imap-ssl succeeded
Sep 4 11:08:28 vps101 pop3d.rc: bind: Address already in use
Sep 4 11:08:28 vps101 pop3d.rc: ll_daemon_start: Resource temporarily unavailable
Sep 4 11:08:28 vps101 courier-imap: Starting pop3 succeeded
Sep 4 11:08:28 vps101 pop3d-ssl.rc: bind: Address already in use
Sep 4 11:08:28 vps101 pop3d-ssl.rc: ll_daemon_start: Resource temporarily unavailable
Sep 4 11:08:28 vps101 courier-imap: Starting pop3-ssl succeeded

imapd.rc suggests starting IMAPD on port 143.

What is this mess?
 
Make sure that you do not have the courier-imap service in xinetd, this can cause the above behaviour.
 
Spot on! That was the problem, Thanks!

How could this happen? I'm certain I didn't enable them!
 
Back
Top