Plesk

[2008-11: New installation on 10.3/8.6.0]
[2007-04: Implementing SMTP Authorization with qpsmtpd running under SuSE 10.0 and Plesk 8.0
[2014-01: Here's an update to these instructions.]
[2018-09: Update #2 on Installing qpsmtpd on Xenial, completely replaces 2014-01]

[2008-11: New installation on 10.3/8.6.0]
[2007-04: Implementing SMTP Authorization with qpsmtpd running under SuSE 10.0 and Plesk 8.0
[2014-01: Here's an update to these instructions.]
[2018-09: Update #2 on Installing qpsmtpd on Xenial, completely replaces 2014-01, replaced by the following]

Note: If you need LESS just for Drupal, see Install the LESS CSS Preprocessor for Drupal.

Some posts, like Ubuntu installation directions for fresh web-server recommend something like


sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install nodejs
sudo ln -s /usr/bin/nodejs /usr/bin/node
sudo apt-get install npm
sudo npm install -g less
node –v
npm -v


This is an update to my original instructions for installing qpsmtpd on a Linux system running under Plesk.

Just in case you don't have cc yet:

apt-get install build-essential


qpsmtpd is now on GitHub

qpsmtpd's README mentions installing the following "required Perl modules"

perl -MCPAN -e 'install Net::DNS'
perl -MCPAN -e 'install MIME::Base64'

Run


aptitude purge mailman psa-mailman-configurator


Run


mysql -uadmin -p`cat /etc/psa/.psa.shadow ` database_name


Here's what 111.93.188.66 (presumably Parallels, India) did:

cat /etc/issue
/usr/local/psa/bin/admin --show-password
mysql -uadmin -p`cat /etc/psa/.psa.shadow ` psa

\q
use psa;
select id,name from domains where cl_id = vendor_id;
select id,login from clients where parent_id is null;
update domains set vendor_id=1 where cl_id=vendor_id;

I've tried moving a Plesk 8.6 installation on SuSE 10.0 to a Plesk 8.6 installation on SuSE 10.3, but this doesn't work (see https://kis.hosteurope.de/support/faq/index.php?cpid=13913 (requires login)).

Downgrading to openssh-4.1p1-10 allows Plesk Migration Manager to work, and to avoid opening up vulnerabilities I've used...

/etc/hosts.deny:
sshd : ALL : DENY

and

/etc/hosts.allow:
sshd : xxx.xxx.xxx.xxx : ALLOW

In this blog entry I'll collect a few minor items where I feel, that Plesk is not quite up where it should be.

Before Anything Else: Fix SSH

Edit /etc/ssh/sshd_config and make the following changes (in the order of the parameters in the file):

Drupal requires http://example.com/cron.php being called regularly. You can set this up in Plesk within each site. Plesk will create a corresponding entry in /var/spool/cron/tabs/site_user. The downside of this is that each cron run will produce an entry in the /var/log/messages system log. If you have a couple of sites and each one runs the cron job every hour, then you'll easily end up with hundreds of useless system log entries every day!