Can SABnzbd download based on msg-id like ?

[sander]

Hi,

Can I instruct SAB to download a certain post based on it's message-id like ? If not directly, can I easily create a NZB with only one message-id?

I tried to create a fake NZB, with that message-id in it (see below), but the size is the problem: filling out a random numer does not work; SAB compalins about out-of-retention. So I guess SAB does checking on the download size versus the NZB specified size (which I don't know before hand). :-(

So: tips? Ideas?





   
     alt.binaries.ftd
   
   
     blablalbal@blaba.net
   

 



EDIT:

PS: Yes, with a manual telnet / NNTP session to a newsserver, it's easy to get the message: HEAD or ARTICLE or BODY will do. And somewhere in SAB, SAB will use that. But how can I instruct SAB to download a certain message-id ... ?

[shypike]

SABnzbd expects a valid yEnc or uuencoded message.
It will just ignore other formats.
It expects a file and it complains about retention because at the end of the NZB
it doesn't have any file.
The size parameter has nothing to do with it.

What are you up to?

[sander]

SABnzbd expects a valid yEnc or uuencoded message.
It will just ignore other formats.
It expects a file and it complains about retention because at the end of the NZB
it doesn't have any file.
The size parameter has nothing to do with it.

Ah. You're good: I did a manul BODY-retrieve of the message, and ... it was a binary message. No ASCII nor yEnc nor UUencode. So that is the reason? I didn't even you know you could use binary / 8-bit octets in Usenet?

What are you up to?

Ouch. You got me. I must confess I'm trying to reverse engineer a certain program that we are not allowed to discuss here ... it uses three different usenet groups for it's decentral communication ... ;-)

[shypike]

Why don't use use a universal Usenet client for this reverse engineering, like Grabit.

[sander]

Why don't use use a universal Usenet client for this reverse engineering, like Grabit.

Grabit is for Windows, which I don't have.

I used Thunderbird to have a look at the post. And a few lines of python are enough too:

Code: Select all

>>> import nntplib

>>> s = nntplib.NNTP('newszilla6.xs4all.nl')

>>> s.stat('<ZykYG8N95dczSfeTQAH2b@bla.net>')
('223 0 <ZykYG8N95dczSfeTQAH2b@bla.net> status', '0', '<ZykYG8N95dczSfeTQAH2b@bla.net>')

>>> s.body('<ZykYG8N95dczSfeTQAH2b@bla.net>','mijnfile')
('222 0 <ZykYG8N95dczSfeTQAH2b@bla.net> body', '0', '<ZykYG8N95dczSfeTQAH2b@bla.net>', [])
>>> 

The problem seems to be the encoding of the body / resulting file (which goes into 'mijnfile'): binary stuff. Not a readable NZB. I don't know which encoding (*zip, sha1, rsa, ...) is used. :-(