SABnzbd Forums

A poorly operating news server has been sending me a lot of badly formed yEnc articles intermittantly. In the article body the yEnc begins, gets truncated, and starts over with a second =ybegin string. So these badly formed articles have two =ybegin and one =yend. I noticed that one old newsreader (BNR2) that people don't use much anymore is actually tolerant of these malformed articles; when it gets to the second =ybegin it discards the previous yEnc as junk and is able to salvage the good yEnc in the rest of the article. So although it reports an error about unexpected end of encoded data, the decoded files are good. I think SABnzbd attempts to decode the whole body between the first =ybegin and the =yend. Easy for you to change that or just let it go?

There is already an option in Config->switches that lets you
choose between strict and non-strict checking.
Although this is less tolerant than what you ask for.
So far I have never seen a compelling reason to do this.
Do you have any reason to believe this happens frequently on
servers other than the one you're using?