Alejandro Colomar

> Can we change the behaviour to mimic `gpg --hidden-recipient` for the `bcc:` field? It seems we can. I'll need to learn more about how we encrypt, and how gpgme...

I'll prepare a patch next week. :)

I've been looking at the code, and it needs some non-trivial work, compared to the other patch sets I have pending. I'll queue this after the other crypto patches. I...

> > Can we change the behaviour to mimic `gpg --hidden-recipient` for the `bcc:` field? > > It seems we can. I'll need to learn more about how we encrypt,...

> > He suggested sending separate mails to each BCC > > Yeah, I mentioned the same idea in #4251 / `*07` Hide Bcc. > > For plain emails, it'd...

> Please can you [open a discussion](https://github.com/neomutt/neomutt/discussions/categories/development) and sketch out your perfect goal for **all** of the upgrades. Hmm, I'll try. > Code is great and each PR is small,...

v1b (by @flatcap ) changes: - Rebase to devel/security ``` $ git range-diff devel/security..78e1bcf38 a5a4540^^^^^^..a5a4540 1: 621911ae0 = 1: 094f2248d ncrypt/crypt.c: Refactor (split) conditional 2: d252c7ecc = 2: e4ca27ba7 ncrypt/crypt.c:...

v1c changes: - Rebase to devel/security ``` $ git range-diff a5a4540^^^^^^..a5a4540 neomutt/devel/security..cryptoweed 1: 094f2248d < -: --------- ncrypt/crypt.c: Refactor (split) conditional 2: e4ca27ba7 < -: --------- ncrypt/crypt.c: Invert logic to...

v1d changes: - Rebase ``` $ git range-diff devel/security..gh/cryptoweed neomutt/devel/security..cryptoweed 1: ed1fc0002 = 1: 055d4429e $crypt_protected_headers_weed: Add variable ```

This is ready by my side. Feel free to merge when you're happy with it, @flatcap .