[neomutt-devel] [PATCH] send.c: Allow crypto operations in batch and mailx modes.

Alejandro Colomar alx at kernel.org
Wed Nov 15 19:10:52 CET 2023


Hi Werner!

On Wed, Nov 15, 2023 at 04:13:14PM +0100, Werner Koch wrote:
> Hi!
> 
> On Fri, 10 Nov 2023 01:41, Alejandro Colomar said:
> 
> > This is breaking behavior, so it needs some more justification than just
> > the above.
> 
> FWIW, I am using another patch for 2 years now to send unattended but
> signed mails.  The patch requires a new option to avoid the risk of
> regressions.  See
> 
>   https://lists.mutt.org/pipermail/mutt-dev/Week-of-Mon-20220725/thread.html
> 
> and Kevin's follow-up.  Unfortunately I had not have the time to
> continue working on the patch to get this or something else upstream.

Hmm.  Interesting.  I think I prefer not adding an option.  It's
breaking behavior, but at least it keeps it simple: you enable crypto in
the config, you get crypto.  It keeps mutt(1) being interactive as
necessary: it will ask for the password as necessary, then do everything
else.  It is the user's responsibility to either not enable crypto in
the config, or do something to keep the keyring unlocked.

Your patch also serves me as an indicator that this patch touches the
right place in the code base.

I wonder if Kevin will accept patches with new features...

Thanks!
Alex

> 
> 
> Shalom-Salam,
> 
>    Werner
> 
> -- 
> The pioneers of a warless world are the youth that
> refuse military service.             - A. Einstein



-- 
<https://www.alejandro-colomar.es/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://mailman.neomutt.org/pipermail/neomutt-devel-neomutt.org/attachments/20231115/6fd18b9b/attachment.sig>


More information about the neomutt-devel mailing list