Heinrich Müller posted on Thu, 24 Jan 2013 17:01:53 +0100 as excerpted: > xzver uses plain old nntp, so you would get a compressed binary stream, > as with gzip. The only indication whether or not it worked would be > hidden in the response code
Shouldn't another indication be the compressed binary stream itself? As long as you know you're downloading the overview file only (yenc is pretty close to binary, so if you're downloading yenced attachments at the same time...), if the raw ncat results in a string of binary gibberish, not the normal text of nntp, you know it's getting /something/ binary. And if that /something/ results in a bunch of new message overviews/headers reconstructed correctly within pan, then you know it must have been the compressed overview file (aka headers). -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman _______________________________________________ Pan-users mailing list Pan-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/pan-users
