mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-12-22 01:14:53 +01:00
5aa60342c8
https://www.ietf.org/id/draft-autocrypt-lamps-protected-headers-02.html Makes it clear that the "Legacy Display" part of an encrypted message with protected headers can (and indeed, should) be of content-type text/plain, though some clients still generate the Legacy Display part as content-type text/rfc822-headers. Notmuch should recognize the part whichever of the two content-types it uses. See also discussion in https://github.com/autocrypt/protected-headers/issues/23 for why the community of implementers is moving in the direction of text/plain. Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net> |
||
---|---|---|
.. | ||
crypto.c | ||
crypto.h | ||
error_util.c | ||
error_util.h | ||
gmime-extra.c | ||
gmime-extra.h | ||
hex-escape.c | ||
hex-escape.h | ||
Makefile | ||
Makefile.local | ||
repair.c | ||
repair.h | ||
string-util.c | ||
string-util.h | ||
talloc-extra.c | ||
talloc-extra.h | ||
unicode-util.c | ||
unicode-util.h | ||
util.c | ||
util.h | ||
xutil.c | ||
xutil.h | ||
zlib-extra.c | ||
zlib-extra.h |