Search left

Courier-IMAP-SSL/TLS: Thunderbird error

The problem: Using an IMAP TLS mail account on Thunderbird could give an error:

Thunderbird can’t connect securely to because the site uses a security protocol which isn’t enabled.

Why: Looking at the the maillog (tail -f /usr/local/psa/var/log/maillog) we got:

imapd: couriertls: accept: error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number

Solution: Edit /etc/courier-imap/imapd-ssl and check the values to match this:

# TLS_PROTOCOL sets the protocol version.

# TLS_STARTTLS_PROTOCOL is used instead of TLS_PROTOCOL for the IMAP STARTTLS extension, as opposed to IMAP over SSL on port 993.

It seems that these two TLS protocol directives do not want to be identical.

Reload the IMAP daemon and QMail daemon, and the problem shoud be gone:

/etc/init.d/qmail restart
/etc/init.d/courier-imap restart

Have fun :)

Posted on October 7th, 2009 in Debian, Linux, Plesk | 1 Comment »

How to recalculate traffic and disk usage in Plesk Unix

The problem: There are some updates on client files, but the changes are not seen in Plesk interface.

Why: Plesk counts statistics once a day (at 4:07 AM by default) with the help of the {Plesk_installation_dir}/admin/sbin/statistics utility, but not every time when you look at domain statistics. (see

The solution: To update traffic and disk usage for all clients, run:


To update traffic and disk usage for a single domain, run:

/usr/local/psa/admin/sbin/statistics --calculate-one

Now, refresh Plesk interface to see the changes :)

Posted on September 21st, 2009 in Debian, Linux, Plesk | No Comments »

Plesk Linux Domain Alias 301 HTTP Redirect

The problem: A Plesk client has one or more domain aliases defined in Plesk Linux. In this article we’ll suppose that the main domain is, having as a domain alias.

In this case, the domain alias will appear as separate site to search engines (Google, Yahoo, MSN and so on). This situation can create duplication issues and can affect the PageRank of the main site.

The solution: We’ll use an Apache .htaccess file to create a Search Engine Friendly 301 redirect from the domain alias ( to the main domain (

Open (or create if it doesn’t exist) the Apache .htaccess file from the root folder (usualy /httpdocs) and add on top of it:

RewriteEngine on

# 301 Redirect requests from to
RewriteCond %{HTTP_HOST} !^(www\.)my-domain\.com$ [NC]
RewriteRule ^(.*)$$1 [L,R=301]

The RewriteCond line checks to see if the HTTP_HOST is NOT If this is true, Apache will do a permanent (301) HTTP redirect to$1, where $1 is the part that was after the HTTP_HOST.

Now, watch the PageRank of the main domain :)

Posted on August 13th, 2009 in Linux, Plesk | 10 Comments »

Plesk Backup to Amazon S3: testing phase

We are currently testing some solutions to an efficient way of syncing the Plesk Backups (see the previous post about creating them) to Amazon S3.

So far, the candidates are:
- s3fs, Fuse Over Amazon project on Google Code
- Subcloud, the commercial supported version of s3fs
- JungleDisk, Desktop Edition, with support for Linux, MacOS and Windows

What we want: a mounted directory to the Amazon S3 (US or EU) bucket on our testing server, followed by a cronjob that will so a “local” rsync of the Plesk Backup directory.

We’ll be back with complete details.

Posted on October 31st, 2008 in Linux, Plesk | 9 Comments »

Plesk 8.6.0 inetd changes

On 28 July 2008, Parallels have released Parallels Plesk Control Panel 8.6.0.

It seems (for unknown reasons) that they changed from xinetd config files to the old inetd style. There’s no more /etc/xinetd.d/smtp_psa files and alike, instead Plesk is now using /etc/inetd.conf.

Keep this in mind when upgrading from ealier version, could save some time and problems :)

Posted on August 13th, 2008 in Debian, Linux, Plesk | 1 Comment »


Footer left Footer right