>1) What happens if two or more such aliases get set up for the >same list. Does your archive check for duplicate messages?
Yes, MHonArc does check for duplicate message-ID's. No, we don't check for the case you describe. Anyway, it hasn't been an issue yet. In all cases until now, the unique archive address is directly subscribed to the list. Thus we've never had duplicate messages from the same list. >2) Does it sound like an impossible suggestion, to try to notify a list >owner whenever an archive for a new list gets started at mail-archive.com? >This way, a nondesirable archiving could be tracked down. Yes, that sounds like an impossible task to automate. Do you feel this is a problem? If so how can we improve? I think the following things are relevant. * List maintainers and message authors can express that messages not be externally archived through standard protocol headers. That's really the best way to tell people (i.e. any subscribers) not to archive messages. * If archiving is known, the list maintainer can easily discontinue it. * All relevant documentation mentions that mail-archive.com is a public archive for public internet email lists.
