Re: Autocrypt support

2019-04-11 Thread Ralph Seichter
* Daniel Kahn Gillmor:

> [...] if you'd like to help me strategize about next steps for getting
> autocrypt support into notmuch itself, i'd welcome the collaboration.

I'd be willing to help if you think I can actually be of use to you. ;-)
I have, as of today, not even looked at the Notmuch architecture and
source code. I do know a reasonable amount about GnuPG, RFC 5322 et al,
though.

-Ralph
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: Autocrypt support

2019-04-11 Thread Daniel Kahn Gillmor
On Thu 2019-04-11 16:01:43 +0200, Ralph Seichter wrote:
> I'm not quite sure if this is a question of Notmuch's Emacs client or of
> Emacs in general, but I am trying to find information on Autocrypt
> support (see https://autocrypt.org/).
>
> The Enigmail addon for Thunderbird supports Autocrypt, and I wondered
> if/how Notmuch might be persuaded to support it as well?

yes, i want notmuch to support autocrypt, and it's been on my to-do list
for many months now.  :(

I would love to have some help on that, because i've been a bit blocked,
still trying to wrap up my protected headers series.

But if you'd like to help me strategize about next steps for getting
autocrypt support into notmuch itself, i'd welcome the collaboration.

  --dkg


signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Autocrypt support

2019-04-11 Thread Ralph Seichter
I'm not quite sure if this is a question of Notmuch's Emacs client or of
Emacs in general, but I am trying to find information on Autocrypt
support (see https://autocrypt.org/).

The Enigmail addon for Thunderbird supports Autocrypt, and I wondered
if/how Notmuch might be persuaded to support it as well?

-Ralph
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: [PATCH v3 4/4] test: add test for checking forwarded messages

2019-04-11 Thread Örjan Ekeberg
Tomi Ollila  writes:
>
> good stuff -- comments inline

Yes, the test suite in general could benefit from more comments, since
there are quite a lot of "smart things" going on.

>> +test_emacs_expect_t "
>> +   (progn
>> +(notmuch-show \"id:$message_id\")
>> +(notmuch-show-forward-message)
>> +(run-hooks 'notmuch-mua-send-hook)
>
> Would instead (run-hooks...) in the above, embedding:
>
> (let ((message-send-mail-function (lambda () t))
>   (mail-host-address \"example.com\"))
> and
>  (notmuch-mua-send)
>
> work (that is what we do in emacs_fcc_message () in test-lib.sh
>
> ?

I agree that it is more straightforward to call notmuch-mua-send than to
only call the send hooks.  Thanks for your tip on how to make this work.
In addition to your suggestion, I had to remove the automatically added
Fcc-header and add a proper To-address for the send machinery to accept
the message.  This seems to work:

test_emacs_expect_t "
  (let ((message-send-mail-function (lambda () t)))
(notmuch-show \"id:$message_id\")
(notmuch-show-forward-message)
(save-restriction
  (message-narrow-to-headers)
  (message-remove-header \"Fcc\")
  (message-remove-header \"To\")
  (message-add-header \"To: nob...@example.com\"))

(notmuch-mua-send)
(notmuch-test-expect-equal
(message-field-value \"References\") \"<$message_id>\"))
"

>> +(notmuch-test-expect-equal (message-field-value \"References\")
>> +   \"<$message_id>\"))"
>
> You probably had tabs and spaces "correct" last time, but I got confused by
> the extra line and forgot to drop indentation to see better. To be
> consistent with other rests these lines do need to have tabs (width 8) and
> rest spaces

Ok.


>> +test_begin_subtest "Forwarding adding the forwarded tag"
>> +# Check that the send hook called in the previous subtest did add the 
>> forwarded-tag
>> +
>> +test_expect_equal $(notmuch search --output=messages tag:forwarded) 
>> id:$message_id
>
> I'd still do something like:
>
>  test_expect_equal "$(notmuch search --output=tags id:$message_id)" \
>   $'forwarded\ninbox\nunread\n' 
>
> (note: quoting aroung first arg and $'dollar-single' in second, but did not
> test that this is what exactly works (newlines could be clearer, though) :)
>
> ... to ensure (and show visibility) that just "forwarded" were added. if
> anyone(tm) ever changes system so that default tags change, many other
> tests also need updating...

Fair enough.  I agree that it is more logical to analyse the tags of the
specific message, than to first search for the tag itself.

One worry though.  Your suggested code depends on that the order in
which "notmuch search" lists the tags is stable.  Since the tags is a
set, it seems fragile to rely on the order of the individual tags.  What
about this variant?  I have tried it and it seems to work.

test_expect_equal "$(notmuch search --output=tags id:$message_id | sort)" \
"forwarded
inbox
unread"

/Örjan
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: [PATCH 2/2] release: use xz compression

2019-04-11 Thread David Bremner
Tomi Ollila  writes:

>
> Something related: any wisdom here:
>
> https://www.nongnu.org/lzip/xz_inadequate.html
>

I guess for me it lacks some kind of "peer review". As the author notes,
he has his own biases being the creator/author of a competing solution.
I'm not aware of any more "arms length" discussion of the issues
involved.

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch