Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!europa.asd.contel.com!seka.scc.com!enger
From: enger@seka.scc.com (Robert M. Enger)
Newsgroups: news.software.nntp
Subject: Re: NNTPD hates Message-IDs with TWO '@'s in them.  (BIG log file attached to this posting)
Keywords: message-id nntpd duplicate
Message-ID: <1991Jun10.164931.21555@europa.asd.contel.com>
Date: 10 Jun 91 16:49:31 GMT
References: <1991Jun9.232828.17956@europa.asd.contel.com> <5930@gazette.bcm.tmc.edu>
Sender: news@europa.asd.contel.com (News)
Reply-To: enger@seka.scc.com
Organization: CONTEL Federal Systems
Lines: 29
Nntp-Posting-Host: seka.scc.com

Hi Stan:

Thanks for responding to my call for help/guidance.

I too took a look at the code, but at the NNTPD server.
I can't figure out WHY it does not recognize the fact that the 'bogus'
message id is ALREADY in the database.  

NNTPD correctly looks for the LAST '@' in the string, and lower-cases 
what is after it, etc.  This looks like good behavior.  
I could not spot any string variables which were ripe to overflow, etc.   
Any ideas why it doesn't work right?

The only difference I could spot was that NNTPD used 'fetch' to access
the data base, while NEWSHIST ultimately called dbzfetch.
Do these behave differently under this 'unusual' circumstance?

Thanks again for responding.  
Bob

ps
Is there someone responsible for notifying the offending site that
they are generating bad message-id fields?  

-- 

Robert M. Enger
CONTEL Federal Systems
enger@seka.scc.com  (Internet)