• 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!
  • 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.

Plesk 11.5.30 Email ERR Temporary Problem, please try again later.

iantresman

Basic Pleskian
After upgrading Plesk from 11.0.x to 11.5.30 #6, I found that myself and several of my clients could no longer receive email (Outlook, Eudora and Thunderbird), and were getting an error: "ERR Temporary Problem, please try again later." I eventually tracked it down to the mail server requiring long POP3 usernames (ie username@domain.com).

However, "Server-Wide Mail Settings" has enabled "Use of short (webmaster) and full (webmaster@domain.com) POP3/IMAP mail account names is allowed". So it seems that this setting is being ignored, or each mailbox is set incorrectly?

It would be useful to get the mailboxes allowing short usernames, as I'd rather not need to help many of my computer-challenged clients from having to change their short mailbox usernames to fully-qualified usernames.
 
Perhaps a related issue, is that I find that spam filtering not working. If I disable it for a mailbox, and then re-enable and chose "Delete all spam messages", then I get the error message:

Error: ERROR:spammng:Multiple errors occurred: Command '['/usr/local/psa/admin/sbin/mail_handlers_control', '--add', '--priority=10', '--executable=/usr/local/psa/handlers/hooks/spam', '--name=spam', '--enabled', '--queue=before-local', '--mailname=email@domain.com', '--context=delete', '--type=recipient', '--dont-preserve-on-restore']' returned non-zero exit status 255 Command '['/usr/local/psa/admin/sbin/mail_handlers_control', '--add', '--priority=10', '--executable=/usr/local

This may be also related to a mailog entry:
spamd[16048]: spamd: server killed by SIGTERM, shutting down
 
Have you tried restarting Courier services? Does spamassassin service start/restart ok? What about mchk/mail_restore? Where is the full maillog for relevant time frame?
 
I'm not sure, and will have to contact my host. I do have a long mailog file, but am not sure what I am looking for. There are (a) a number of entries for: courier-pop3d: LOGIN FAILED, (b) No mention of spamassassin or mchk. I'll contact my host.

There was an issue during the Plesk upgrade, which my host told me was just a configuration issue. The log file mentions: ERROR: Failed to run the Yum utility.
 
Back
Top