You can probably combine these two recipes into a single one. Ron posted
a much better one that checks just about every aspect of RFC compliance
a while back. You can see it at
http://www.rosat.mpe-garching.mpg.de/mailing-lists/procmail/1998-03/msg00268.html
Philip Guenther posted a very complete regexp back in March. Grep the
archive for the "bad message id's" thread.
You're right -- it was Philip Guenther. Philip, my apologies for
attributing your code to someone else!
Anyhow, the URL above should link right to it.
The rules caught incomimg Message-Id:'s with "<@host.domain.com>". The sender
was in the domain of one of the "TOP 5 PC makers", btw ...
Yes, I'm shocked by the number of invalid message-ids that I come
across. Right now I have a script that auto-replies to the postmaster
at an offender's site, explaining what RFC compliance requires. So
far a couple of major companies have come back and said that they'll
fix it, and some actually have. Most problems seem to come from
home-grown scripts to do trouble tickets, etc.
Chris