Daniel Kahn Gillmor writes:
> --- a/devel/schemata
> +++ b/devel/schemata
> @@ -89,9 +89,15 @@ crypto = {
>status: sigstatus,
># was the set of signatures described under encrypted
> cover?
>encrypted: bool,
> +
On Fri 2018-06-15 07:16:05 -0300, David Bremner wrote:
> Daniel Kahn Gillmor writes:
>
>> +notmuch_status_t
>> +_notmuch_message_crypto_set_sig_list (_notmuch_message_crypto_t
>> *msg_crypto, GMimeSignatureList *sigs)
>> +{
>
> It's a bit confusing that nothing in this API/patch seems to use the
Daniel Kahn Gillmor writes:
>
> sp->map_key (sp, "Subject");
> -sp->string (sp, g_mime_message_get_subject (message));
> +if (msg_crypto && msg_crypto->payload_subject) {
> + sp->string (sp, msg_crypto->payload_subject);
> +} else
> + sp->string (sp,
Hi David,
David Bremner wrote:
"Naveen N. Rao" writes:
In my case, I seem to be having the In-Reply-To headers. I end up with
two files per message: one from my inbox and one from the gmane archive
that I pull in. All the messages from the gmane archive seem to have a
re-written
