• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Webmail and IMAP fix after upgrading

shoggy24

Regular Pleskian
I just wanted to share this, so that anyone who happened to have a similar problem after upgrade to 8.2 will try this fix.
I upgraded using autoinstaller and my upgraded completed without error, only to find out later that my customers cant login to webmail and cant connect to imap. I spent hours following suggestion found in this forum, including modifying my etc/hosts and etc/psa horde/servers.php among others, but none fixed the issue.
I finally paid for 1 hour support so that swsoft can take a look at it. They responded really quick and resolved the issue although they had to escalate it to second line of engineers, below is the explanation of the problem;


"IMAP service was down there, it could not start with error

Jul 27 06:00:05 websvr1 imapd: Invalid -maxperip option.
Jul 27 06:00:05 websvr1 imapd-ssl: Invalid -maxperip option.

The reason of the error was that MAXPERIP option was absent in /etc/courier-imap/imapd configuration file. I have added the missed line and restarted service, it should work OK now. Please check and let me know if the problem continues

I have reported the problem description to the development team to have them investigate who it may happen and correct it in the next updates if it is needed."

I was surprised to learn IMAP didnt start because when the system is booting up it shows IMAP as succesfully started which completely threw me off.

Well hope this helps someone someday
 
shoggy24 thanks!

just had the same problem during Plesk 8.3 -> 8.6 upgrade - uncommenting MAXPERIP helped:

# grep MAXPERIP /etc/courier-imap/imapd
##NAME: MAXPERIP:0
MAXPERIP=6
 
Back
Top