Tomi Ollila writes:
> On Sun, Dec 26 2021, David Bremner wrote:
>
>> From: Jani Nikula
>>
>> In [1] Mark Walters reported a problem with messages being removed
>> from the database when the parent directory was renamed. Jani Nikula
>> proposed [2] these tests but observed
>
> With that 'From:' l
This particular bug is apparently caused by the malformed (according
to RFC5822 section 3.6.4) In-reply-to field of
id:5422.1299798...@alphaville.usa.hp.com.
---
test/T265-thread-fusing.sh| 21
.../cur/1397885606.000217.mbox:2,S| 67 +++
.../cur/13978
On Sun, Dec 26 2021, David Bremner wrote:
> From: Jani Nikula
>
> In [1] Mark Walters reported a problem with messages being removed
> from the database when the parent directory was renamed. Jani Nikula
> proposed [2] these tests but observed
With that 'From:' line commit message starts to look
Daniel Kahn Gillmor writes:
> After some discussion with amdragon on IRC, i believe that this is only
> relevant to notmuch when actively decrypting a message -- OpenPGP's
> ability to embed compression makes it possible to write a PGP/MIME
> message that is a quine: that is, when decompressed,
Austin Clements writes:
> Quoth Ramakrishnan Muthukrishnan on Aug 05 at 11:35 pm:
>> Ramakrishnan Muthukrishnan writes:
>>
>> > Hi,
>> >
>> > Pardon me for using non-standard terms here because of lack of knowledge
>> > of the language used in the email world.
>> >
>> > I have this thread in wh
Since the bug was first reported in [1], notmuch has gained the
ability to have the database located outside the mail root, hence this
this change differs slightly from Jani's proposed solution [2] in not
using notmuch_database_get_path, but rather the already retrieved
mail_root.
[1]: id:87mwhifu
In [1] Rob observed that notmuch new ignored directories called
.notmuch everywhere in the tree, where they should only (and now, with
split configs, at most) be ignored at the top level. Add a test to
demonstrate the problem.
[1]: id:87mwhifu9a@trouble.defaultvalue.org
---
test/T050-new.sh |
David Bremner writes:
>
> i.e. #secure method=pgpmime mode=signinvalidencrypt will end up
> sending an encrypted message (with the <>, of course).
>
> It seems like it should error out if the mode= is set to an invalid or
> unknown value, rather than sending mail in the clear.
>
> I've got this se
From: Jani Nikula
In [1] Mark Walters reported a problem with messages being removed
from the database when the parent directory was renamed. Jani Nikula
proposed [2] these tests but observed
This test is not suitable for merging since it's not deterministic.
After applying Jani's patch [3],
