How to upload using JBinUP
Notes for JbinUP:
NNTP and NNTPS support
No connection limits
Headercheck after upload
Batchfunction for WinRar and Par2
All uploads are encoded with the yEnc algorythm
Creation of NZB-files after finishing a JBinUp mission is possible
JbinUP is Freeware but it is possible to donate from €5.
Choose English on installation
File => Settings => Common Settings
The default number of lines is 3000. You can easily increase that to 5000.
Leave the rest as it is.
File => Settings => Server Settings
JbinUP has two main advantages.
- Verification of headers after upload. Which means that the the programme checks the upload before the end of the post, avoiding the possibility of incompletes or that the peering between two Usenet serves is ineffectual. This is why it is necessary to configure two Usenet servers. One is for the upload (Use Server for Uploads). You can choose the same for checking headers (in that case tick the three boxes at the bottom) or choose a second one (Use Server for Header Checks).
- JbinUP carries out the Upload in SSL (using NNTPS). This means your posts are secured in a safe tunnel between your computer and the Usenet servers where you make your post. Do not mistake this for anonymity, SSL will not make you anonymous, it protects the upload. The information about the poster is guaranteed (and has been for a long time) by the NNTP-posting-host header which replaces your IP upload address with the Usenet Service Provider address. The X-TRACE header encrypts information about the uploader (for example login, machine, ...). Be aware: post logs are sometimes kept on the Usenet server.
File => Settings => Poster Settings
File => Settings => Newsgroups Settings
For the first step, you click on Add to choose the files you want. The list should include RAR and PAR files, then click on forward.
Then the second step choose the group where you want to post and click Add Job.
The central window provides a summary of files to post.
Start the post
the post will begin
At the end of the post you can consult your Post Logs. Edit => Show application Log