Version: 0.7.2 (using KDE 3.1.3) Installed from: SuSE Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB-athlon I saw a bugreport seemingly on the same topic, which said that the feature was already present, but then I'm puzzled, because I didn't find it... I haven't been able to use KNode to any download binary file from a newsgroup. I used Pan and KNode in parallel, to be able to compare. In KNode, if there is a binary file attached to a message (usually a RAR archive part), all I get is a very long string of garbage in the message body, as KNode probably tries to display it as text. So I tried to right-click everywhere, to look in the menus, in order to find the option to save the attachment, and found nothing. In Pan, I can right-click on the message in the message list and choose to save the attachments. There is even a queueing system for the downloads. So my wish is: make KNode aware of binary attachments, enable to download them with a queueing system (maybe KGet?) Thanks for your attention!
If that may help, when I'm speaking of binary attachments, I mean yEnc-encoded attachments. yEnc is the standard format used in all alt.binaries newsgroups I know. See http://www.yenc.org for the specs. Thank you for your attention!
I agree wholeheartedly with this request. Lack of binary support is the one thing holding me back from using KNode instead of Pan. Please support yEnc and UUE multipart messages and provide a way to easily download them.
Adrian, multipart binaries are already covered in Bug 22447. This bug seems to deal exclusively with yEnc-encoded binaries, in which case perhaps it's a duplicate of Bug 54389...?
I'm the reporter of the bugreport. Yes, my bugreport is a duplicate of 22447 (sorry, I hadn't seen that one, perhaps because it was very old). I'll transfer my votes to 22447 and let you close that report. On the other hand, bugreport 54389 is very vague and I would not consider my bugreport as a duplicate of that one. Thanks for your attention!
*** This bug has been marked as a duplicate of 22447 ***