Re: bad message id's

Professional Software Engineering writes:
> Have you tried taking the message and manually running it through a small
see below
> Looks like the rule was supposed to match VALID messageids, not match bad
Yes, that's rite.  Here's a rerun w/ verbose logging:

procmail: Match on ! "^Message-Id:[     ]*<[^   <>@]+(_at_)[^   <>@]+>[         
]*$"
procmail: Assigning "TRAP=formail -XMessage-Id:"
procmail: Assigning "LOG=Bad Message ID
"
Bad Message ID
procmail: Locking "Spam/.lock"
procmail: Executing "rcvstore,+Spam"
procmail: Assigning "LASTFOLDER=rcvstore +Spam"
procmail: Unlocking "Spam/.lock"
> From helm  Tue Mar 17 19:17:32 1998
 Subject:      NEXT DISIWG TELEVIDEO CONFERENCE 4/1
  Folder: rcvstore +Spam                                                   3717
procmail: Notified comsat: "helm@:rcvstore +Spam"
procmail: Assigning "EXITCODE=0"
procmail: Executing "formail,-XMessage-Id:"
Message-ID:  <M10250103.005.z2j35.1.980317164507Z
 .CC-MAIL*/O=HQ/PRMD=USDOE/ADMD=ATTMAIL/C=US
             /@MHS>

So, why does it reject this message id if it's legit?