On 9/14/2016 11:35 PM, Onno Ekker wrote:
> On Thu, Sep 15, 2016 at 8:28 AM, Patrick Brunschwig
> <[email protected] <mailto:[email protected]>> wrote:
> 
> 
>     OK, NoOp sent me the message (which was actually a public newsgroup
>     message). The message structure is completely wrong (broken). According
>     to the content-type, it's a PGP/MIME signed message with a single plain
>     text body. However, at some point the message ends. There is no marker
>     for the end of the body text MIME part, nor is there any signature part.
> 
>     I agree, Enigmail should do better than displaying nothing, but it's
>     certainly not related to any interference with S/MIME messages. Enigmail
>     is just not prepared to handle such message gracefully.
> 
>     -Patrick
> 
> 
> Did you double-check with NoOp that he sent you the complete message? :-)
> Onno

The attached EML that I sent is complete. I also put a copy of the
message text in the email body, so yes, it was complete. It's a public
newsgroup message that you can check on the
comp.handhelds.android.k9mail newsgroup. For gmane (which I use):
Xref: news.gmane.org gmane.comp.handhelds.android.k9mail:4896

Given that it's public, here is a pastebin copy w/headers:
http://pastebin.ubuntu.com/23183265/

As Patrick points out, there is no signature part. Here is a more recent
post by the same user that is complete and is displayed properly with
Enigmail 1.9.5 installed:

http://pastebin.ubuntu.com/23183315/
Xref: news.gmane.org gmane.comp.handhelds.android.k9mail:5238

1.8.x displays the 4896 message, 1.9.x does not.

@Patrick: Thanks for reviewing. I'm not sure what the answer is, but
perhaps if Enigmail 1.9.x does not find a proper signature or other
tags/markers etc., it should take the 1.8.x approach and let the message
display?


_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to