Version 0.12.4

The new obfuscation method introduced in 0.12.3 was a bit too much for some newsreader clients.
This version dials this down a bit.

Additionally some indexers required file name extensions for .rar files in order to succesfully parse the generated nzb files.
To solve this a new parameter is introduced:

# When using random message subjects, if the filename ends with any of the configured strings below keep this extension on the random generated filename.
# Configure multiple strings separated by a |
# For example ".part1.rar|.par2|.par"
# Include the dots before the extension if you want to include it.
ForceIncludeExtensionsInSubject=".rar"

Take into account the . (dot) of the extension is also included in this configuration.

Version 0.12.3

This version fixes a potential security issue with the log4net version used. (improbable to affect previous versions due to what is used of log4net)

Additionally a new message obfuscation method is available.

To enable this add a new setting to your folder configuration:

# Use a random usenet message subject instead of the filename
# this extra obfuscation method makes it harder to reconstruct a message from usenet posts
# but might introduce issues with less advanced downloaders that check the message headers instead of the yenc headers.
UseRandomMessageSubjects=yes

The default value of this setting is no so the new method will only be used when you enable this setting.

What this new obfuscation method does:

For NZB's it seems the message subject does not matter at all, only the yenc header is looked at by the downloader. This setting makes it so all posted messages have a completely nonsensical subject. Only the nzb downloader with the nzb can reassemble the files.

It is possible downloaders other than sabnzbd and nzbget encounter issues with these nzbs, be aware of this possibility.

Version 0.12.2

This version fixes issues with the configuration loader being too strict in requiring some configuration parameters.
Empty values in NzbPostFilenameParam and NzbPostExtraParams are now permitted.

The default .Net version has also been increased from 4.5 tot 4.7.1 as this fixes some available TLS issues with some indexers.

Version 0.12.1

enhancements

• The nzbPost notification method has been extended to allow for a custom form field name to be used to place the nzb file in.

• The nzbPost notification method has gained the ability to specify extra form fields and values to post to the server.

Combined these two enhancements allow you to post the generated nzb files to any webform that has anonymous access. (cookie or http header based authentication is not supported, if demand arises this could be added as well)

When using these alterations to the notification method either NewznabSearch or Dummy have to be used as verification method. The former uses a generic newznab search method to find the uploaded release, the latter always assumes success and removes the upload from the backup folder.

Version 0.12.0

enhancements

• Par file creation is now executed in the context of the working folder, this makes it so all files to be parred can be passed with a relative path (no folder) and makes the overall command length much shorter.

• if a file or folder is accompanied by a file with the same name as the file or folder but with an .nfo extension this .nfo file will not be rarred or parred but instead get put next to the rars and pars in the nzb.

Version 0.11.5

Bugfixes

• Changed the method of writing nzb files to disk. If the nzb file already existed and new nzb contents length was less than existing old data was left behind generating an invalid nzb file.

Version 0.11.4.1

Version 0.11.4.1

Bugfixes

• removed extra logging that was used to pinpoint locking issue.

Version 0.11.4

Version 0.11.4

Bugfixes

• Reposts get moved back to the queue.
• By default .Net has no TCP timeout, this caused a posting thread hang when the server stopped responding.
• UploadAttempts counter was not always stored in the database, causing endless retry loops in certain cases.
• zero byte files or folders dropped in the watchfolder will no longer be picked up.

Version 0.11.2

Version 0.11.2

New features

• Added a new method to randomly assign a message ID instead of relying on the news provider to supply this (which gave predictable sequential message IDs)

• When a value of RANDOM is used in the FromAddress parameter a random string value is used for this.

• The max block size for par2 is now calculated based upon the maximum number of blocks.

Bugfixes

• A forgotten cast in the rar and par settings made it so that any size config over 2 GB wrapped around.

Version 0.11.0

Version 0.11.0

Major Changes

• Added support to use a completely custom par2 command this is mainly intended for people that want to use nodejs ParPar a sample ini file is included in the conf folder (99_nodejsParPar.ini) copy this to the userconf and modify the path to parpar as required to utilize this new functionality.
  (Note, this requires a working parpar installation)
• Added support to specify renaming exclusion masks in the folder configuration. Add CharsToRemove="()=@#$%^,?<>{}|" to an existing folder config and modify as required. or start anew from the template (where it has been included)
• The database cleanup script now also runs an SQLite vacuum statement, this keeps the database size somewhat more under control.

Minor Changes

• At startup the database version is now also shown in the log.
• External process feedback now works with a custom stream instead of the framework events (that only trigger at newlines) this will probably prevent timeouts on slower devices that take a long time to create par2 files (even when using the standard par2cmdline)