Date: Wed, 02 Sep 1998 10:55:36 +0200 From: Andre Oppermann <oppermann@pipeline.ch> To: andrew@squiz.co.nz Cc: "'freebsd-isp@FreeBSD.ORG'" <freebsd-isp@FreeBSD.ORG>, Manar Hussain <manar@ivision.co.uk> Subject: Re: qmail/ezmlm Message-ID: <35ED0808.10F7DAA1@pipeline.ch> References: <Pine.BSF.3.96.980902121230.596K-100000@aniwa.sky>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew McNaughton wrote: -snip- > Does anyone have any pointers to a step by step guide to doing the > transition to either of these? I'd like to move away from sendmail, but > there's very little room for error on my system, and not knowing all that > much about any of the packages involved, I've been a bit hesitant about > it. Take a look on www.qmail.org and my "big-qmail-picture" to get how qmail works. You can find it on http://www.nrg4u.com. > My system has a small ammount of incoming mail, and large ammounts of > automated outgoing mail. I have inhouse software providing customized > news feeds (current affairs, not nntp) via email. ie every message goes > out to a different list of people. Qmail was originally developed and designed to run a huge mailing list... > I want to be able to have tens of deliveries running in parallel, but I > don't want this to meant that deliveries are attempted over-frequently for > queued messages. I'd also like good control over how long messages sit in > the queue before the next delivery attempt. I want to be able to make a > second attempt after 5 minutes, and then progressively increase the > waiting time for successive attempts. Qmail does 20 concurrent deliveries by default, you can set that up to 200 and more. It also maintains a list of unreachable hosts so it simply jumps over additional deliveries to the same destination. I don't know of top of my head the delay for the second delivery, but it's a compile time option. > If parallel delivery for a single messages recipient list that would be a > bonus. Qmail does one SMTP connection for *every* message (some consider that as an DoS). So if you have 20 messages to one receipient it will open 20 remote deliveries at the same time. > Any suggestions on what I should be using for outgoing mail? Qmail :-) > Incoming mail is a separate problem, and may or not be migrated to the > same software. Handling error messages is the main problem there. ezmlm does a great job here, it handles unreachable receipients, hosts and other stuff by itself. You don't even have to deal with bounces. Some really big lists are driven by qmail/ezmlm, for example one list of the library association (or so) with 110,000 subscribers. Or the qmail list itself with about 700 subscribers. The turnaround times for a message are under 3 minutes in average. Remember the times where the freebsd lists with sendmail/majordomo had times of 2-4 hours (with ~300 subscribers (I don't know exactly but I think jmb siad something like this))? -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35ED0808.10F7DAA1>