"G. Armour Van Horn" wrote:
> Those groups of multiple recipients are large - several hundred at a time. To make
> the change you suggest means multiplying your bandwidth and server requirements by
> the average size of your active lists. My most active list has 240 digest
> subscribers and 300 regular subscribers. Both appear to be handled in a single
> command. Done one at a time there would be a huge increase in CPU load and
> bandwidth, and folks at the end of a list would get their messages later than those
> at the head of the list.
Ya, I realize all of this, however I have clients who would like, are requesting,
and generally want this type of mechanism built in. The main reason is because many of
the subscribers no longer remember what e-mail address they used to subscribe, and
consequently don't know what to use to UNsubscribe. Having Mailman serialize its
messages will provide a simple way for them to unsubscribe.
--
W | I haven't lost my mind; it's backed up on tape somewhere.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
IT Director / SysAdmin / WebSmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
