On Oct 23, 2012, at 11:06 AM, Mark Sapiro <m...@msapiro.net> wrote: > > > I don't see this as a problem. If you try to add the same address twice > with a --nomail option, the first add will succeed and set nomail and > the second add will fail and do nothing, but the result is the address > is added with nomail set.
> The only situation in which this makes a difference is if the address > is already a member without nomail, which would only occur if it was > added previously by some other process or if it was added previously > and the user subsequently enabled delivery. Either way, I think the > right thing is for add_members --nomail to not disable delivery for an > existing member. True - I guess it's only happenstance that my script subscribes the yesmail members first, then does a second pass for the nomail members. I could easily reverse this order in my script. Problem solved. > Note, if you want to just set some or all users to nomail, see > <http://www.msapiro.net/scripts/set_nomail.py>. Also a good option! Thanks for that. ./s -- 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
