Ydecode

Your newsgroup server, you need to make a little adjustment to make it work with yDecode. To do so first click on your account name using the right mouse button to get a menu just like on the screenshot below and then select option properties. STEP 2 - Changing server name to localhost Now you will get to a window similar to the one below. Replace your server name with localhost just like on the screenshot below. Remember - it's not local host (two words) but one word - localhost. It must be exactly like this. This will redirect Outlook Express from your news server to yDecode (yDecode is in fact a server). The server name that used to be here should be now in yDecode NNTP server name box. Do not modify other settings except server name, even if they look different than the screenshot below, especially not Account name and Password settings! Press OK to close this window.STEP 3 - Testing if it works By this point you should have it operational. Do not close yDecode - it must be running every time you read newsgroups from now on. Now, select some newsgroups that hold yEnc posts and try to display them... yDecode will do the rest! TIP: For proper Multipart handling, please make sure your news client downloads as much headers as possible. For Outlook Express users: - go to Tools menu and select Options. Make sure option "Get 300 headers at a time" is UNCHECKED under "Read" tab. Take a look at the screenshot below for example. Outlook Express Windows Mail Windows Live Mail By default main menu is not visible - this is how you access options. You can also click Show menu bar to enable main menu. (Configuration part 2 of 2) - Configuring Mozilla Thunderbird to work with yDecode If you are using Mozilla Thunderbird instead of Outlook Express first configure yDecode just like described above. Note that Test Config button will not be able to detect if you properly configured Mozilla Thunderbird. However, server connection will be tested successfully. Regardless of inability to check account settings for Mozilla Thunderbird, yDecode will still work with it as well as with any other news reader. To configure Mozilla Thunderbird, simply follow the steps on the screenshots below. [Top of page]

Beginners - you can leave this list empty and everything will work correctly. You require this only if you connect to yDecode from more than one computer at once (e.g. yDecode is installed on one computer and accessed from another). In case you are running yDecode on a computer where you also run newsreader software such as Outlook Express, you don't have to edit this list at all - you may leave it empty and it will work.The list of IP addresses shows allowed or explicitly disallowed addresses. By using Add / Edit / Remove and Arrow buttons you can do appropriate action on selected address. Simply click on the address you wish to edit and press appropriate button.IP address 127.0.0.1 (or localhost) is always allowed regardless of the list entries (even if the list is empty). This is no security breach because it allows access only to a computer where yDecode is started and none of the others.NOTE: Demo version allows only connections from 127.0.0.1 and from no other IP address. To remove this limitation please register and get full version!IP filtering works like this: by default it blocks access from ALL IP addresses except those that are added as allowed and 127.0.0.1 which is always allowed (even if it isn't in the list). If you wish to add a range of addresses you can use wildcards like * and -The picture below shows an example connection from 3 computers running Outlook Express to the computer running yDecode. yDecode

