Hans Salvisberg's blog

Implementing SMTP Authorization with qpsmtpd running under SuSE 10.0 and Plesk 8.0

Receiving incoming email and making it available to your users via POP3 or IMAP is only the first half of running a Message Transfer Agent (MTA). The other half is to relay outgoing email from your users to the world.

We don't want to run an open relay, of course, so we we need some form of authorization.

Getting a SuSE 10.0 / Plesk 8.0.1 VPS on HostEurope up and running

There are a number of issues that need to be fixed/acknowledged before the VPS will run well.

How to Move a qmail Installation

I was running a mail server (SMTP and POP3) for the domain example.com on the old.example.com host and needed to move it to new.example.com.

How to Forward Spam Sent to Spamtraps to SpamCop using qmail

I have a number of email addresses that get nothing but spam, and I like to feed these to SpamCop's quick reporting service. This is easy to do with qmail, if you know how and if you have a paid SpamCop account.

Installing qpsmtpd on SuSE 10.0 with Plesk 8.0

[14-01: Here's an update to these instructions.
[08-11: New installation on 10.3/8.6.0]

The qpsmtpd daemon started as a replacement daemon for the qmail-smtpd SMTP receiver from the qmail mail transport agent (MTA), but it can also be used with other MTAs. qpsmtpd is written in pure Perl and can be customized easily. It consists of a core that implements a complete SMTP server, and a number of plug-ins that enhance the operations of the server. These plug-ins allow for the checking of recipients and senders, as well as virus scanning, spam checking, blocking lists (DNS and RHS), SMTP AUTH and TLS. If you like to tweak, you can adapt qpsmtpd to almost any environment and task.

In this article I collect information that I've gathered from various sources and customized for installing qpsmtpd on Suse and Plesk.

How to Get Rid of Drupal's Ugly User Login Block

The User Login block is not a pretty sight. If you'd like to set up a website where part of the audience is anonymous users, then the User Login block is not welcome on each and every page. This is one of the first things I wanted to customize on my Drupal site


logrotate keeps Linux logs from growing indefinitely.

/var/lib/logrotate.status shows the list of the logs under logrotate control as well as the date of when each was last rotated.

Controlling Access to Pages

If you need a way to control who can see your content, then you should tackle this early on.

Configure the Drupal Default Input Format

By default, Drupal allows only the following tags in the HTML filter:
<a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>

That's not enough for writing any reasonably formatted content

Welcome to My Blog

The purpose of my blog is to document setting up and running a Linux web server with the Drupal content management system. I will write on all sorts of issues more or less related to that main topic.

Syndicate content