Closed Bug 496627 Opened 16 years ago Closed 14 years ago

S/MIME digital signature gets corrupted "sometimes" or missing from message body

Categories

(MailNews Core :: Networking: IMAP, defect)

1.9.1 Branch
x86
Windows Vista
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: zhalassy, Unassigned)

Details

(Whiteboard: [has protocol logs])

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; hu; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; hu; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 I sent an msinfo (created by msinfo32, file -> export) to a foreign e-mail address (with S/MIME digital signature), then i noticed my own sent message in the IMAP Sent folder, it has a corrupted signature (envelope icon with a red X on the bottom right corner). Reproducible: Sometimes Steps to Reproduce: I tried to reproduce it, but the results were strange and weird. I tried to send several messages to myself and some gmail account. I could produce but not reproduce the following situations: The signature appeared missing two times, Ctrl + U showed "Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; ..." but there was no "smime.p7s" attachment shown (but read further)... I tried to attach pictures, small and big texts, sometimes they got thorugh without apparant error, three times not. With the picture, in the IMAP folder showed a bad signature, but the picture itself was ok. but in the incoming folder i couldn't open the picture, it was cut around 10% of it's height. Now comes the weird part, i deleted all the messages, so all of the got into the trash folder, now all the signatures are there (!), and ok. Actual Results: Sometimes the signature attachment is missing from even the Ctrl+U window. Mostly it's there, but sometimes the letter shown as corrupted. Expected Results: Signatures and messages should be intact, and Ctrl+U should show the original envelope. It happened i sent exactly the same message twice, first it got corrupted, second it was ok...
Zoltan thanks for the bug. Could you try spend some time reproducing ? When you reproduce can you save a proper message and a non proper one and add them as attachment to this bug. Also it seems that your issue might be related to saving messages on imap servers. Could you enable logging(https://wiki.mozilla.org/MailNews:Logging ) when you try to reproduce. It would be very nice for you to try to reproduce - because with the information you have given us so far there is little chance that the programmers can figure out what caused the issue you encountered.
I had some time to test this again. I had success for first try this time. I opened mspaint. Created a blank canvas with 1024x768 size, left it white. I saved it as a 24bit bmp (so it's bigger than 2 megs). Clicked on "new message", entered a subject "test1", also entered it as body too, "test1". Then i just simply attached the huge bmp, and clicked send (signing is turned on by default). It took some secs till it was sent over smtp, then again some time it was saved to the imap folder as a copy. Now both message in sent and inbox are "corruped", claims the thunderbird. I added my mailbox to outlook, the signature seems intact at both places. Server has a Cyrus 2.3.13, using it over an SSL connection.
imap.log, compressed. level 5 of imap logging. Strange, thunderbird even stopped putting messages now in the sent imap folder, tough it uploads it after smtp-ing it.
Moving to Network:Imap to have a few pair of eyes looks at the imap log provided.
Component: Security → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: thunderbird → networking.imap
Version: unspecified → 1.9.1 Branch
I don't know it's important or not, I am using this IMAP server over IPv6.
Still having the issue with version 5.0 ?
Whiteboard: [has protocol logs]
I didn't meet with this bug since a long time ago. Thank you.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: