• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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