Adam Sjøgren <[email protected]> writes: > I noticed that instead of including an unencrypted Subject:-header, it > is replaced by "Subject: ..." and then 'filled in' when the message is > decrypted.
Hm... I guess it would be possible to update the Summary buffer, too, but it'd be pretty awkward -- do we want to redo the threading, for instance? > I wonder if anyone has looked into adapting Gnus to do something similar? > > Or maybe just do the same extraction and 'filling in' of the Subject: > when reading an encrypted email sent from Thunderbird. > > It looks like what Thunderbird does it that it generates an > encrypted.asc which decrypts to a MIME message, which has a part that > includes the Subject:-header: > > Content-Type: multipart/mixed; boundary="80MRq3onMnRYcWyMqpzN3xR7VKumL3WsW"; > protected-headers="v1" > Subject: Dette er emnelinien > From: Test Testersen <[email protected]> > To: =?UTF-8?Q?Adam_Sj=c3=b8gren?= <[email protected]> > Message-ID: <[email protected]> > > So the display-part is perhaps easier than the sending part. We could update the headers in the Article buffer easily enough, but on the other hand -- if the user wants to respond to this in clear text, hitting `C-d' first is easy enough, and ... do we want to encourage responding to encrypted stuff in clear text? (I mean, if we just rewrite the Article buffer Subject/From/etc headers, then hitting `r' will use those, and then we might reveal... stuff...) > I also noticed that Thunderbird included an Autocrypt:-header, which > seems to include the public key of the sender - I haven't looked into > it, but it might be worth adding support for that in Gnus as well? Or > maybe it's a waste of bandwidth... What does the Autocrypt header do? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no
