Hello, We are changing student email from mailboxes, to forwarding addresses. Among other challenges, we are exploring various ways to deal with students who are subscribed to closed (only subscribers may post) mailing lists.
(There are a lot of similar challenges when switching to an email forwarding model - any list members who have gone through this, I would love to pick your brain!) One possibility we're exploring, is to change a student's mailing list subscriptions, when they change their forwarding address. We would iterate through these address changes and run clone_member, like: Clone_member --remove --admin [email protected] [email protected] We could end up processing as many as 500 address changes nightly (running clone_member for each one), with each run of clone_member iterating through all mailing lists. I'm concerned that this is much more than clone_member was intended for. Can Mailman developers or heavy uses of Mailman comment on this? Thanks very much, Ivan. ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
