Upgrades to 0.88

================

Version 0.88 contains two BREAKING CHANGES.

BREAKING CHANGE #1: may, deliberately, cause connections to fail which

previously succeeded.

If the Sieve server does not offer STARTTLS, then connections should now fail

unless one of three scenarios is in play:

* `--clearchan` is explicitly passed on the command-line

* `SIEVECONNECT_INSECURE_CLEARTEXT_FALLBACK` is set non-empty in

  environ

* TLS verification is disabled, whether by packagers or command-line.

The stance now is: if you try for TLS, don't fall back to non-TLS, unless

explicitly told that it's okay.  I've explicitly and deliberately changed to

handling MitM attacks stripping pre-TLS capabilities as part of the threat

model, and breaking in that scenario is now more important than "just working".

This is a pre-v1 tool, so I hope to be forgiven for this change.  It's my

belief that the world has changed enough that it's no longer socially

acceptable to run services without TLS and without users knowing to disable

TLS.

(POSSIBLY) BREAKING CHANGE #2: when deriving a remote script name from the

local filename, use the basename and strip off directories.

Some widespread ManageSieve servers (eg, timsieved) disallow a directory

separator in a sieve script name.  So when deriving remote names, just use

basename.  This might cause issues for those with servers which allow directory

separators and users who were relying upon this.

Mitigation: explicitly specify the remote script name to include the path, and

things should work as before.

Full ChangeLog can be found at:

http://people.spodhuis.org/phil.pennock/software/sieve-connect.ChangeLog.txt