From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id D268E6DE01EC for ; Tue, 9 Jan 2018 11:27:13 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OuWkpeVjTtsf for ; Tue, 9 Jan 2018 11:27:12 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id A0C006DE01EB for ; Tue, 9 Jan 2018 11:27:12 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1eYzYD-0002I1-85 for notmuch@notmuchmail.org; Tue, 09 Jan 2018 14:27:09 -0500 Received: (nullmailer pid 28510 invoked by uid 1000); Tue, 09 Jan 2018 19:27:08 -0000 From: David Bremner To: notmuch@notmuchmail.org Subject: notmuch release 0.26 now available X-List-To: notmuch Date: Tue, 09 Jan 2018 15:26:59 -0400 Message-ID: <87bmi2kf3w.fsf@tethera.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.24 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2018 19:27:14 -0000 --=-=-= Content-Type: text/plain Where to obtain notmuch 0.26 =========================== https://notmuchmail.org/releases/notmuch-0.26.tar.gz Which can be verified with: https://notmuchmail.org/releases/notmuch-0.26.tar.gz.sha256 d3e894ed2ad9d721a442663f07a6f2a241dc98be7cc4af681f16edf88e0d76df notmuch-0.26.tar.gz https://notmuchmail.org/releases/notmuch-0.26.tar.gz.sha256.asc (signed by David Bremner) What's new in notmuch 0.26 ========================= Command Line Interface ---------------------- Support for re-indexing existing messages There is a new subcommand, `notmuch reindex`, which re-indexes all messages matching supplied search terms. This permits users to change the way specific messages are indexed. Note that for messages with multiple variants in the message archive, the recorded Subject: of may change upon reindexing, depending on the order in which the variants are indexed. Improved error reporting in notmuch new Give more details when reporting certain Xapian exceptions. Support maildir synced tags in `new.tags` Tags `draft`, `flagged`, `passed`, and `replied` are now supported in `new.tags`. The tag `unread` is still special in the presence of maildir syncing, and will be added for files in `new/` regardless of the setting of `new.tags`. Support /regex/ in new.ignore Files and directories may be ignored based on regular expressions. Allow `notmuch insert --folder=""` This inserts into the top level folder. Strip trailing '/' from folder path for notmuch insert This prevents a potential problem with duplicated database records. New option --output=address for notmuch address Make `notmuch show` more robust against deleting duplicate files The option --decrypt now takes an explicit argument The --decrypt option to `notmuch show` and `notmuch reply` now takes an explicit argument. If you were used to invoking `notmuch show --decrypt`, you should switch to `notmuch show --decrypt=true`. Boolean and keyword arguments now take a `--no-` prefix Encrypted Mail -------------- Indexing cleartext of encrypted e-mails It's now possible to include the cleartext of encrypted e-mails in the notmuch index. This makes it possible to search your encrypted e-mails with the same ease as searching cleartext. This can be done on a per-message basis by passing --decrypt=true to indexing commands (new, insert, reindex), or by default by running "notmuch config set index.decrypt true". Encrypted messages whose cleartext is indexed will typically also have their session keys stashed as properties associated with the message. Stashed session keys permit rapid rendering of long encrypted threads, and disposal of expired encryption-capable keys. If for some reason you want cleartext indexing without stashed session keys, use --decrypt=nostash for your indexing commands (or run "notmuch config set index.decrypt nostash"). See `index.decrypt` in notmuch-config(1) for more details. Note that stashed session keys permit reconstruction of the cleartext of the encrypted message itself, and the contents of the index are roughly equivalent to the cleartext as well. DO NOT USE this feature without considering the security of your index. Emacs ----- Guard against concurrent searches in notmuch-tree Use make-process when available This allows newer Emacs to separate stdout and stderr from the notmuch command without using temporary files. Library Changes --------------- Indexing files with duplicate message-id Files with duplicate message-id's are now indexed, and searchable via terms and phrases. There are known issues related to presentation of results and regular-expression search, but in principle no mail file should be completely unsearchable now. New functions to count files Two new functions in the libnotmuch API: `notmuch_message_count_files`, and `notmuch_thread_get_total_files`. New function to remove properties A new function was added to the libnotmuch API to make it easier to drop all properties with a common pattern: `notmuch_message_remove_all_properties_with_prefix` Change of return value of `notmuch_thread_get_authors` In certain corner cases, `notmuch_thread_get_authors` previously returned NULL. This has been replaced by an empty string, since the possibility of NULL was not documented. Transition `notmuch_database_add_message` to `notmuch_database_index_file` When indexing an e-mail message, the new `notmuch_database_index_file` function is the preferred form, and the old `notmuch_database_add_message` is deprecated. The new form allows passing a set of options to the indexing engine, which the operator may decide to change from message to message. Test Suite ---------- Out-of-tree builds The test suite now works properly with out-of-tree builds, i.e. with separate source and build directories. The --root option to tests has been dropped. The same can now be achieved more reliably using out-of-tree builds. Python Bindings --------------- Python bindings specific Debian packaging is removed The bindings have been build by the top level Debian packaging for a long time, and `bindings/python/debian` has bit-rotted. Open mail files in binary mode when using Python 3 This avoids certain encoding related crashes under Python 3. Add python bindings for `notmuch_database_{get,set}_config*` Optional `decrypt_policy` flag is available for notmuch.database().index_file() nmbug ----- nmbug's internal version increases to 0.3 in this notmuch release. User-facing changes with this notmuch release: * Accept failures to unset `core.worktree` in `clone`, which allows nmbug to be used with Git 2.11.0 and later. * Auto-checkout in `clone` if it wouldn't clobber existing content, which makes the initial clone more convenient. * Only error for invalid diff lines in `tags/`, which allows for `README`s and similar in nmbug repositories. Documentation ------------- New man page: notmuch-properties(7) This new page to the manual describes common conventions for how properties are used by libnotmuch, the CLI, and associated programs. External projects that use properties are encouraged to claim their properties and conventions here to avoid collisions. What is notmuch =============== Notmuch is a system for indexing, searching, reading, and tagging large collections of email messages in maildir or mh format. It uses the Xapian library to provide fast, full-text search with a convenient search syntax. For more about notmuch, see https://notmuchmail.org make[1]: Leaving directory '/home/bremner/software/upstream/notmuch' --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlpVF4MACgkQ8gKXHaSn nixfJwv9G13vohPU55QycABk5tZaSn2V+zq4Ksgk3/zrVDxW3B8Lkyza7uNt5dV3 Kf5EbXciluzo3Zxb9y2jEHo4caB1lzAXOgGR6jem0H6b6MYh5DDi7ZTGA/iIBH/d S9pJY6J4O/BbUBGnycn80AezU5GHG8lCUKlNLsBl9zdBEzfOZQQnlQtIV8xtRq1y eexuzdsUoaodLQ9VTmVllOu1nUpAAVOSQ3OQZXSM/OXTQZCeza+fdbgM+qRtURHF Jz7KG9tfgxV4WcaqukH53D27jSO39wZw7V/Fl+MXRRsebI34lAjCJkvOC2AQLZL8 2OXwwKPccLBj0q9rq/2920zgy4ObRF5ar8Dstik4Dw0eVNSJVWB+oXq2XfoOcmCU qwNzunc++Pgg5GLYLUGoLKe+YcG6P7EjcS+oLWfwyN2ZIOEy4Z9eADcaLygIRA6n Ckais47H+bHt2LczbkH/RFlPAB050ME9Ngc7WrF94Q0x1q41XAkHvM0PgCVWfPDe uaODcuCG =+GcP -----END PGP SIGNATURE----- --=-=-=--