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#[EMAIL PROTECTED]> 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#[EMAIL PROTECTED]> 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
