On Oct 22, 2012, at 7:15 PM, Mark Sapiro <m...@msapiro.net> wrote: > On 10/20/2012 11:06 AM, Scot Hacker wrote: >> >> Here's a simple 2.x diff in case it's useful to anyone: >> https://gist.github.com/3924229 > > > Thanks. > > I'm inclined to implement this for the 2.1 branch, but my taste is to do
Sorry for response delay - no time to learn bazaar and launchpad right now for this, so I appreciate your offer. > it differently. I would prefer to have a -n|--nomail option which if > specified would set the added members to nomail by admin, the default in > the absence of the option being current behavior. Thus, no need for > --enable-mail=<y|n>. > Absolutely - anything that can be scripted easily would work fine for me, and for others too I imagine. > Also, If the member to be added is already a member, I wouldn't change > its delivery option. > Hmm, not sure about that part - my implementation sometimes includes duplicate addresses, relying on the mailman import to weed them out. So I would *prefer* to have the option changed for existing members. But if that doesn't sit well with you, I understand - my script will just have to be smarter about it. Thanks, Scot > Would such an implementation work for you? > > -- > Mark Sapiro <m...@msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Birdhouse web and mail hosting http://hosting.birdhouse.org http://about.me/shacker _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
