Closed
Bug 750100
Opened 13 years ago
Closed 13 years ago
Severe data loss while checking mail for UNIX Movemail account
Categories
(MailNews Core :: Movemail, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 748726
People
(Reporter: martijn, Unassigned)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725
Steps to reproduce:
System: Slackware Linux 13.1 32-bit (GCC 4.4.4, GTK+ 2.18.9). Using Mozilla's official precompiled Thunderbird 12.0 binary from releases.mozilla.org.
Problem: Severe email data loss while checking mail on Movemail (UNIX mail spool) account in Thunderbird 12.0. Only part of the first message is delivered into TB and the rest is lost. This happens even when starting TB in safe mode (using "thunderbird -safe-mode").
Problem is new as of 12.0 and does NOT occur in Thunderbird 11.0.1 and previous. Downgrading to TB 11.0.1 fixes the problem.
Steps to reproduce:
1. Create movemail account (Account Prefs -> Account Actions -> Add Other Account -> Unix Mailspool (Movemail)).
2. Deliver some mail messages in /var/mail/USERNAME
3. Check mail for the movemail account
Actual results:
Only a part of the header of the first message in the mail spool (/var/mail/USER) is delivered to TB, the rest of the message and all other messages waiting in the mail spool are lost. Below is a complete source code sample of such a corrupted message. (Note that it is interrupted in the middle of a header, i.e. MIME-Version.)
From ltsp-discuss-bounces@lists.sourceforge.net Thu Apr 26 11:19:35 2012
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-Path: <ltsp-discuss-bounces@lists.sourceforge.net>
Received: from lists.sourceforge.net (lists.sourceforge.net [216.34.181.88])
by tna.nl (8.14.4/8.14.4) with ESMTP id q3Q9JTmW026890
for <mdekker@tna.nl>; Thu, 26 Apr 2012 11:19:34 +0200
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.sourceforge.net; s=beta;
h=List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:Message-ID:Date:Reply-To:To:Subject:From:MIME-Version:Content-Type; bh=rI3VWkkWSRprBv6qyzxzdP+ZWP2wBU9hyJ0Wfz+sG+A=;
b=TgiW0VHliEOLeoK0lf09Y0V3SNlz13VbwZVhiuWz/CuZJnxZ+L87jPbMRz3fJTLE4dtwwpYxLnQfz4IUylpzwx/B+TwTVVq3mYuDvhc5oA5kRbAY6Ce1hs2GOvD/5ZrRQpHFcd5v1japwBB2c45RTtAlXrmZlMAvVhI1qrJo22I=;
Received: from localhost ([127.0.0.1] helo=sfs-ml-4.v29.ch3.sourceforge.com)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ltsp-discuss-bounces@lists.sourceforge.net>)
id 1SNKrH-0003bD-FN; Thu, 26 Apr 2012 09:19:27 +0000
Content-Type: multipart/mixed; boundary="===============8810006826432485841=="
MIME-Version: 1
Expected results:
All mail should have been delivered to TB as normal.
Reporter | ||
Updated•13 years ago
|
OS: Mac OS X → Linux
Updated•13 years ago
|
Component: General → Movemail
Product: Thunderbird → MailNews Core
QA Contact: general → movemail
Martijn, please try again with the TB 12.0.1 update which is expected to be released tomorrow. It contains the fix Magnus was referring to.
Making a backup of your ~/.thunderbird directory would be advisable, and you can also make a folder repair to be safe (right-click on an affected folder, then select Properties and click the "Repair Folder" button to reindex its contents).
Reporter | ||
Comment 3•13 years ago
|
||
The TB 12.0.1 update does seem to have resolved the problem. Thank you, rsx11m. I am marking this a duplicate of the bug referred to by Magnus Melin.
There is now a new, minor issue: every time mail for a UNIX mailspool account is checked, the string "spool path = /var/spool/mail/mdekker" is printed on standard output. This seems like a debugging line that should have been removed. I will file a separate bug about that if no one has already.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 4•13 years ago
|
||
I put a patch for removing the printf in bug 748726, which also has a comment mentioning that.
You need to log in
before you can comment on or make changes to this bug.
Description
•