Bug #2713
closedFigure out the emailing strategy for CVS emails
0%
Description
We currently have an alias (cvs(at)unc-dot-edu) that points to michael's unc email address. This is difficult to manage in that
1) it only goes to one person (So if they are on vacation, swamped by email, accidentally delete it, we respond slowly or not at all or lose something).
2) there is no archive
3) it's hard to change who it goes to (michael has to release the alias then someone else has to grab it, hoping no one else gets it first!)
---
So, we could use a listserv, which we could setup at UNC, such as cvsdata@listserv.unc.edu. Potential Problems there:
1) private lists are not archived; public lists could get members added (we'd want to avoid that)
2) The is an awkward email address, so perhaps we could alias it somehow
3) listserv emails are limited to 5MB attachments (too small for our purposes, perhaps we could get some listserv admin to change that for us).
4) a 12MB file would go to all of michael, forbes, bob, and maybe steve, which results in 48MB of email, plus perhaps something in the archive. This begs for an FTP system that results in only one upload of the file, perhaps married to a listserv system that would alert us to the successful upload of a new package to the FTP server.
What are our FTP options at UNC, Bob? Can we set up something like that easily. We could have a backup of using the existing cvs@unc.edu alias if the ftp doesn't work for someone, with a separate (perhaps automated) email to let cvsdata listserv know.