-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Adam McGreggor wrote:
On Thu, Jun 18, 2009 at 02:00:54PM -0500, Kenneth Raffenetti wrote:
I recently had a request to make it so a Mailman domain I had setup would include a default set of email addresses in the accept_these_nonmembers field of each list. I thought it was a reasonable request as these people are responsible essentially all things in that domain. Default.py and mm_cfg.py are not currently setup to allow this.
Does anyone think this is a reasonable feature request?
Yes, and no.
Yes, in that I can see some advantages/cases where it may be useful to this, but no for a couple of reasons/prejudices:
(a) if something's worthy of a list's attention, the poster should have the courtesy to be a member of the list (assuming these are other people, not, say, functional aliases, or whatever); (b) i'd imagine this may be a case of cross-posting. Which infuriates me. (How about having one list for everyone that needs to be on it, and if appropriate send *those* list's messages to other lists?)In my instances, after creating new lists, i subscribe a series of address (+ trusted domains) to the list -- or rather my list-creating and configuring script does that for me (I like to do some customizations with withlist: and am quite lazy.).
I considered setting up a quick wrapper to do this from the command-line (in fact I did something similar to retroactively add addresses to all the lists), but that would only work for those of us using the CLI. We generally hand off list creation to our helpdesk staffers, whom we prefer use the web interface rather than give elevated privileges on the actual server.
Ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAko/oiMACgkQvRJB9CBtvwgnsACffqbRrUwiAp9cmt68CtGMwkPc QBwAnizln783vkUslHzD9by0JK6+KxPZ =nw/R -----END PGP SIGNATURE-----