Version 0.2
===========

• libisds version 0.6 is required for this Shigofumi release.

• Public key infrastructure and one-time password authentication by client
against ISDS server are implemented now. See `login' command options for more
details.

• New command `set' shows current settings as one long listings.

• New command `cat' prints binary stream of current message. You should
redirect the output to a command. Otherwise your terminal can become funky.

• New command `catdoc' prints binary stream of document. XML documents are
serialized in the same manner as with `savedoc' command.

• New command `opendoc' opens message document in an external viewer. Default
is xdg-open. You can redefine it with `open_command' configure option.
Temporary file is used to pass the document to the viewer. Removing the files
is controlled by `clean_temporary_files' configure option.

• New command `boxlist' obtains ZIP archive of all boxes in the system.
Internal structure of the archive is defined in ISDS specification.

• New `commercialsending' command lists permissions to send commercial
messages.

• New `delete' command can be used to remove a message from long term storage
on the server.

• Delivery details listing recognizes EVENT_ENTERED_SYSTEM event.

• Manual pages are now subject of internationalization and they are translation
into Czech language too.

• `compose' command has new `-I' option to publish sender's name in the
message. Receiver can obtain the name of the sender using `sender' command.

• `compose' command has new `-C' option to specify type of composed commercial
message.

• Overwriting existing files is configurable using `overwrite_file' option.
Default is to overwrite.

• It's possible to redirect output of any command into a any shell command
connected with pipe. Use pipe (`|') operator for that. Anything after the pipe
symbol is executed as a shell command.

Version 0.1
===========

• First public release.

• We support all basic features needed by casual ISDS user (i.e. no
maintenance services from central government point of view). Some features are
handled at poor usability level (e.g. no message list paging or filtering).
Some features are incomplete (e.g. authentication with client certificate not
supported yet).
