Forums / Support / long and silly postingnames/subjects make BB decode crazy stuff

long and silly postingnames/subjects make BB decode crazy stuff

by Shinji @
Hello

Sometimes, when a Poster uses a silly long filename/subject with dots and so BB only saves the file partially.

Example:
An 8 GB big contentfile is splitted in 169 attachmentfiles (50MB each) and each of the attachmentfiles consits of around 201 partfiles (around 260kB each) in separate postings.
contentfile: "DETEKTIV CONAN MOVIE 01 DER TICKENDE WOLKENKRATZER.1080P.BLURAY.DE.JAP.ENG.MKV BY AYUMI"
is posted in <4f1ee1b8$0$2395$6d4919ba@reader.astinews.de> (and similar postings).
Those are written by BB with name(s) like
"usenet4ever.info-Sponsored by www.Secretusenet.com.097.201.BBT"

With a bit of fantasy, you can see, that the other Postings (partfiles Part001.rar - Part169.rar) will be named almost the same.
===
Dir F:\BB-PARTS
258.624 usenet4ever.info-Sponsored by www.Secretusenet.com.001.201.BBT
258.625 usenet4ever.info-Sponsored by www.Secretusenet.com.002.201.BBT
258.680 usenet4ever.info-Sponsored by www.Secretusenet.com.003.201.BBT
...and so on...
===

When I use more than 1 download slot/connection at a time, it happens so, that BB downloads postings from more attachmentfiles at the same time.
And since it does not use different partfile-names, it decodes them all together in one attachmentfile since it finds the partfiles 001 up to 201 (even if they came from different Attachmentfiles).

With so big (and silly named) contentfiles it is almost impossible to download the postings and decode them in the correct way.


Maybe it is possible to insert a significant part of the real attachmentfilename in the saved partsfile so BB has a chance to decode the correct partfiles to create the attachmentfile?
 

BinaryBoy's reply to Shinji #15645 @

Yes, using the real filename from the body could help resolve this. In the past that wasn't possible because the name was stored only in part 1. Now most of the time it's stored in all parts because of yEnc. In the case of older encoding methods, it could fall back to guessing based on the subject.
 

nikkil's reply to BinaryBoy #16049 @

Is there an update that would autmatically fix this instead of a work around?
 

BinaryBoy's reply to nikkil #16054 @

Only if the article happens to be in MIME format. MIME stores the filename in the header. Binary Boy will grab that filename and rename the BBT file appropriately even if the subject is messed up.