_getMessage('alt.binaries.te...', '1486783640.8004...')#4 /site/nzedb/NZBContents.php(132): nzedb\NNTP->getMessages('alt.binaries.te...', '1486783640.8004...', false)#5 /site/nzedb/Nfo.php(368): nzedb\NZBContents->getNfoFromNZB('be2f52efff0b7ed...', '4220157', '156', 'alt.binaries.te...')#6 /site/misc/update/nix/multiprocessing/.do_not_run/switch.php(243): nzedb\Nfo->processNfoFiles(Object(nzedb\NNTP), '', 'b')#7 {main} thrown in /site/app/extensions/util/yenc/adapter/Ydecode.php on line 52PHP Fatal error: Uncaught exception 'Exception' with message 'Error getting data from yydecode.' in /site/app/extensions/util/yenc/adapter/Ydecode.php:52Stack trace:#0 /site/app/extensions/util/yenc/adapter/Ydecode.php(60): app\extensions\util\yenc\adapter\Ydecode::decode('\r\n=ybegin part=...', true)#1 /site/app/extensions/util/Yenc.php(64): app\extensions\util\yenc\adapter\Ydecode::decodeIgnore('\r\n=ybegin part=...')#2 /site/nzedb/NNTP.php(1452): app\extensions\util\Yenc::decodeIgnore('\r\n=ybegin part=...')#3 /site/nzedb/NNTP.php(629): nzedb\NNTP->_getMessage('alt.binaries.te...', '1486776814.5265...')#4 /site/nzedb/NZBContents.php(132): nzedb\NNTP->getMessages('alt.binaries.te...', '1486776814.5265...', false)#5 /site/nzedb/Nfo.php(368): nzedb\NZBContents->getNfoFromNZB('e63afed6c67c168...', '4207497', '156', 'alt.binaries.te...')#6 /site/misc/update/nix/multiprocessing/.do_not_run/switch.php(243): nzedb\Nfo->processNfoFiles(Object(nzedb\NNTP), '', 'e')#7 {main} thrown in /site/app/extensions/util/yenc/adapter/Ydecode.php on line 52PHP Fatal error: Uncaught exception 'Exception' with message 'Error getting data from yydecode.' in /site/app/extensions/util/yenc/adapter/Ydecode.php:52Stack trace:#0 /site/app/extensions/util/yenc/adapter/Ydecode.php(60): app\extensions\util\yenc\adapter\Ydecode::decode('=ybegin part=1 ...', true)#1 /site/app/extensions/util/Yenc.php(64): app\extensions\util\yenc\adapter\Ydecode::decodeIgnore('=ybegin part=1 ...')#2 /site/nzedb/NNTP.php(1452): app\extensions\util\Yenc::decodeIgnore('=ybegin part=1 ...')#3 /site/nzedb/NNTP.php(629): nzedb\NNTP->_getMessage('alt.binaries.te...', '1486790285.1521...')#4 /site/nzedb/NZBContents.php(132): nzedb\NNTP->getMessages('alt.binaries.te...', '1486790285.1521...', false)#5 /site/nzedb/Nfo.php(368): nzedb\NZBContents->getNfoFromNZB('a2dbc9e82d193c3...', '4252459', '156', 'alt.binaries.te...')#6 /site/misc/update/nix/multiprocessing/.do_not_run/switch.php(243): nzedb\Nfo->processNfoFiles(Object(nzedb\NNTP), '', 'a')#7 {main} thrown in /site/app/extensions/util/yenc/adapter/Ydecode.php on line 52PHP Fatal error: Uncaught exception 'Exception' with message 'Error getting data from yydecode.' in /site/app/extensions/util/yenc/adapter/Ydecode.php:52Stack trace:#0 /site/app/extensions/util/yenc/adapter/Ydecode.php(60): app\extensions\util\yenc\adapter\Ydecode::decode('\r\n=ybegin part=...', true)#1 /site/app/extensions/util/Yenc.php(64): app\extensions\util\yenc\adapter\Ydecode::decodeIgnore('\r\n=ybegin part=...')#2 /site/nzedb/NNTP.php(1452): app\extensions\util\Yenc::decodeIgnore('\r\n=ybegin part=...')#3 /site/nzedb/NNTP.php(629): nzedb\NNTP->_getMessage('alt.binaries.te...', 'part1of1.kCQsQ$...')#4 /site/nzedb/NZBContents.php(132): nzedb\NNTP->getMessages('alt.binaries.te...', 'part1of1.kCQsQ$...', false)#5 /site/nzedb/Nfo.php(368): nzedb\NZBContents->getNfoFromNZB('993e72d7cf0f7bb...', '4249282', '156', 'alt.binaries.te...')#6 /site/misc/update/nix/multiprocessing/.do_not_run/switch.php(243): nzedb\Nfo->processNfoFiles(Object(nzedb\NNTP), '', '9')#7 {main} thrown in /site/app/extensions/util/yenc/adapter/Ydecode.php on line 52.....">PHP Fatal error: Uncaught exception 'Exception' with message 'Error getting data from yydecode.' in /site/app/extensions/util/yenc/adapter/Ydecode.php:52 [45/2874]Stack trace:#0 /site/app/extensions/util/yenc/adapter/Ydecode.php(60): app\extensions\util\yenc\adapter\Ydecode::decode('=ybegin part=1 ...', true)#1 /site/app/extensions/util/Yenc.php(64): app\extensions\util\yenc\adapter\Ydecode::decodeIgnore('=ybegin part=1 ...')#2 /site/nzedb/NNTP.php(1452): app\extensions\util\Yenc::decodeIgnore('=ybegin part=1 ...')#3 /site/nzedb/NNTP.php(629): nzedb\NNTP->_getMessage('alt.binaries.te...', '1486783640.8004...')#4 /site/nzedb/NZBContents.php(132): nzedb\NNTP->getMessages('alt.binaries.te...', '1486783640.8004...', false)#5 /site/nzedb/Nfo.php(368): nzedb\NZBContents->getNfoFromNZB('be2f52efff0b7ed...', '4220157', '156', 'alt.binaries.te...')#6 /site/misc/update/nix/multiprocessing/.do_not_run/switch.php(243): nzedb\Nfo->processNfoFiles(Object(nzedb\NNTP), '', 'b')#7 {main} thrown in /site/app/extensions/util/yenc/adapter/Ydecode.php on line 52PHP Fatal error: Uncaught exception 'Exception' with message 'Error getting data from yydecode.' in /site/app/extensions/util/yenc/adapter/Ydecode.php:52Stack trace:#0 /site/app/extensions/util/yenc/adapter/Ydecode.php(60): app\extensions\util\yenc\adapter\Ydecode::decode('\r\n=ybegin part=...', true)#1 /site/app/extensions/util/Yenc.php(64): app\extensions\util\yenc\adapter\Ydecode::decodeIgnore('\r\n=ybegin part=...')#2 /site/nzedb/NNTP.php(1452): app\extensions\util\Yenc::decodeIgnore('\r\n=ybegin part=...')#3 /site/nzedb/NNTP.php(629): nzedb\NNTP->_getMessage('alt.binaries.te...', '1486776814.5265...')#4 /site/nzedb/NZBContents.php(132): nzedb\NNTP->getMessages('alt.binaries.te...', '1486776814.5265...', false)#5 /site/nzedb/Nfo.php(368): nzedb\NZBContents->getNfoFromNZB('e63afed6c67c168...', '4207497', '156', 'alt.binaries.te...')#6 /site/misc/update/nix/multiprocessing/.do_not_run/switch.php(243): nzedb\Nfo->processNfoFiles(Object(nzedb\NNTP), '', 'e')#7 {main} thrown in /site/app/extensions/util/yenc/adapter/Ydecode.php on line 52PHP Fatal error: Uncaught exception 'Exception' with message 'Error getting data from yydecode.' in /site/app/extensions/util/yenc/adapter/Ydecode.php:52Stack trace:#0 /site/app/extensions/util/yenc/adapter/Ydecode.php(60): app\extensions\util\yenc\adapter\Ydecode::decode('=ybegin part=1 ...', true)#1 /site/app/extensions/util/Yenc.php(64): app\extensions\util\yenc\adapter\Ydecode::decodeIgnore('=ybegin part=1 ...')#2 /site/nzedb/NNTP.php(1452): app\extensions\util\Yenc::decodeIgnore('=ybegin part=1 ...')#3 /site/nzedb/NNTP.php(629): nzedb\NNTP->_getMessage('alt.binaries.te...', '1486790285.1521...')#4

