Skip to content

Releases: joeyates/imap-backup

Handle multi fetch failure gracefully

10 Jun 08:03
Compare
Choose a tag to compare

When a fetch fails (often because a locally backed-up folder no longer exists on the server), simply log an error an continue.

Update flags in transactions and deprecate Ruby 2.x

04 Jun 08:53
Compare
Choose a tag to compare

Changed

  • Implemented update in transactions. Previous only appends were handled.
    This allows actions which modify existing emails to be handled inside
    transactions when using the 'delayed_metadata' strategy.

  • Update flags in a transaction, speeding up flag refreshes by avoiding
    repeated writes of the JSON metadata file. This is a change inspired by
    this pull request: #200.

  • Deprecated Ruby 2.x Support

Handle `--mirror` in single backup

30 Mar 10:28
Compare
Choose a tag to compare

Fixed a bug in single backup where the --mirror parameter was ignored.

Added handling of `--delimiter` and `--prefix` options for `imap-backup restore`

31 Jan 10:14
Compare
Choose a tag to compare

When the server has a delimiter that is different from the default /, the user can now specify the value.

When the server uses a namespace (that was not present at the moment of backup), it is now possible to specify it.

Suppress Spurious 'Invalid File' Warnings

22 Jan 09:11
Compare
Choose a tag to compare

Suppressed mailbox and metadata '...is invalid' messages when these
files are missing. Now, the messages are printed when a file is
actually malformed.

Bugfix: corrected the behaviour of the legacy metadata convertor

18 Jan 10:57
Compare
Choose a tag to compare

Previously, mailboxes and metadata files would get deleted after migration.

Permit use of TLSv1.3

13 Jan 18:29
Compare
Choose a tag to compare
v14.5.0

Version 14.5.0

Documentation-only Release

24 Nov 08:30
Compare
Choose a tag to compare

This release serves only to update the documentation at rubydoc.info

Bugfix for container

17 Nov 12:09
Compare
Choose a tag to compare

Bugfix: check for the presence of the spec directory before conditionally activating code coverage

Split user and developer documentation

17 Nov 12:00
Compare
Choose a tag to compare

Documentation is now split into two areas:

  • End-user facing: via the README on GitHub
  • Developer: via a different main YARD page on rubydoc.info