Comments on How To Install Qmailtoaster (CentOS 5.3)

I dont get it. isnt Qmail kinda dead. ref: http://en.wikipedia.org/wiki/Qmail

Why would someone want to deploy it.

--

 Ozzy

It is not dead at all. Don't confuse the fact that there has not been a need to update anything with it being dead. There have been no security holes, so no need for updates.

Many large organizations use Qmail. Many large ISPs use Qmail. It is deployed because admins want fast, secure, scalable email servers. It has been rock solid for many years without constant security fixes and updates. Doesn't that say something there?

You dont often see rpms (or other binaries) for the recent distributions. That also played in its-dead mentality. Not to mention the lack to quality/updated howto doc/tutorials etc..

 Anyway I was thinking of deploying a production email server. this solution also cross the radar. but this howto is way to messy for a server deployment. I mean installing development libs on the server to compile the packages .. too messy.

Correct me.

--

Ozzy

You need the development libs to build the packages. Once the packages are built, you can just install the binary RPMs on the production machine. No need to install the libs on the production machine that way if you build them in a VM or another machine.

In the past we were not allowed to release binary RPMs due to licensing, only source. This has changed and we will be offering a binary version download in the near future. It takes time to scale and build binary RPMs for  the 5 different distributions and 30 different versions of those same distributions.

Qmail is not dead. It has not needed any security updates since it was written, so people confuse this with "dead". There are many large corporations and ISPs who use Qmail. This, to me, means it's so stable and well written that nothing needed to be changed.

Jake ,  great job.

I wanna ask if is not better to use RPMforge instead doing CPAN install of perl dependencies ?

I always do this and I think it is a easy way .

http://wiki.centos.org/AdditionalResources/Repositories/RPMForge

Regards,

 Marco.

Jake , just for you known I replaced steps 4 and 5 to :

4 - install qmailtoaster-plus 

http://qtp.qmailtoaster.com/trac/wiki/WikiStart#a1-InstallQMTRepository

5 - deploy qmailtoaster using qtp-newmodel

#qtp-newmodel

 Regards, Marco.

Qmail is really a awesome package containing RPM information. It has script for all RPMs. I really loved the inforamtion provided in this article.

Full information with steps of installation.  Awesome tips.

Thanks for cool stuff!!!!

I would assume some very recent source of events have been responsible for sudden reversal of this  licensing policy thing. Anyway all´s well that ends well.

Regarding ur insinuation about binary release for distributions, packages for only the core/production kind (read stable) distributions would suffice & be appreciated.

Cheers.

---

Ozzy

I have install qmail toaster smoothly .its working very good . Every day I have sent & receive 5000 thousand ...Email... 

Please dont use qmail..  please.

qmail's insane security design makes it unable to reject mail based on unknown users, without first receiving it, and then bouncing it. With the current spamfilled internet environment, this creates loads of backscatter spam with a default qmail configuration. This is:

1. annoying
2. likely to get you into a RBL
3. creating load and queues on your server

Also, all this qmailtoaster project would not be nessasary if qmail had a proper license, which it does not. Thats right..  qmail is not free software. It is open source, but it is not free. Please support a proper mailserver project.

 So, please, pretty please, if you can, use a more sane MTA like Postfix, Exim or Sendmail.

Thanks for your opinions, but they are wrong.

Qmailtoaster will reject messages for unknown recipients without accepting them. It has been this way for a LONG time.

The old license for the software was put into place to ensure that you did not get code with sloppy patches or unknown patches applied. The author required that everyone distribute clean, pristine code as he had written it since he had his money riding on a guarantee that his code was secure. If he allowed just anyone to write code into his software and it created a security hole, he would be responsible for the reward money.

We created source RPMs that compiled Qmail from the original code and applied commonly used patches to it. DJB has since changed his license on the software, so binary packages are now allowed.

"Thanks for your opinions, but they are wrong."

Or rather outdated, it seems :)

"Qmailtoaster will reject messages for unknown recipients without accepting them. It has been this way for a LONG time."

It is very nice to see that this has changed. You might want to correct the wikipedia-article on qmail,  http://en.wikipedia.org/wiki/Qmail since it states that qmail indeed does accept messages to nonexisting users.

 "The old license for the software was put into place to ensure that you did not get code with sloppy patches or unknown patches applied. The author required that everyone distribute clean, pristine code as he had written it since he had his money riding on a guarantee that his code was secure. If he allowed just anyone to write code into his software and it created a security hole, he would be responsible for the reward money.

We created source RPMs that compiled Qmail from the original code and applied commonly used patches to it. DJB has since changed his license on the software, so binary packages are now allowed."

To be honest that sounds like a lame excuse. I didnt not read the terms of his reward, but it seems lame that he should be responsible for other peoples bad code. The GPL or BSD licences would not have made a difference IMO, so my opinion is still that the old license was lame.

However, it is nice to see that the license has changed to public domain (as I read in another thread).

The firewall script should be edited to insert your IP.

Also -  I found that DomainKeys install failed during the perl dependencies install, and I had to follow this thread: http://www.mail-archive.com/[email protected]/msg23540.html to arrive at a solution, on a slightly modified CentOS 5.3 install.

HTH,

Tom