kevin@kosman.UUCP (Kevin O'Gorman) (03/01/91)
I'm trying to set up an nntp newsfeed. I'm setting up three pieces of software: rn, cnews and nntp. I think the first two are going okay. Nntp can even receive news, and rn can mail replies. Cnews can post and receive news, and it can build outgoing queues. Nntp just can't get the news back to the newsfeed. When I try, nntpsend gives me a report like this: nntpsend: [8820] begin Thu Feb 28 19:40:47 PST 1991 nntpsend: [8820] begin gate.oxy.edu nntpxmit: /usr/NNTP/NEWSARTS/to/tiger/7: message-id syntax error: 273 nntpxmit: gate.oxy.edu stats 0 offered 0 accepted 0 rejected 0 failed nntpxmit: gate.oxy.edu xmit user 0.067 system 0.100 elapsed 2.617 3.9 real 0.0 user 0.1 sys nntpsend: [8820] end gate.oxy.edu nntpsend: [8820] end Thu Feb 28 19:40:53 PST 1991 It's the third line I'm worried about. There's nothing particular about the news article: it's regular cnews stuff, just like many things that oxy.edu sees every day. I'm not even sure what 'message-id' it's referring to. Anyway, the software is new, just snarfed from uunet in the last week, it's running on an Interactive Systems box running BSD 4.3. The feed is also BSD running B news and has been an nntp server for a while, so it's probably not anything at their end. Does anyone have any idea what I should be looking for? -- Kevin O'Gorman ( kevin@kosman.UUCP, kevin%kosman.uucp@nrc.com ) voice: 805-984-8042 Vital Computer Systems, 5115 Beachcomber, Oxnard, CA 93035 Non-Disclaimer: my boss is me, and he stands behind everything I say.
molenda@s1.msi.umn.edu (Jason Molenda) (03/03/91)
kevin@kosman.UUCP (Kevin O'Gorman) writes: > nntpxmit: /usr/NNTP/NEWSARTS/to/tiger/7: message-id syntax error: 273 What flag are you using in the Cnews sys file? If I remember correctly, the default is "f" which will output two fields for each article in the togo file, the location of the article and the size. Normal nntpxmit expects to see what is output by "F", just the location of the article. With nntp 1.5.11, you can use "n" which puts the location of the article and the message-ID so nntpxmit doesn't have to scan out the message-ID for each article (a big performance win). My guess is you are using nntp 1.5.11 and it thinks that the second field in the togo file is the Message-ID when in fact it is the size of the article. This would probably cause nntpxmit to barf. I suppose I could actually look at the source to confirm/deny this supposition, but I'd like to hear what flag you're using in the sys file first. -- More information that you couldn't have existed another day without, from: Jason Molenda, Tech Support, Iris & News Admin, Minnesota Supercomputer Inst molenda@s1.msi.umn.edu || molenda%msi.umn.edu@umnacvx.bitnet "And remember: Evil will always prevail, because Good is dumb." -- Spaceballs