Rainer Duffner wrote:
Crispin Cowan wrote:
miguel gmail wrote:
Therefore it is basically not possible for SUSE to distribute Qmail. At most we could bundle the source code and give you instructions on how to compile it.
Oh! That would be more than wellcome for newcommers to mail servers administrators... :-)
# ./configure; make; make install worked for me. :-) Of course, configuration is another matter.
creates less headaches) - but what I really miss are RPMs (or .spec-files) for djbdns (and daemontools and ucspi-tcp). DJB's DNS-cache is one of those things that I end up installing on all hosts that need to do more than a handful of lookups - and it can boost performance several orders of magnitude compared to using a non-local DNS-resolver.
I installed daemontools, but not (yet) djbdns nor ucspi-tcp. But my server will typically not need to do more than a handful of lookups. Actually, at least for now, most/all of my outgoing mail is routed through my ISP's SMPT server. I am using qmail mostly for incoming mail.
So, as binaries are not allowed for all DJB-ware and the default install is really horrible, I'd appreciate if some kind of "clean" .spec file, that helps installing it in a SuSE-compliant way, was available. Because it does offer significant value ;-)
What is horrible about the default install? You and others mention that it needs a lot of patching to give it basic functionality? I used the default install, and it *seems* to be working for me. However, I am not stressing it much (and probably never will; it will be the server for my family and my wife's small business -- perhaps a few dozen outbound messages a day, a once-a-month mass mailing to a list of 100 or so subscribers, and maybe a hundred or so incoming messages a day). I have not figured out how to hook it up to SpamAssasin, but I have not put much effort in to it yet -- almost nobody knows about the addresses handled by my server, so it is not getting spammed (yet). I'm concerned about security issues in the default install. I'm less concerned about performance issues, since it is not going to be processing much mail. -- Chuck Linsley linsley@sonic.net