qmail links

7 May 2011 Roberto Puzzanghera2 comments

In a LQ forum's thread I was asked to prove that updates to the original DJB qmail program really exist, providing direct links to them. Since I think that the set of links I provided could be of interest for the visitors of this pages, this is a copy&paste of that post:

In no particular order:

...and of course I'm forgetting something. There are many other patches I like which wait for updates, but at the same time they can be still considered useful; chkuser http://www.interazioni.it/opensource/chkuser/ is one of them, it provides recipient verification and MAV.

The main repository of links to all the available projects is always http://qmail.org.

This stuff can be applyed over the original Bernstein's program, which is claimed to be secure (read "Some thoughts on security after ten years of qmail 1.0" by D.J. Bernstein on the purpose).

And if you think that your site should be considered in this list you are invited to drop me a note


failover replication


I am thinking of having 2 qmail toaster servers to handle the same domains for incoming and outgoing mails, exactly like http://qmailtoaster.com/replicated.html. But i do not wish to use qmailtoaster as i feel that the packages used are outdated. Is your toaster able to do the same? Can i use the same instructions on http://wiki.qmailtoaster.com/index.php/QMT_Failover_replication_Setup to do the task using your tutorial?


Many thanks


Reply | Permalink

I'm not familiar with unison,

I'm not familiar with unison, but I think yes. The only thing that seems to be different from my configuration is this option:

path = /etc/tcprules.d

in the qmail.rpf file.

As far as the migration from qmailtoaster is concerned, I think that my combined qmail patch can be used to upgrade the one you have with the qmailtoaster installation.

let me know if you manage to do the replication, please


Edit: someone reported that spamdyke conflicts with other qmail-auth patches like the one included in my package..

Reply | Permalink