[news.admin] Bad message-ids make nntp croak

matt@oddjob.UChicago.EDU (Ka Kahula) (03/06/87)

Messages from UMass.bitnet are showing up, chiefly in mod.music.gaffa,
with message-ids that do not conform to rfc850/rfc822.  Example:

   Message-ID: <870304165022.0000028A.AEHS.MA@UMass> (UMass-Mailer 4.03)

The extra string after the '>' is causing nntp servers to abort
connections.  I have sent mail to postmaster@UMass.bitnet and I will
post a cure for the nntp trouble.

By the way, most messages in mod.music.gaffa also have

   Reply-To: Love-Hounds

Very few have a hostname in this field.
________________________________________________________
Matt	     University		matt@oddjob.uchicago.edu
Crawford     of Chicago     {astrovax,ihnp4}!oddjob!matt

ron@brl-sem.ARPA (Ron Natalie <ron>) (03/07/87)

In article <3685@oddjob.UChicago.EDU>, matt@oddjob.UChicago.EDU (Ka Kahula) writes:
 > Messages from UMass.bitnet are showing up, chiefly in mod.music.gaffa,
 > with message-ids that do not conform to rfc850/rfc822.  Example:
 > 
 >    Message-ID: <870304165022.0000028A.AEHS.MA@UMass> (UMass-Mailer 4.03)
 > 
 > The extra string after the '>' is causing nntp servers to abort
 > connections.  I have sent mail to postmaster@UMass.bitnet and I will
 > post a cure for the nntp trouble.

The string in parentheses is legal.  Someone should fix NNTP.
It should ignore comments.

-Ron