• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

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