Re: Mailman-Developers Digest, Vol 175, Issue 14

TAKE OFF YOUR LIST
Send Mailman-Developers mailing list submissions to mailman-developers@python.org
To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-developers or, via email, send a message with subject or body 'help' to mailman-developers-request@python.org
You can reach the person managing the list at mailman-developers-owner@python.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Mailman-Developers digest..."
Today's Topics:
- Re: Uncaught bounce notification .. (Martin Maechler)
- Re: Uncaught bounce notification .. (J C Lawrence)
- Re: Uncaught bounce notification .. (Nigel Metheringham)
Message: 1 Date: Fri, 14 Nov 2003 09:05:48 +0100 From: Martin Maechler <maechler@stat.math.ethz.ch> Subject: Re: [Mailman-Developers] Uncaught bounce notification .. To: J C Lawrence <claw@kanga.nu> Cc: mailman-developers <mailman-developers@python.org>, Martin Maechler <maechler@stat.math.ethz.ch> Message-ID: <16308.36060.659955.861772@gargle.gargle.HOWL> Content-Type: text/plain; charset=us-ascii
"J" == J C Lawrence <claw@kanga.nu> on Tue, 11 Nov 2003 09:05:45 -0500 writes:
J> On Tue, 11 Nov 2003 10:52:07 +0100 J> Martin Maechler <maechler@stat.math.ethz.ch> wrote: >> My problem is that I get about 50 "Uncaught bounce notification"s per >> day, only few of which are spam/virus related. J> Turn on VERP for a few days. J> -- J> J C Lawrence J> ---------(*) Satan, oscillate my metallic sonatas. J> claw@kanga.nu He lived as a devil, eh? J> http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
Thank you, "J", for the suggestion, but that seems not an option for two reasons
we (currenly must) use sendmail and that doesn't seem to support VERPing -- or at least we haven't found docu on that
VERP will probably cost quite a bit of CPU/memory/disk-IO resources on the mail servert. Currently that server almost constantly runs on load 2.5 -- 3 (because of anti-virus / anti-spam / mailman ..)
OTOH, most of these "uncaught bounce notification" can quite easily resolved by a human, i.e., the subscriber's e-mail can very often be found in the bounce. E.g., if they resend the full headers, I can find the proper subscriber's address in a "Received:" header such as
Received: from hypatia.math.ethz.ch (root@hypatia.ethz.ch [129.132.58.23]) by cryforhelp.mr.itd.umich.edu (umich) with ESMTP id hAB7NrHc014893 for <pgreen@umich.edu>; Tue, 11 Nov 2003 02:23:53 -0500
(hypatia is our own mail server)
I.e., I think mailman's analysis of the bounce message leaves room for improvement. Can you tell me where in the python code this happens (so we might consider improving it here)?
Best regards, and thank you all for mailman!
Martin Maechler <maechler@stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <><
Message: 2 Date: Fri, 14 Nov 2003 08:40:02 -0500 From: J C Lawrence <claw@kanga.nu> Subject: Re: [Mailman-Developers] Uncaught bounce notification .. To: Martin Maechler <maechler@stat.math.ethz.ch> Cc: mailman-developers <mailman-developers@python.org> Message-ID: <10436.1068817202@kanga.nu>
On Fri, 14 Nov 2003 09:05:48 +0100 Martin Maechler <maechler@stat.math.ethz.ch> wrote:
"J" == J C Lawrence <claw@kanga.nu> on Tue, 11 Nov 2003 09:05:45 -0500 writes:
On Tue, 11 Nov 2003 10:52:07 +0100 Martin Maechler <maechler@stat.math.ethz.ch> wrote:
My problem is that I get about 50 "Uncaught bounce notification"s per day, only few of which are spam/virus related.
Turn on VERP for a few days.
- we (currenly must) use sendmail and that doesn't seem to support VERPing -- or at least we haven't found docu on that
Mailman's VERP supports don't require VERP support in the MTA, merely support for plus addressing.
- VERP will probably cost quite a bit of CPU/memory/disk-IO resources on the mail servert. Currently that server almost constantly runs on load 2.5 -- 3 (because of anti-virus / anti-spam / mailman ..)
The added overhead is increased delivery expense in the form of more disk IO, both for the initial delivery from Mailman, and the final delivery to the target MX. The other overheads are fairly minimal given minor MTA tuning.
-- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
Message: 3 Date: Fri, 14 Nov 2003 13:48:05 +0000 From: Nigel Metheringham <Nigel.Metheringham@dev.InTechnology.co.uk> Subject: Re: [Mailman-Developers] Uncaught bounce notification .. To: mailman-developers <mailman-developers@python.org> Message-ID: <1068817685.18487.17.camel@angua.localnet> Content-Type: text/plain
On Fri, 2003-11-14 at 13:40, J C Lawrence wrote:
On Fri, 14 Nov 2003 09:05:48 +0100 Martin Maechler <maechler@stat.math.ethz.ch> wrote:
- VERP will probably cost quite a bit of CPU/memory/disk-IO resources on the mail servert. Currently that server almost constantly runs on load 2.5 -- 3 (because of anti-virus / anti-spam / mailman ..)
The added overhead is increased delivery expense in the form of more disk IO, both for the initial delivery from Mailman, and the final delivery to the target MX. The other overheads are fairly minimal given minor MTA tuning.
Virus/Spam scanning should not be done for mail injection from mailman - its already been scanned when it came through the MTA on the way into mailman, so a second scan is completely superfluous and downright silly when you have expanded the original incoming message into a number of outgoing ones (even without VERP).
Nigel.
-- [ Nigel Metheringham Nigel.Metheringham@InTechnology.co.uk ] [ - Comments in this message are my own and not ITO opinion/policy - ]
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers
End of Mailman-Developers Digest, Vol 175, Issue 14
participants (1)
-
Pat