Closed Bug 538373 Opened 16 years ago Closed 16 years ago

Disappearing e-mail messages due to New return receipt handler extension

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: pavel.zahradnik, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1 Thunderbird/3.0 After sending message it was not shown in sent mail folder. I tried to reindex sent mail folder but with no success. I explored appropriate mbox file and the message was there, but did not show in TB 3.0! I think the problem was because in mbox file the message started with "------=12345--From - Thu Jan 07 12:09:04 2010" instead of "From - Thu Jan 07 12:09:04 2010". After manually deleting the string "------=12345--" in mbox file the message is shown again in TB 3.0 I don't know why there was suddenly the string "------=12345--" in the beginning of the first line of message header but I have found more such messages in my mbox files so I dont't know whether it is safe to manually delete all "------=12345--" strings. I have a lot of mail so I didn't notice messages disappearing but now I can remeber messages I see in mbox file which are not shown in TB 3.0. Reproducible: Sometimes
Very probably the problem is related to extension (New return receipt handler) which makes some manipulation with "------=12345--" (e.g. reportContent = reportContent + allHeaders + "\n\n------=12345--")
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Summary: Disappearing e-mail messages → Disappearing e-mail messages due to New return receipt handler extension
Version: unspecified → 3.0
Pavel can you contact the add-on author ?
(In reply to comment #2) > Pavel can you contact the add-on author ? I have done already. Author released new version on 07/01/2010, from his email: "I think to have found out the cause of that bug and it should be fixed in 0.4.6.1 version, released now."
You need to log in before you can comment on or make changes to this bug.