Archive imports must be automatic, or not allowed. (I'm laying down
the law here; a core value of the service is automation, and I am not
going to do manual imports of list archives) Is archive-date: a
standard field? If so, do you have the RFC number?
A few other (unsavory) possiblities, off the top of my head:
1. Disallow archive imports except for special circumstances.
2. Allow SMTP imports, but warn people their dates will be mangled.
3. Write an automated import system using FTP or HTTP
4. Look into SMTP interfaces with list servers
(majordomo and friends) that keep archives.
Jeff
------------------------------
the better way to merge / import existing arhives may be
1. to have them send numbered files / tar files, or
2. add the "Archive-date:" field that overrides the msg date.
(i know that this is "additional complexity to the
system" that you hate.)
