>So, would it be possible to use the "To:" address for the name of the >mailing list rather than the "Delivered-To:"? Pretty please?
Ok, so here is what I think was happening. The "subscribe confirmation" message to the wedi-* lists got archived under wedi-mirror. This is actually a reasonable thing to do. From Mail-Archive's perspective, it really does look like wedi-mirror was the list name. Now that wedi-mirror archive was started, incoming messages matched two lists, wedi-mirror and wedi-<ACTUAL>. As soon as that happens, Mail-Archive takes a closer look at headers and tries to disambiguate. It sees wedi-mirror in the Delivered-To: and says "ah ha! We've disambiguated." And files under wedi-mirror I've gone ahead and moved the wedi-mirror archives aside. Now that there is no disambiguation step required, mail is archiving ok. We match just one list, wedi-<ACUTAL>. But it is very fragile, and the second some message creates a wedi-mirror archive things will go south again. Bottom line - I've got things kinda working, but it could break again at any time. This tunneling though a mail alias business does not play well with the sorting heuristics. And I'm not going to optimize the sorting heuristics for tunneling (especially if it hurts the non-tunneling cases). Nothing against wedi, but I often associate tunneling with abuse. Such as lists trying to get around the YahooGroups ban or someone trying to covertly archive a mailing list. That's an additional motivation not to spend effort support tunneling. In an unrelated note, Mail-Archive survived today's slashdotting just fine. We served nearly a million hits today. After I upped the number of allowed simultaneous HTTP connections to about 550, there was no problem keeping up with the load. -Jeff _______________________________________________ Gossip mailing list [EMAIL PROTECTED] http://www.mail-archive.com/cgi-bin/mailman/listinfo/gossip
