7>?tQ$'oOPRwc:6^PIs@G>M\NsrD]1Y3CGhb75ufqxfv%)?*o5t>Ze0JnD1MAn:^J2S#%A6}-<g
D)p
ASoe~3Z-alsyiL6HLe=9(~m~Vt)R!]g8v2z~%[=/tQ)"Oa4L~)Vs-Qhl!Hl'5]U(^drhalzxvGK
&fV
;#|HWL61c0uiiLzC|Q^dCO+fij?V{%#.`7Kd#y0%3cvbh[EbA'k6XNpQ?iYpoi
References: <nran58$lik$2...@blaine.gmane.org>
<pan$70295$3b2cc59f$67a6e305$ceb8e...@cox.net>
<nrbue3$19t$2...@blaine.gmane.org>
X-No-Archive: yes
User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT b8fc14e
git.gnome.org/git/pan2)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
On Wed, 14 Sep 2016 16:38:27 +0000 Dave wrote:
> On Wed, 14 Sep 2016 14:57:02 +0000, Duncan wrote:
>
>> Based on previous bugs (one of which I experienced in pan and reported
>> to upstream gmime myself, after some help debugging it right on this
>> list, a couple years ago), I'd guess there's a relatively high chance
>> it's a libgmime bug, however, not a pan bug directly. What version of
>> gmime did you build against?
>
> Looks an X-Face header where the corruption in occurring. The actual X-
> Face header looks a bit short and the garbage at the start of the body
> before the References header (which is displayed as part of the body)
> also looks like X-Face data.
>
> I'd suggest re-creating the X-Face data, possibly make a slight edit to
> the image file first to create a different encoding stream.
Here we go...
--
Regards,
hiker
_______________________________________________
Pan-users mailing list
Pan-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/pan-users
