Allen Prunty wrote to Digital Man <=-
Try enabling the debug output (add "debug" line to your newslink.cfg file). And then paste the last log output line before the "hang" here.
rsp: X-RFC2646: Format=Flowed; Original
rsp: Message-ID: <51777$557509a5$454272b8$4357@ALLTEL.NET>
rsp: X-Complaints-To: firstname.lastname@example.org
rsp: Organization: UseNetServer.com
rsp: Lines: 4
rsp: X-Trace: 51777557509a5e0e7d71d04357
rsp: X-Received-Bytes: 775
rsp: X-Received-Body-CRC: 3519384017
rsp: Bytes: 1026
rsp: Xref: number.nntp.giganews.com alt.activism.chronic-pain:141
rsp: NFL Message Board. New Members Wanted! Free. Check it out. Join us today! rsp: http://falconsfanforum.freeforums.net/
Alprunty wrote to Bill McGarrity <=-
Re: Re: newslink hanging
By: Bill McGarrity to Allen Prunty on Sat Apr 16 2016 10:46 am
Could it be possible you have a typo in your newslink.cfg file regarding the above code? Make sure the msgbase codes are identical in both the cfg file and msgbase internal code. The cfg file is telling your provider what usenet group to pull but Synch doesn't have a clue where you want to put it.
No it's not that... I've posted other examples. The common denomiator when it errors out is...
the rsp: .
And the fact that the message is very large and looks like a binary
that it can't decode. I think people are posting graphics in text newsgroups or something.
|Location:||Riverside County, California|
|Nodes:||15 (1 / 14)|