Ivan Fetch writes: > 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]
I can't really comment on the burden on the host, but ISTM that this would be a substantial burden on the students. They would have to remember which account is their real account to make any changes, or to post. This might be non-trivial for students with multiple mailboxes. How about having the forwarding address setup update accept_these_nonmembers, instead? Also, what are you going to do about the old forwarding address? It seems likely that in many cases students will want to do things like receive on their cellphone account but sometimes post from their home ISP, etc. Then they change back, creating a real muddle. OTOH, allowing dead or dormant accounts to post is a potential issue. ------------------------------------------------------ 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
