Path: news.nzbot.com!not-for-mail
From: Ratty <AUser@nltworld.com>
Newsgroups: alt.binaries.pictures.erotica.spanking
Subject: Re: crc problems with xyzzy's posts
Message-ID: <b8lc4bl8l9eu53tiue603osjdpeobn7248@4ax.com>
References: <d5ia4blib22voil62vc1lp889ga2nae7j3@4ax.com>
X-Newsreader: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 26
X-Complaints-To: abuse@easynews.com
Organization: Easynews - www.easynews.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Fri, 13 Nov 2015 21:28:45 +0000
X-Received-Body-CRC: 4291980126
X-Received-Bytes: 1676
Xref: news.nzbot.com alt.binaries.pictures.erotica.spanking:731
You're right, it looks like they've been posted with an old version of
yEnc. I think yours is expecting 1.3 spec but it must be an earlier
spec.
It seems that Agent on Windows is happy without it. It's a pity as
with PAR2 files, it's not really that necessary - a bit of corruption
is easily fixed.
Might be worth asking around in the Linux world.
I could repost them sometime in the future as my poster seems
compliant.
Ratty
skywalker <skywalker@no.spam.invalid> wrote:
>I'm running on Linux and on every one of xyzzy's posts I get a crc error:
>
> 'pcrc32=' not found in end line
>
>And indeed, when I look at the packets, they end with:
>
>=yend size=512000 part=1 pcrc=0963B8DD crc32=01AB1409
>
>Is there a ydecoder that knows how to deal with this or is there some
>workaround to allow the decoding to happen? THANKS!!
> -:skywalker:-
|
|