<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T070-insert.sh, branch 0.36_rc0</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.36_rc0</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.36_rc0'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2022-02-20T02:11:35Z</updated>
<entry>
<title>CLI/insert: escape envelope from</title>
<updated>2022-02-20T02:11:35Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-02-12T02:47:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b320d3fb59d80b071459a0b2f28c4340ac687327'/>
<id>urn:sha1:b320d3fb59d80b071459a0b2f28c4340ac687327</id>
<content type='text'>
The idea is to do as little parsing and modification of the delivered
message as possible. Luckily the position of the "envelope header"
lets us escape it by replacing the first 5 characters of the stream
with a regular header name (with ':').
</content>
</entry>
<entry>
<title>test: add known broken test for insert with mbox as input</title>
<updated>2022-02-20T00:15:10Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-02-12T02:10:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4a380371e7f6d907823df66bee07fa569f379875'/>
<id>urn:sha1:4a380371e7f6d907823df66bee07fa569f379875</id>
<content type='text'>
It seems reasonable that notmuch should try to avoid delivering
messages in formats it cannot index.
</content>
</entry>
<entry>
<title>config: ignore leading/trailing spaces in ';'-delimited lists</title>
<updated>2021-12-04T16:16:12Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-09-30T17:17:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bab633d3ac87167dc214094f9d340655885a01b1'/>
<id>urn:sha1:bab633d3ac87167dc214094f9d340655885a01b1</id>
<content type='text'>
In [1] Ciprian observed that it was easy for users to mistakenly
introduce leading and trailing space to new.tags when editing a
notmuch config file. This commit strips spaces on either side of the
';' delimiter when splitting.

In principle it would be possible to support tags (or other config
values) with leading or trailing spaces by processing '\s' escapes in
the input string. Currently such processing is not done.

[1]: id:CA+Tk8fzjPLaEd3vL1f9ebk_bF_RV8PDTLzDupraTkCLCpJAmCg@mail.gmail.com
</content>
</entry>
<entry>
<title>test: known broken tests for leading/trailing ws in config</title>
<updated>2021-12-04T16:15:49Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-09-30T17:17:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e22bbb124e4f9191880e80d6517346f35bf7e2a9'/>
<id>urn:sha1:e22bbb124e4f9191880e80d6517346f35bf7e2a9</id>
<content type='text'>
These tests duplicate the bug/misfeature reported in

      id:CA+Tk8fzjPLaEd3vL1f9ebk_bF_RV8PDTLzDupraTkCLCpJAmCg@mail.gmail.com
</content>
</entry>
<entry>
<title>test: trivial style cleanups</title>
<updated>2021-05-17T10:27:52Z</updated>
<author>
<name>Felipe Contreras</name>
<email>felipe.contreras@gmail.com</email>
</author>
<published>2021-05-15T20:47:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=645bea13cb204108fd520010afbba25d0d6a8693'/>
<id>urn:sha1:645bea13cb204108fd520010afbba25d0d6a8693</id>
<content type='text'>
Signed-off-by: Felipe Contreras &lt;felipe.contreras@gmail.com&gt;
</content>
</entry>
<entry>
<title>test: clean up some extra whitespace.</title>
<updated>2021-03-12T11:19:14Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-01-16T01:29:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=97fadd0645e908ff8322577a983dc710bfda33d6'/>
<id>urn:sha1:97fadd0645e908ff8322577a983dc710bfda33d6</id>
<content type='text'>
The extra space is mainly just untidy.
</content>
</entry>
<entry>
<title>CLI/insert: convert to new config framework.</title>
<updated>2021-02-06T23:17:34Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-08-26T11:43:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f994f0e7df178eb31c656329bb28ffa832ac4364'/>
<id>urn:sha1:f994f0e7df178eb31c656329bb28ffa832ac4364</id>
<content type='text'>
The new talloc context is needed to run the hook at the very end of
the function. That in turn is needed so that this process gives up the
write lock on the database.
</content>
</entry>
<entry>
<title>test: fix syntax errors in erroring calls to notmuch insert</title>
<updated>2020-09-05T00:04:33Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-09-04T01:10:57Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=85b580386905ca1fdb168edc64fca66ffb9620a7'/>
<id>urn:sha1:85b580386905ca1fdb168edc64fca66ffb9620a7</id>
<content type='text'>
notmuch insert does not currently support passing a filename for the
input, so all of these tests have an extra error in addition to the
one being tested for.

Currently this does not make a difference because the error being
tested for is caught before the error of an extra command line
argument. In the future it might make a difference, and in any case it
is confusing.
</content>
</entry>
<entry>
<title>test: replace use of gdb with LD_PRELOAD shims in T070-insert.sh</title>
<updated>2019-06-29T19:11:08Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-26T16:23:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1959a95d2538daa2a802b74699ecb2b42d997a2d'/>
<id>urn:sha1:1959a95d2538daa2a802b74699ecb2b42d997a2d</id>
<content type='text'>
This removes the dependency of this test script on gdb, and
considerably speeds up the running of the tests.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>cli/show: emit new whole-message crypto status output</title>
<updated>2019-05-26T11:20:23Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-25T18:04:06Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4cb789aa090fb6ba3c7897584ecbcc0a547b2f81'/>
<id>urn:sha1:4cb789aa090fb6ba3c7897584ecbcc0a547b2f81</id>
<content type='text'>
This allows MUAs that don't want to think about per-mime-part
cryptographic status to have a simple high-level overview of the
message's cryptographic state.

Sensibly structured encrypted and/or signed messages will work fine
with this.  The only requirement for the simplest encryption + signing
is that the message have all of its encryption and signing protection
(the "cryptographic envelope") in a contiguous set of MIME layers at
the very outside of the message itself.

This is because messages with some subparts signed or encrypted, but
with other subparts with no cryptographic protection is very difficult
to reason about, and even harder for the user to make sense of or work
with.

For further characterization of the Cryptographic Envelope and some of
the usability tradeoffs, see here:

   https://dkg.fifthhorseman.net/blog/e-mail-cryptography.html#cryptographic-envelope
</content>
</entry>
</feed>
