Re: [Qmail-scanner-general]Two instances of qmail and multiple rcpts issue
AV/content filter for Qmail
Brought to you by:
jhaar
From: Jason H. <Jas...@tr...> - 2004-12-22 22:32:55
|
Jeremy Kusnetz wrote: > We have 2 instances of qmail setup. The first instance is just a > plain version of qmail which sucks in the email and then forwards it > (using smtproutes) to a second instance using qmail-scanner to do my > spam and virus scanning. This allows my users to send large emails > and not have to wait for the large attachments to finish scanning > before closing the SMTP session. > > > Quite understandable. > The problem I run into is when the user sends a single email to lots > of recipients. When the first instance of qmail forwards the mail to > the second instance of qmail instead of forwarding the email once, it > creates a single SMTP session for every single recipient, which causes > the 2^nd instance of qmail to scan the same email many times, one for > each recipient (creating quite a load!). > > > Yup - that's the downside to Qmail in general. > I understand that this is just the way qmail works (to allow VERPS), > but is there some other way to get the first instance of qmail to send > the email intact with all the recipients in the header so the second > one only has to scan once? Do I have to go as far as using another > MTA to replace the first instance of qmail? > > > > No - unless you're willing to do silly things with serialmail. A different MTA would definitely work - but then I'd be remiss not to suggest that you look at replacing Qmail all together. I mean, if you have to change the frontend, why support two different MTAs? I've never liked Qmail's lack of support for serializing mail deliveries... :-( OTOH that feature allows other sites to do per-user configurations easily. If each message is guaranteed to have only one recipient, then you can much more extensively control delivery options. -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +64 3 9635 377 Fax: +64 3 9635 417 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 |