Contents Quickstart Troubleshooting About Features Requirements Credits and Acknowledgments Manual Main Menu Indicators Servers Tab Connections Tab Attachments Tab IP Filtering Tab Logging Tab Options Tab Registration & Ordering QuickstartyDecode can auto-configure itself - simply answer "Yes" to the question that asks you to automatically configure yDecode after you start yDecode the very first time. If you answer "No" you can still start automatic configuration wizard later by clicking on Auto-Config button in yDecode.Following procedure should be used only if you are having issues with the automatic configuration or if you use some other news reader software unsupported by auto-config (such as Agent or Netscape News).Here is the basic scheme how yDecode works: So, you need to setup yDecode and your news reader. The following describes just that with the examples of Outlook Express, Windows Mail, Windows Live Mail and Mozilla Thunderbird. If you use some other news readerplease note - all news readers have similar settings but they are only placed on different locations so use this tutorial as a guideline. yDecode setup is identical for any newsreader only newsreader setup varies.(Configuration part 1 of 2) - Configuring yDecodeSTEP 1 - Enter your server (and optionally port and SSL) Enter your news server name into the NNTP Server Name box. In this example (screenshot below) we have news.yourhost.com - but this is only an example - you should replace this with your actual Usenet server name that you use. Also look at servers tab section of this help for more info. Don't modify other settings if unsure - 119 for both port values (see screenshot) and SSL box unchecked is fine most of the time. STEP 2 - Test configuration Make sure that your firewall is not blocking yDecode. Now you can test the connection to the server as well as news account configuration by pressing the Test Config button - you should get a window showing messages similar to these: Server connection availability is the important part here. Make sure you have no red-colored errors there. NOTE: Any red message in this window might indicate an error. Please look at servers tab section of this help for more info. At this point you may have some errors for accounts - but this is because you haven't configured accounts yet - which you will do in the following step. So for now, just ignore error messages for accounts. Note that accounts are only tested for supported news readers (Outlook Express, Windows Mail, Windows Live Mail, Mozilla Thunderbird) and you should ignore that test if you use other news reader. Take a look if the Server connection test passed without problems. If there are errors in server connection, please check your firewall - it must not block yDecode from connecting to the Internet. (Configuration part 2 of 2) - Configuring Outlook Express / Windows Mail / Windows Live Mail to work with yDecodeSTEP 1 - Getting into server properties Assuming that you already have configured newsgroup account that works with

Computer has IP address 192.168.0.1 and it allows IP addresses 192.168.0.2-4 to access it. All other IP addresses cannot access yDecode. Examples:allow: 127.0.0.* for range from 127.0.0.0 to 127.0.0.255allow: 127.0.1-5.* for range from 127.0.1.0 to 127.0.5.255 (all possible combinations).The rest of the addresses are denied! There is use for deny as well:deny: 127.0.0.5 will explicitly deny access from this address allow: 127.0.0.1-10 will allow all addresses from 127.0.0.1 to 127.0.0.10 except 127.0.0.5, which is denied above. Note that in the above example order of addresses in the list is significant. If you, in this example, replaced order of allow:127.0.0.1-10 with deny:127.0.0.5 it will not work as expected because first the range from 1-10 will be allowed (including 5) and then deny won't have any purpose as it has already been allowed in the line above.If you allow access to wrong IP addresses you may receive traffic from addresses you may not want to reach yDecode. They may consume your Internet bandwidth. You can always return to safe configuration by deleting all entries in the list.