-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It must be my mistake because otherwise there would be a hue and cry by now if all Mailmans (Mailmen? :-)) were doing the same.
My Mailman-1.1 sent monthly reminders thus
- -------------- cut here ---->8 ---< head
Return-Path: mailman-owner@venice.essential.org
Delivered-To: jam@jamux.com
Received: from milan.essential.org (milan.essential.org [216.0.124.12])
by athene.jamux.com (Postfix) with ESMTP id 1AD3448031
for jam@jamux.com; Wed, 1 Nov 2000 05:01:39 -0500 (EST)
Received: from venice.essential.org (venice.essential.org [216.0.124.17])
by milan.essential.org (8.9.3/8.9.3) with ESMTP id FAA06070
for jam@essential.org; Wed, 1 Nov 2000 05:01:38 -0500
Received: from venice.essential.org (localhost [127.0.0.1])
by venice.essential.org (Postfix) with ESMTP id DC46429B60
for jam@essential.org; Wed, 1 Nov 2000 05:01:37 -0500 (EST)
From: mailman-owner@venice.essential.org
Subject: lists.essential.org mailing list memberships reminder
To: jam@essential.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.1
Precedence: bulk
List-Id: Promoting new uses of agricultural residue...
Message-Id: 20001101100137.DC46429B60@venice.essential.org Date: Wed, 1 Nov 2000 05:01:37 -0500 (EST) - ---- 8<------- cut here ----------> tail
the bogus "List-Id being a known problem creating a minor annoiance. Now my shinny new Mailman-2.0 sent them thus[1]
- -------------- cut here ---->8 ---< head Return-Path: ababa-admin@venice.essential.org Delivered-To: jam@jamux.com Received: from milan.essential.org (milan.essential.org [216.0.124.12]) by athene.jamux.com (Postfix) with ESMTP id 728B14800B for jam@jamux.com; Fri, 1 Dec 2000 05:02:06 -0500 (EST) Received: from venice.essential.org (venice.essential.org [216.0.124.17]) by milan.essential.org (8.9.3/8.9.3) with ESMTP id FAA29820 for jam@essential.org; Fri, 1 Dec 2000 05:02:05 -0500 Received: from venice.essential.org (localhost [127.0.0.1]) by venice.essential.org (Postfix) with ESMTP id 9418729BA8 for jam@essential.org; Fri, 1 Dec 2000 05:02:05 -0500 (EST) Subject: lists.essential.org mailing list memberships reminder From: mailman-owner@venice.essential.org To: jam@essential.org X-No-Archive: yes X-Ack: no Sender: ababa-admin@venice.essential.org Errors-To: ababa-admin@venice.essential.org X-BeenThere: ababa@lists.essential.org Precedence: bulk Message-Id: 20001201100205.9418729BA8@venice.essential.org Date: Fri, 1 Dec 2000 05:02:05 -0500 (EST)
- ---- 8<------- cut here ----------> tail
with the bogus envelope sender, "Errors-To" and header-sender presumably causing ababa-admin@venice.essential.org to be inundated with delivery error notices.
Is this an error that has crept into my Mailman configuration, or is this what Mailman will do until the item on the To Do list is resolved?
I am making an unadvertised aaaaa-list hoping to shield ababa-admin@venice.essential.org from a repeat performance. Will this work?
ALSO, when the problem of the monthly reminders is worked upon I urge again for a X-Addressed-To or some such header field to help understand those delivery error notifications from AOL and many universities that, correctly IMHO, attempt to reduce the exposure of potentially private information by excluding the original message body from delivery error notices. Add recipient address munging and without some counter measure such a delivery error notice is useless.
jam
Footnotes: [1] To protect the innocent, I have replaced the name of the alphabetically first mailing list on this Mailman with a fictions list name.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: OpenPGP encrypted mail preferred. See http://www.gnupg.org/
iEYEARECAAYFAjonsgAACgkQUEvv1b/iXy8c0ACfZNqc1MiPgJdMkMoZM3fRRLM1 iZ0AniKuBuz+GswVatO8iz6vi9+eqx2n =uD/d -----END PGP SIGNATURE-----
participants (1)
-
John A. Martin