Il giorno ven, 20/05/2016 alle 11.04 +0200, Milan Crha ha scritto:
> On Fri, 2016-05-20 at 10:14 +0200, Andrea Vai wrote:
> > If I click on ctrl+U then evo hangs for many minutes waiting for
> the
> > source to be shown, and finally I have to kill it (worth try to
> > undersand what happens here, too? The message is 22MB large;
> opening
> > a 5MB message waits for some time but finally succeed).
> 
>       Hi,
> the 22MB may succeed too, but after significantly longer than the
> 5MB
> message. With WebKit2, the evolution UI will be responsive, only the
> message preview will be empty.
> 
> > Content-Disposition: inline; filename=Higgs.pdf
> > Content-Type: application/pdf; x-unix-mode=0644; name="Higgs.pdf"
> > Content-Transfer-Encoding: base64
> > ...
> > Does this mean that it's not "actually an attachment"? So evo
> cannot
> > handle it? Or, is there any other way to remove it?
> 
> As far as I can tell [1], the "inline" disposition is also fine and
> considered. Could you grep for Content-Type instead, please?

Thanks for clarifications.
grep -C 3 Content-Type (obfuscated some personal data with xxxxxxxxx):


 08:55:25 +0200
Subject: Re: xxxxxxxxxxxxxxxxxxxxxxxxxxx
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_7C3C1C8C-
4EAF-498E-9DCA-DE6DEF9ED6C8"
From: xxxxxxxxxxxxx <xxxxxxxxxx...@xxxxxxxxxxxxx.xxx>
In-Reply-To: <8a1c8878-bafb-4dd3-859e-c4cc65277...@xxxx.xxx>
Date: Thu, 5 Jul 2012 08:55:26 +0200
--

--Apple-Mail=_7C3C1C8C-4EAF-498E-9DCA-DE6DEF9ED6C8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=iso-8859-1

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

--


--Apple-Mail=_7C3C1C8C-4EAF-498E-9DCA-DE6DEF9ED6C8
Content-Type: multipart/mixed; boundary="Apple-Mail=_DD437C6A-1E9D-
46CF-8671-74EB65D8BEEA"


--Apple-Mail=_DD437C6A-1E9D-46CF-8671-74EB65D8BEEA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;
"><div =
--

--Apple-Mail=_DD437C6A-1E9D-46CF-8671-74EB65D8BEEA
Content-Disposition: inline; filename=Higgs.pdf
Content-Type: application/pdf; x-unix-mode=0644; name="Higgs.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjMKJcTl8uXrp/Og0MTGCjQgMCBvYmoKPDwgL0xlbmd0aCA1IDAgUiAvRmlsdG
VyIC9G
--

--Apple-Mail=_DD437C6A-1E9D-46CF-8671-74EB65D8BEEA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;
"><div =


Thanks,
Andrea




> 
> > I would say no, as far as I can know, because I cannot see any
> "sign"
> > icon under the message body... and also in the source message I
> can
> > read the message body clearly (sorry, don't know if this is enough
> to
> > say the message it's not signed)
> 
> I'll know more with the Content-Type grep result. The signing
> doesn't
> encode the message body usually, it does the encrypt. Though it was
> only my wild guess, where I believe you are right and your message
> is
> neither signed, nor encrypted.
>       Thanks and bye,
>       Milan
> 
> [1] https://git.gnome.org/browse/evolution/tree/libemail-engine/e-ma
> il-folder-utils.c?h=gnome-3-20#n1313
> _______________________________________________
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to