> I know I once saw a mailer that stuck the sender's
> address inside the message-id; this caused some
> grief. Maybe it is stultifyingly rare, though.

I believe a mailing list source package (ListServ?)
did this.

It is a real pain since a single message will have
a different message-id for each receipient. I think
this violates the semantics of message-id, where the
message-id should be the same for the same message.

I'm not sure it is worth the risk of false
negatives, but maybe it makes sense to consult
the message-ID database when deciding whether
something is an address or not. It would be really
cool to support automatic linking to the
relevant HTML page if a message-ID matches.

I know I once saw a mailer that stuck the sender's
address inside the message-id; this caused some
grief. Maybe it is stultifyingly rare, though.

============================

On the archive pages, messaged IDs are treated like e-mail addresses and bunged. Is there something that you can do about this?

> I don't see an obvious way to exclude it and include real email
> addresses using a regexp.

> Do you have a suggestion?

If it is prefixed with mid or msgid, perhaps? Or, maybe if the list in question already contains a message with that message ID (this doesn't work when lists refer to each other, however). Aside from those, no, I cannot think of a good way to simultaneously protect e-mail addresses and display message IDs.