heather@athena.cs.uga.edu (Heather Pritchett) (04/26/91)
The Problem: Clients can only post locally, no matter what distribution they give. The Supposed Solution: Change the 'L' flag in your /usr/lib/news/sys to 'L1', since just an 'L' defaults to 'L0' and that means clients can only post locally. Sounds like the perfect solution? The Continued Problem: Client posts still don't go out. They get placed in the out.going file, but nntpsend refuses to send them. The Problem Narrowed Down: After a little fiddling it is discovered that what is missing from the client messages is the date. If a date is borrowed from a working message and placed on the bottom of the header, the message gets sent out. (we test posted to alt.test) Just To Confuse Matters: I went back to the /usr/lib/news/sys file and changed the flag back to just 'L', then I added a date to the bottom of a message. It went out?!? Apparently the 'L' flag made no difference! The Facts: Our server is a Sun 4/380, running SunOS 4.1.1. We're using rn, v 4.3.2.4 (patch #47), and NNTP server version 1.5.10. Question #1: Am I using the L flag correctly? Question #2: Would changing the default header to include the date allow clients to post? Question #3: If so, where do I change the clients default header? If none of the above questions are valid does anyone have any ideas as to what would work? E-mail or Post, I read both! Heather Pritchett Computer Science Dept, heather@athena.cs.uga.edu University of Georgia
wisner@delius.Gryphon.COM (Bill Wisner) (04/28/91)
Make sure that you defined INEWS correctly in common/conf.h when building NNTP. inews will insert a Date: header is there isn't one present, but if NNTP is feeding your article into rnews or relaynews all bets are off. Bill Wisner <wisner@delius.Gryphon.COM> Gryphon Gang Fairbanks AK 99775 "If I decide to let my users send to bang-path addresses by jumping up and down on their left foot while hitting the F1 key that's my business." -- Mark Strawcutter <MJSTRAW@IUP.BITNET>