GNOME Bugzilla – Bug 731604
Recursive inline-PGP-signed text not shown properly
Last modified: 2014-06-18 14:56:50 UTC
Created attachment 278387 [details] mbox of email with display problem Hi All, I have run into an interesting problem while displaying certain types of emails I receive on a regular basis. I'm hoping that someone here can help me out. OS: Ubuntu 14.04 LTS (all latest updates) Evolution version 3.10.4 (latest available though ubuntu repositories) Attachments: 1) Mbox of email giving me trouble. This is just one example. There are many emails likes this. 2) Screenshot of how that email is displayed for me in Evolution. As can be seen in the screenshot, the outer PGP signature from AusCERT is validated and results displayed at the bottom of the email as expected "Valid signature, but cannot verify sender". That's great. No problems here. However, the AusCERT email is wrapped around a Debian bulletin which itself is PGP signed. In the screenshot you can see that the area between "BEGIN INCLUDED TEXT" and "END INCLUDED TEXT" has just been swallowed by Evolution! If you look at the mbox attachment, you'll see that's where the Debian bulletin is. Evolution doesn't seem to be able to display it. Of course, I can always see the raw text by going "View -> Message Source (Ctrl + U)" but that is not ideal at all. Ideally, I'd like to see both signatures validated independently and results of both displayed. ---------- I also had another question. Is there any way to move "Valid signature" bar from the bottom of the message to the top of the message near the "From" and "To" fields. I don't want to have to scroll to the bottom of the message to see if the signature check passed or not. I'd like to be alerted! Any help with either of those would be much appreciated. Regards, Parth
Created attachment 278388 [details] screenshot of problematic email as displayed by evolution
Confirming, I also do not see the text between "BEGIN INCLUDED TEXT" and "END INCLUDED TEXT" marks, just the same as in your screenshot. I see it with git master, to be 3.13.3 soon.
I figured out that I disabled recursion in time of 3.7.4. I definitely had some reason for it, but when I re-enabled the recursion then I was not able to reproduce any issue with my test messages, thus I'm enabling recursion again. Created commit 2cd604b in evo master (3.13.3+) [1] Created commit 73641c4 in evo evolution-3-12 (3.12.4+) https://git.gnome.org/browse/evolution/commit/?id=2cd604b