569430 - Last message in folder sometimes gets messed up

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Reader UI, defect)

Description

[Hendrik Maryns]

From time to time, the last message in a folder (be it Inbox or another one) is messed up:  First, the message before it is shown as if it weren’t MIME, or something.  E.g.:

======
Beantwortung des Fragebogens habt Ihr (oder: haben wir) euch ja nochmal =

einen Haufen Arbeit eingebrockt. Das war mir vorher gar nicht klar. =

Jetzt ist fast ein zweites Protokoll daraus geworden. Danke daf=FCr!

Ich w=E4re daf=FCr, beides nicht nur an die omin=F6se KV-Gruppe zu schicken =

(mit der wir ja real nie zu tun hatten), sondern auch ans Hamburger =

B=FCro, auch zur Weitergabe an die KKG (oder sogar an die gesamte =

Buko-Liste?). Aber wahrscheinlich haben die Hamburgers beide Texte =
======

and then, the selected last message itself follows, including all headers, also without MIME parsed:

======
Herzliche Gr=FC=DFe, michael



Hendrik Maryns schrieb:
> > Hallo,
> >
> > Also anbei noch malDelivered-To: XXX
Received: by 10.142.179.20 with SMTP id b20cs4620wff;
        Wed, 26 May 2010 22:48:31 -0700 (PDT)
Received: by 10.87.50.6 with SMTP id c6mr13888210fgk.41.1274939309062;
        Wed, 26 May 2010 22:48:29 -0700 (PDT)
Return-Path: <XXX
Received: from ilpostino.jpberlin.de (ilpostino.jpberlin.de [213.203.238.6])
        by mx.google.com with ESMTP id 3si8356442fge.10.2010.05.26.22.48.27;
        Wed, 26 May 2010 22:48:29 -0700 (PDT)
Received-SPF: pass (google.com: domain of XXX designates 213.203.238.6 as permitted sender) client-ip=213.203.238.6;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of XXX designates 213.203.238.6 as permitted sender) smtp.mail=XXX
Received: from ilpostino.jpberlin.de (localhost [127.0.0.1])
	by ilpostino.jpberlin.de (Postfix) with ESMTP id 0243835881A;
	Thu, 27 May 2010 07:48:35 +0200 (CEST)
X-Original-To: XXX
Delivered-To: XXX
Received: from mx2.heinlein-support.de (mx2.heinlein-support.de
	[91.198.250.20])
	by ilpostino.jpberlin.de (Postfix) with ESMTP id 782A9358816
	for <XXX
	Thu, 27 May 2010 07:48:33 +0200 (CEST)
Received: from kristall.heinlein-support.de (kristall.heinlein-support.de
	[91.198.250.42])
	by mx2.heinlein-support.de (Postfix) with ESMTP id E21DD2FE85
	for <XXX
	Thu, 27 May 2010 07:48:25 +0200 (CEST)
X-Virus-Scanned: amavisd-new at heinlein-support.de
Received: from mx2.heinlein-support.de ([91.198.250.20])
	by kristall.heinlein-support.de (kristall.heinlein-support.de
	[213.203.238.118]) (amavisd-new, port 10024)
	with ESMTP id ol8Kf32ZAq+E for <XXX
	Thu, 27 May 2010 07:48:23 +0200 (CEST)
X-policyd-weight: DYN_NJABL=SKIP(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5
	NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5 DSBL_ORG=ERR(0)
	CL_IP_EQ_HELO_IP=-2 (check from: .aol. - helo: .omr-m33.mx.aol.
	- helo-domain: .aol.) FROM/MX_MATCHES_HELO(DOMAIN)=-2
	IN_PM_RFCI=0.1; rate: -8.4
Received: from omr-m33.mx.aol.com (omr-m33.mx.aol.com [64.12.143.145])
	by mx2.heinlein-support.de (Postfix) with ESMTP
	for <XXX
	Thu, 27 May 2010 07:48:05 +0200 (CEST)
Received: from imo-da04.mx.aol.com (imo-da04.mx.aol.com [205.188.169.202])
	by omr-m33.mx.aol.com (8.14.1/8.14.1) with ESMTP id o4R5m08W025792
	for <XXX; Thu, 27 May 2010 01:48:00 -0400
Received: from XXX
	by imo-da04.mx.aol.com  (mail_out_v42.9.) id u.ce8.7510a25a (43915)
	for <XXX
	Thu, 27 May 2010 01:47:55 -0400 (EDT)
Received: from magic-d18.mail.aol.com (magic-d18.mail.aol.com
	[172.19.155.134]) by cia-dc08.mx.aol.com (v129.4) with ESMTP id
	MAILCIADC084-ab8b4bfe078a1c9; Thu, 27 May 2010 01:47:54 -0400
From: XXX
Message-ID: <[e-mail]>
Date: Thu, 27 May 2010 01:47:54 EDT
To: XXX
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="part1_9290b.90db433.392f618a_boundary"
X-Mailer: AOL 9.0 VR sub 5200
X-AOL-ORIG-IP: 78.52.35.182
X-AOL-IP: 172.19.155.134
X-AOL-SENDER: XXX
Subject: [XXX] Fwd: kleiner Fragebogen zur Vorbereitung des XXX
X-BeenThere: XXX
X-Mailman-Version: 2.1.11
Precedence: list
Reply-To: XXX
List-Id: <XXX
List-Unsubscribe: <XXX
	<mailto:XXX
List-Post: <mailto:XXX
List-Help: <mailto:XXX
List-Subscribe: <XXX
	<mailto:XXX
Sender: XXX
Errors-To: XXX


--part1_9290b.90db433.392f618a_boundary
Content-Type: multipart/related;
	boundary="part1_9290b.90db433.392f618a_rel_boundary"



--part1_9290b.90db433.392f618a_rel_boundary
Content-Type: multipart/alternative; boundary="9290b.90db433_alt_bound"



--9290b.90db433_alt_bound
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en


=20
=20
=20
Hallo rundrum
=20
ein Teil der T=C3=BCbinger-Vorbereitungsgruppe haben diesen Brief der KV=
 schon =20
bekommen, =C3=BCber die Liste (von der die KV offenbar nichts wei=C3=9F :-=
) sollten es=20
nun  alle haben.
Mein Vorsc

=====

Note that the first message is abruptly broken off.
The problem is not solved by rearranging the order of the messages in the folder (e.g. by sorting on another attribute).  Nor by a simple restart.  It is solved, e.g. if I start TB from another machine.  And then some time later it happens to another message.
I seem to recall this problem popped up with 3.0, but has carried through all updates until now.

Comment 1

[Hendrik Maryns]

Now, one day later, after a system restart, the message is displayed fine.

Comment 2

[Hendrik Maryns]

Today, a variant occurred: the last message itself was rendered correctly first, then, without anything in between, the message before it (which I just deleted) showed up, including all headers and un-MIMEd.

Comment 3

[Ludovic Hirlimann [:Usul]]

Can you compact and rebuild the index of your folder showing the issue ?

Comment 4

[Hendrik Maryns]

(In reply to comment #3)
> Can you compact and rebuild the index of your folder showing the issue ?

I did Properties → repair folder, everything blanked out for a while, when the message popped up again, it was still shown incorrectly.

Compacting the folder seems to have solved the problem (I went to another folder in the meantime).