Closed Bug 1518071 Opened 7 years ago Closed 7 years ago

email date is wrong when printed

Categories

(Thunderbird :: Untriaged, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: lawrence.chan, Unassigned)

Details

(Whiteboard: [addon: Enigmail])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce: Thunderbird was installed with - gpg4win - Enigmail Actual results: When printing a decrypted email with Thunderbird v.60.4, the email date 17/07/2018 changed into 18/07/2017 on the printout. The date appeared correct on screen and it works fine when printing a normal (unencrypted) email. Thunderbird v.60.3 worked normally. Expected results: The email date should be printed correctly on printout.
Your description doesn't sound like a crash
Summary: email date crashes when print → email date is wrong when printed
Flags: needinfo?(patrick)

Enigmail mighty modify the date in the message database (and thus the date that is visible in Thunderbird), if the message date is additionally contained in the first content-type of a signed&encrypted message (that's the Memoryhole Specification).

However, the message date is not modified during printing (I did not manage to "modify" messages for printing). In other words, yes, it's possible, and no it's not a bug in Thunderbird.

It's the same problem as https://sourceforge.net/p/enigmail/bugs/837/

Marking as "invalid" because the error is not in Thunderbird.

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(patrick)
Resolution: --- → INVALID
Whiteboard: [addon: Enigmail]

Thank you for your comment.

This case was reported only because the printing of email dates worked in Thunderbird 60.3 but did not work in 60.4 since its release in 20 Dec 2018. I incorrectly thought that there was something different in between.

I am sure we will be able find a way out for this issue.

Thanks again.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.