• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue Upgrading to Plesk Onyx 17.5.3 update 13 broke IMAP

Lindworm

New Pleskian
Hi,
today I upgraded from Plesk Onyx 17.5.3 update 12 to update 13. The result (like ****ing always with plesk upgrades) broke IMAP. None of my users can connect via IMAP anymore. Help please.

I used Dovecot and Postfix in update 12 and after it didn't work I removed Dovecot and replaced it with Courrier. No benefit in that, now the IMAP Connection from my client just runs into a timeout.

I do not find anything in any logfile. I am stuck. No clue anymore where to look.

How can I rollback to upgrade 12?

Bast regards ans pease help
Lindworm
 
If you receive timeout, then:

- [for a system with systemd] check service status:
# systemctl status dovecot.service
# journalctl --unit=dovecot.service


- check opened ports for dovecot;
# netstat -apt4 | grep dove
tcp 0 0 0.0.0.0: pop3 0.0.0.0:* LISTEN 11168/dovecot
tcp 0 0 0.0.0.0: imap 0.0.0.0:* LISTEN 11168/dovecot
tcp 0 0 0.0.0.0: sieve 0.0.0.0:* LISTEN 11168/dovecot
tcp 0 0 0.0.0.0: imaps 0.0.0.0:* LISTEN 11168/dovecot
tcp 0 0 0.0.0.0: pop3s 0.0.0.0:* LISTEN 11168/dovecot
#

- check from localhost that ports are open and work
# telnet localhost imap
Trying ::1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready.
^]
telnet> Connection closed.
#

- check from outside, that ports are opened in a firewall; it could be telnet too.
 
Back
Top