The listserver is managed by an unrelated company. They would refuse to look into the problem, as I have already asked them why messages arrive so late at my mail server (i.e., two day delays sometimes) - and they say it is my problem (at my ISP)! At least in the case of describing my problems, I can show them my headers and tell them when my mail server received the messages. In the case of Mail Archive, I have no headers to show!!
But I am fairly certain that I have received all messages posted to the listserve in question between 12-30 and today. The messages I described awhile back on Gossip were received by me, but were not archived by Mail Archive. This is a common occurrence (on various of the WEDI listserve archives). I discover it quite frequently when attempting to refer someone to a posting via URL - only to find the posting is missing from the archive. I suppose it's possible that I receive all messages (even if some are delayed), while Mail Archive does not. William J. Kammerer Novannet, LLC. Columbus, US-OH 43221-3859 +1 (614) 487-0320 ----- Original Message ----- From: "Earl Hood" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, 07 January, 2003 02:58 PM Subject: Re: [Gossip] Some Messages not archived to wedi-transactions On January 7, 2003 at 10:46, "William J. Kammerer" wrote: > If you searched on this Message-ID in your logs, I would not have > expected you to find a match because the Message-ID is specific to the > recipient. The header I showed are specific to me as recipient, and the > headers in the messages sent to archive@mail-archive.com would look > somewhat different as the Lyris listserver assigns unique Message-IDs > for every recipient. IMHO, a questionable practice since it screws up references (for discussion threads) and makes tracking delivery errors harder (like in this case). Looking at the header you did provide: <LYRIS-14922627-168882-2003.01.02-15.00.40--wkammerer#novannet.com@lists .wedi.org> it could be implied that the ID for other users would be: <LYRIS-14922627-168882-2003.01.02-15.00.40--[useraddress]@lists.wedi.org > where [useraddress] is the subscriber's address with @ replaced with a #. Therefore, I would guess the Message-ID for archive@mail-archive.com would be: <LYRIS-14922627-168882-2003.01.02-15.00.40--archive#mail-archive.com@lis ts.wedi.org> Of course, this is just guessing. Since a timestamp is part of the ID, it could also vary if it is based on when the message sent to the receipient. Therefore, one may have to grep for something like (using regex notation): <LYRIS-14922627-168882-2003\.01\.02.*--archive#mail-archive\.com@lists\. wedi\.org> Assuming the day part is the same and only the time part could vary. To be more general: <LYRIS-14922627-168882-.*--archive#mail-archive\.com@lists\.wedi\.org> If the "LYRIS-14922627-168882" is sufficiently random, the above should be sufficient in searching for the message. The "archive#mail-archive\.com" could probably be dropped from the expression to be extra forgiving and still avoid potential false positives. BTW, some list management software may not do auto-retries on a failed mail delivery. For example, for one list, if unable to deliver a message, the list software sends a status message to the receipient of the problem. If repeated tries of sending the status message fail, the address is auto-unsubscribed. If successful, the status message contains instructions for the receipient on how to retrieve the past undeliverable messages. Since mail-archive.com is all automated, such manual retrieval methods would not be supported. It seems that it would be more effective for you to check out your listserver's delivery logs to track down the problem. If such logs do not exist, you may want to enable such a feature, if available, to avoiding burdening mail-archive, and others, when troubleshooting errors when it is not even clear if mail delivery to mail-archive actually occurred for the messages in question. --ewh _______________________________________________ Gossip mailing list [EMAIL PROTECTED] http://jab.org/cgi-bin/mailman/listinfo/gossip
