If you have a Plesk server where short mail names are enabled, upgrading to Plesk 8.4 can cause some issues. Valid logins may be rejected, and they’ll appear in your /usr/local/psa/var/log/maillog as “no such user”. You can correct the issue by switching to long mail names (click Server -> Mail in Plesk), or you can run a shell script provided by Parallels. For further details, refer to the Plesk KB article “Mail users cannot get or send mail after upgrade to Plesk 8.
Some of you may have already noticed from my Twitter feed, but I’ve started a complete re-write of pleskhacker.com in an easier-to-use format. The old site was done in Dokuwiki, and I found that it didn’t scale too well. The new site uses WordPress, and the performance is already improving. Another improvement to the site is that it is now hosted on Mosso. This should allow the site to handle a lot more traffic and be more redundant than the original configuration.
I found a Plesk 8.3 server running RHEL 4 last month that was presenting errors when users attempted to send e-mail via SquirrelMail: ERROR: Email delivery error Server replied: 127 Can't execute command '/usr/sbin/sendmail -i -t -firstname.lastname@example.org'. The error was appearing because safe_mode was enabled and SquirrelMail was unable to drop e-mails into /usr/sbin/squirrelmail. After disabling safe_mode on the server, the users were able to send e-mails via SquirrelMail.
If you have Plesk 8.1 or later, you have support available for Ruby on Rails. Unfortunately, clicking the FastCGI checkbox in Plesk won’t get you all of the support you need (and expect). The folks over at Parallels created a relatively simple process to get Ruby on Rails working properly on your site: Go to your domain that you want to adjust, and click Setup. Make sure the CGI and FastCGI options are enabled.
If you recently upgraded to Plesk 8.4.0 with short names enabled, you may have found that it’s working with SMTP, but it doesn’t work with POP3 or IMAP. There’s a bug in the Plesk version that prevents the courier configuration from being updated. To correct the issue, first make sure that Plesk has short names enabled (Server > Mail). Once you’ve confirmed that Plesk thinks it’s enabled, add SHORTNAMES=1 to the following configuration files: