[Mailman-Users] Re: broadcast only
John A. Martin
jam at jamux.com
Wed Nov 29 07:25:26 CET 2000
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "DM" == Dan Mick
>>>>> "Re: [Mailman-Users] Re: broadcast only"
>>>>> Tue, 28 Nov 2000 18:34:44 -0800 (PST)
>> I would *love* to have an option to click "Announce Only" list
>> and when the user gets the welcome message it's *clearly* noted
>> that it's:
>> 1. Not a list they or others (other than the authorized
>> admins/company/etc.) can send messages to.
>> 2. Somehow indicates the frequency that they will receive
>> messages (customizable to each list).
Unfortunately it seems that the boilerplate manufactured by mailman
tells lies because it disregards the options selected for the list.
Perhaps a worthy item for 2.1 might be to tell no lies.
DM> Well, I guess I don't see the need for a mailing-list manager
DM> for such things, because it seems like they're nearly-always a
DM> "broadcast-only, you are subscribed because you're someone
DM> I've been given the right to broadcast to" list, for which
DM> normal aliases work *very* well.
DM> [[ ... ]]
DM> Mailman need not be involved in this; the archival,
DM> member-sub-unsub, and other value-adds of an MLM aren't useful
DM> for this application.
I see several announce lists that subscribe and unsubscribe dozens of
members daily. The archives of these lists get hundreds of hits
Besides having a straight forward way to divert mail away from the
list address it seems that some of these lists would benefit from
better bounce management. With default settings announce lists that
"publish" infrequently or irregularly do not automatically disable or
delete their bouncers effectively but instead get "first fresh".
Several dozen such lists with overlapping memberships of several
hundred to several thousand members results in there always being
several score of mails in the MTA's queue attempting deliveries to a
couple hundred defunct addresses that never disappear from the various
subscription lists. For some reason the owners of such lists do not
seem to disable or remove bouncers manually when the automatic process
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: OpenPGP encrypted mail preferred. See <http://www.gnupg.org/>
-----END PGP SIGNATURE-----
More information about the Mailman-Users