![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
After threading e-mails just fine for 1 year, thunderbird will randomly misthread a few messages
I have verified that "right click the folder, select properties and then repair. Just in case that helps." does fix this issue. However with 97,169 messages in the folder it takes a long time.
This is the third time I have repaired the same folder. Without any crashes.
The latest misthread that I noticed (usally I just ignore these).
Top of the thread:
Received: from fldsmtpi02.verizon.com (166.68.71.144) by
MIA20725CAS891.apps.tmrk.corp (10.1.3.223) with Microsoft SMTP Server id 14.2.318.1; Mon, 5 May 2014 14:03:13 -0400
X-VzAPP: 1 X-IronPort-AV: E=Sophos;i="4.97,990,1389744000";
d="scan'208";a="713637337"
X-Local: true Received: from unknown (HELO don-760.CloudSwitch.com) ([162.47.5.40]) by
fldsmtpi02.verizon.com with ESMTP; 05 May 2014 18:03:12 +0000
From: Don Slutz <dslutz@verizon.com> To: <qemu-devel@nongnu.org> CC: =?UTF-8?q?Andreas=20F=C3=A4rber?= <afaerber@suse.de>, "Michael S. Tsirkin" <mst@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Don Slutz <dslutz@verizon.com> Subject: [PATCH v4 0/2] qdev: Display warning about unused -global Date: Mon, 5 May 2014 14:03:05 -0400 Message-ID: <1399312987-29499-1-git-send-email-dslutz@verizon.com> X-Mailer: git-send-email 1.8.4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Return-Path: dslutz@verizon.com X-MS-Exchange-Organization-AuthSource: MIA20725CAS891.apps.tmrk.corp X-MS-Exchange-Organization-AuthAs: Anonymous MIME-Version: 1.0
1st bad:
Received: from fldsmtpi02.verizon.com (166.68.71.144) by
MIA20725CAS892.apps.tmrk.corp (10.1.3.224) with Microsoft SMTP Server id 14.2.318.1; Mon, 5 May 2014 14:03:11 -0400
Received: from fldsmtpe04.verizon.com ([140.108.3.143]) by
fldsmtpi02.verizon.com with ESMTP; 05 May 2014 18:03:11 +0000
X-IronPort-Anti-Spam-Filtered: false X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai4HAHHRZ1PQdusRnGdsb2JhbABZgmVwgz+nQxCSNhuEGIMfAoEaFg4BAQEBAQgLCQkUKIItAiAjCikDAwECBgIkAiIEAgIDAXGIPAEDAZ1rihKkBheBKoQshW2GCoFLBIVJhDiPM5Yt Received: from lists.gnu.org ([208.118.235.17]) by fldsmtpe04.verizon.com
with ESMTP/TLS/AES256-SHA; 05 May 2014 18:03:00 +0000
Received: from localhost ([::1]:58830 helo=lists.gnu.org) by lists.gnu.org
with esmtp (Exim 4.71) (envelope-from <qemu-devel-bounces+don=cloudswitch.com@nongnu.org>) id 1WhNEC-0004ge-3G for Don@cloudswitch.com; Mon, 05 May 2014 14:03:00 -0400
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47084) by lists.gnu.org
with esmtp (Exim 4.71) (envelope-from <mjt@tls.msk.ru>) id 1WhNDS-0003hI-VC
for qemu-devel@nongnu.org; Mon, 05 May 2014 14:02:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <mjt@tls.msk.ru>) id 1WhNDM-00016J-Qz for
qemu-devel@nongnu.org; Mon, 05 May 2014 14:02:14 -0400
Received: from isrv.corpit.ru ([86.62.121.231]:56774) by eggs.gnu.org with
esmtp (Exim 4.71) (envelope-from <mjt@tls.msk.ru>) id 1WhNDM-00015i-Ez; Mon, 05 May 2014 14:02:08 -0400
Received: from tsrv.corpit.ru (tsrv.tls.msk.ru [192.168.177.2]) by
isrv.corpit.ru (Postfix) with ESMTP id EDAE340708; Mon, 5 May 2014 22:02:05 +0400 (MSK)
Received: from tls.msk.ru (mjt.vpn.tls.msk.ru [192.168.177.99]) by
tsrv.corpit.ru (Postfix) with SMTP id AB0D0661; Mon, 5 May 2014 22:02:05 +0400 (MSK)
Received: (nullmailer pid 24207 invoked by uid 1000); Mon, 05 May 2014
18:02:05 -0000
From: Michael Tokarev <mjt@tls.msk.ru> To: <qemu-devel@nongnu.org> Date: Mon, 5 May 2014 22:01:41 +0400 Message-ID: <1399312923-24129-1-git-send-email-mjt@msgid.tls.msk.ru> X-Mailer: git-send-email 1.7.10.4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 86.62.121.231 CC: <qemu-trivial@nongnu.org>, Michael Tokarev <mjt@tls.msk.ru> Subject: [Qemu-devel] [PULL 00/22] Trivial patches for 2014-05-05 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: <qemu-devel.nongnu.org> List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>, <mailto:qemu-devel-request@nongnu.org?subject=unsubscribe> List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel> List-Post: <mailto:qemu-devel@nongnu.org> List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help> List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>, <mailto:qemu-devel-request@nongnu.org?subject=subscribe> Errors-To: qemu-devel-bounces+don=cloudswitch.com@nongnu.org Sender: <qemu-devel-bounces+don=cloudswitch.com@nongnu.org> Return-Path: qemu-devel-bounces+don=cloudswitch.com@nongnu.org X-MS-Exchange-Organization-AuthSource: MIA20725CAS892.apps.tmrk.corp X-MS-Exchange-Organization-AuthAs: Anonymous MIME-Version: 1.0
1st good:
Received: from fldsmtpi02.verizon.com (166.68.71.144) by
MIA20725CAS891.apps.tmrk.corp (10.1.3.223) with Microsoft SMTP Server id 14.2.318.1; Mon, 5 May 2014 14:03:13 -0400
X-VzAPP: 1 X-IronPort-AV: E=Sophos;i="4.97,990,1389744000";
d="scan'208";a="713637359"
X-Local: true Received: from unknown (HELO don-760.CloudSwitch.com) ([162.47.5.40]) by
fldsmtpi02.verizon.com with ESMTP; 05 May 2014 18:03:13 +0000
From: Don Slutz <dslutz@verizon.com> To: <qemu-devel@nongnu.org> CC: =?UTF-8?q?Andreas=20F=C3=A4rber?= <afaerber@suse.de>, "Michael S. Tsirkin" <mst@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Don Slutz <dslutz@verizon.com> Subject: [PATCH v4 1/2] qdev: Display warning about unused -global Date: Mon, 5 May 2014 14:03:06 -0400 Message-ID: <1399312987-29499-2-git-send-email-dslutz@verizon.com> X-Mailer: git-send-email 1.8.4 In-Reply-To: <1399312987-29499-1-git-send-email-dslutz@verizon.com> References: <1399312987-29499-1-git-send-email-dslutz@verizon.com> Content-Type: text/plain Return-Path: dslutz@verizon.com X-MS-Exchange-Organization-AuthSource: MIA20725CAS891.apps.tmrk.corp X-MS-Exchange-Organization-AuthAs: Anonymous MIME-Version: 1.0
Tüm Yanıtlar (6)
Perhaps not the answer you are looking for, but have you considered moving old messages to an archive folder (e.g. based on the year)?
That would make it faster to do the repairs. Note: the 97000+ is about 20 months of e-mail... So by the time scale would be by the month. However valid threads to cover more then 1 month. So not at all clear on how to split the folder. The best way would be by threads, but since that is the main issue; this does not help with the root cause.
97,169 messages in the folder ...wow that's a lot.
Although you see a 'Folder' in the left Folder Pane, Emails are not stored in separated files in a folder.
They are stored one after the other in the order they are downloaded into a single file. When you access any email in that file, it opens the entire file which is using memory. If some corruption occured to that single file then you may risk losing everything in that file.
It is much better to use the creating of folders to try to organize those emails by eg: Client or Topic.
Anything older than a month ideally should be archived by month and year and folder structure should be selected as maintained. This keeps the files much smaller.
Archiving does not mean backup. It means the emails are still viewed via Thunderbird, but they have been moved from the main folder into 'Archives' folder, then by year and then by month and then by folder name.
example:
- > Archives
- >> 2014
- >>>>2014-01
- >>>>>>Client
- >>>>>>Sent
If you choose to view an email - right click and select 'open message in conversation', it will auto select all the threaded emails, no matter what folder, assuming threaded is switched on.
I would suggest you get a backup of those emails, if you have not done one recently.
Pop Backup info:
IMAP backup:
I would then organise those emails; move emails into suitable folders and Archive as advised.
Delete anything you do not want.
Then right click on Folder and select 'Compact'. This will remove all traces of messages 'marked as deleted' and free up some space. If compacting loses emails then your folder was corrupted and you will need the backup to restore them.
Info on compacting:
Info on how to maintain a healthy Thunderbird:
When you have organised all the emails, archived and compacted folder, then try to see if 'open message in conversation' retrieves the correct threaded emails.
Toad-Hall tarafından
This does not help. Archiving has issues:
1) Extremely slow 1000 messages takes a long time.
2) It flattens the folders and so each month becomes very large
3) With enough messages, thunderbird starts poping up the dialog box:
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
Here is a list of scripts that are reported at least 30 times each:
Script: chrome://messenger/content/folderPane.js:1727
Script: chrome://messenger/content/folderPane.js:1782
Script: resource://gre/components/newMailNotificationService.js:295
Script: chrome://messenger/content/folderPane.js:1729
Script: chrome://messenger/content/folderPane.js:1783
Script: resource://gre/components/newMailNotificationService.js:159
Script: resource://gre/components/newMailNotificationService.js:318
Script: resource:///modules/gloda/log4moz.js:399
Script: chrome://messenger/content/folderDisplay.js:1298
Script: resource://gre/components/newMailNotificationService.js:187
4) All the archive folder also have the reported problem. The messages in them are NOT threaded correctly and require a rebuild to fix.
3. Script issues are commonly caused caused by.
a) Anti virus programs (exclude the thunderbird profile folder from scans, disable email scanning entirely and remove MvAfee after year they obviously can not fix their product.
b) slow processors.
c) Shortage of Disk space
d) Clogged temp folders
The number of mails of folders in not relevant. I have some 27000 mails in the folder for this forum, and my inbox has around 20 thousand. I also have lots of local folders.
Now threading.
I really can make very little out of that messed up munged out rubbish this forum turned your headers into. I see a reference to msExchange... and am sorry to say Microsoft will scramble just about any thread because they apparently think it is done there way and have had multiple threading methods since 2000.
What is not clear is what your complaining about. Threading is done using the References: field and well and the message id field. You are complaining the wrong messages are being thread because why?
some general info on how the threading works http://kb.mozillazine.org/Stop_threading_by_subject