igb@fulcrum.bt.co.uk (Ian G Batten) (10/19/89)
What is the bhudda nature of a message-id with a SPACE in it? I was forced to use nntpxfer this afternoon; I informed my feed that we would be without power overnight, so he shut the feed off. We got power back, but the feed's not back yet, so I'm pulling it from this end. nntpxfer choked on this message: <120actuyA NKE EDU> because presenting this as a message-id with ARTICLE barfs. I'm running 1.5.5, by the way. IHAVE <120actuyA NKE EDU> fails too. I've special cased it in nntpxfer just to get the transfers done, with an if (strchr (articleid, ' ')) return (0); but this isn't the whole answer. And I'll never get to see one message (sniff). ian -- Ian G Batten, BT Fulcrum - igb@fulcrum.bt.co.uk - ...!uunet!ukc!fulcrum!igb
henry@utzoo.uucp (Henry Spencer) (10/20/89)
In article <215@masalla.fulcrum.bt.co.uk> igb@fulcrum.bt.co.uk (Ian G Batten) writes: >What is the bhudda nature of a message-id with a SPACE in it? It's illegal, pure and simple. Unfortunately we don't have Network Police to come over and haul away the turkeys who write software that generates such botches. -- A bit of tolerance is worth a | Henry Spencer at U of Toronto Zoology megabyte of flaming. | uunet!attcan!utzoo!henry henry@zoo.toronto.edu
fair@Apple.COM (Erik E. Fair) (10/28/89)
I suggest that you rip the message-ID syntax checker out of nntpxmit and punch it into nntpxfer, so that you'll never have to worry about this again. That syntax checker looks for all manner of illegalities, and has saved the Internet portion of USENET from much grief and destruction (like the time that microsoft let loose three messages with tabs in the message-IDs - boy was *that* a mess). Erik E. Fair apple!fair fair@apple.com