release-1.1

This release contains a breaking change. In the past you would add a cron-job to poll the feeds, and email you the appropriate new items via the addition of a cronjob like this:

00 * * * * $HOME/bin-ssh/rss2email cron 2>/dev/null
30 * * * * $HOME/bin-ssh/rss2email cron 2>/dev/null 

Now you must specify the recipient explicitly:

00 * * * * $HOME/bin-ssh/rss2email cron [email protected] 2>/dev/null
30 * * * * $HOME/bin-ssh/rss2email cron [email protected] 2>/dev/null 

This change has been made because I'm no longer running this tool on my SMTP-host, so mails to $LOGNAME (i.e. "steve") cannot be delivered. Instead I must explicitly list the email address to notify.

As a bonus you can specify multiple email addresses:

rss2email cron [email protected] [email protected] [email protected]

I'm not sure that will be useful, but it was an easy thing to support.

release-1.0

This release changes the handling of failures to process an RSS feed; previously if a feed-item couldn't be processed it would be retried the next time the cron-handler ran, which would lead to a flood of non-stop errors.

To avoid this we now mark feed-items as having been processed before we generate any emails, which means that any error processing a feed item will be alerted about only once, then the item will be discarded/marked as processed. This is still a kind of failure, but it is a failure which will occur only once, rather than every ten minutes.

In addition to this feature-change there have been some linting and code-quality improvements made.

This release is being made solely to transition the testing and release process from TravisCI to github actions:

• github-action-tester
  • Used to run tests.
• github-action-publish-binaries
  • Used to make releases.

This release updates the handling of (atom) feeds, to use the contents of the Description field of the remote feed, if the "Content" field is empty.

This release updates the emails which are generated to include a link to the item which was being notified about.

This helps when sites publish blog-posts, articles, etc, which don't actually link to themselves.

This release contains zero functional changes, it only fixes a spelling mistake in a comment.

This release features several internal cleanups of the code-base, partly for neatness, and partly to improve portability. For example now we correctly store our feed-state and feed-list beneath the user's home directory regardless of whether the environmental variable HOME is set.

The new feature in this release is the ability to process all feeds without sending email notifications. This is useful when you add a new feed, and don't wish to receive every existing item as an email initially, and can be used like so:

 $ rss2email add https://blog.steve.fi/index.rss
 $ rss2email cron -send=false

This release moves our code from being implemented in a single file, to being split based upon sub-commands.

The whole notion of sub-commands is new, but should be natural for either a golang-user, or an r2e migration.

• Add a new URL to our feed-list
  • rss2email add https://example.com/blog.rss
• Delete an URL from the feed list
  • rss2email delete https://example.com/blog.rss
• List the feeds that are being monitored:
  • rss2email list
• Process the feeds, sending email on new items:
  • rss2email cron

The other new feature in this release is the sending of multi-part emails. The generated emails will now contain text/html and text/plain parts, allowing you to view whichever you prefer.

This release updates the process of sending email to use the environmental variable $LOGNAME instead of $LOGIN - because this should always be available under cron, whereas $LOGIN probably won't be.

Almost all possible errors in sending the email are now explicitly detected, to avoid failures to see RSS-items. If there is an error sending the mail then the feed-item will not be marked as seen, such that it will be retried the next time cron runs.

This is the first release for which binaries are automatically built via travis.

The auto-built binary will contain a version number set appropriately, and this may be viewed via:

 rss2email -version

This is our initial release of a functioning-project.