I currently have a very large mailing list (approx 1700 subscribers,
50K a day in traffic, regular and digest options) that I run manually
(with a little help from MH, procmail, and shell scripts). The
mailinglist package SmartList (companion to procmail) has come of age
(i.e. incorporating all the features I wish) and I plan to switch the
list over in the near future.
I'm not sure about the best way to go about doing this. The
distribution list of SmartList is not compatible with my current list
and the sendmail aliases will have to be changed. Additionally, the
current directions for subscribing/unsubscribing to the list will no
longer be valid.
My inclination is to choose another mailing name for the list and set
up that list using the new software and have everyone resubscribe.
Then put an auto-replier on the old address with the new directions
and send out admin changes to the various places I know that list my
list.
Thing is, I'd really like to keep the name. I could switch back again
to the first name (just moving the distribution list this time, not
having folks have to resubscribe), but this would require sending out
mailinglist admin changes twice to the various places that mention my
list. Not good. I also don't want to bother my sysadmin for alias
changes more than necessary.
I suppose I could move the current list to a new name (which would
require changing all my scripts to reflect this) and set up SmartList
on current name. Biggest problem with this approach is that currently
both regular and digest on/off requests go to one request address
(fatfree-request) and with my new software, digest requests must go to
a seperate request address (probably fatfree-d-request).
Anyone else go through a software change on their list? Any advice?
--
Michelle Dick artemis@rahul.net East Palo Alto, CA
Owner, FATFREE Vegetarian Mailing List
|
|
