224822 - Can't send encrypted email with 1.6a and later after applying latest MacOSX (panther) fixes

Status: RESOLVED DUPLICATE of bug 224138

(MailNews Core :: Networking: SMTP, defect, P2)

Description

[Larry Riffle]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007

As of today I can sign and decrypt email but not encrypt with either 1.6a or the
latest nightly (10/29) for MacOSX. The only change I can think of are the two
fixes I downloaded from Apple this morning.

2003-11-05 07:47:57 -0500: Installed "Security Update 2003-11-04" (1.0)
2003-11-05 07:48:02 -0500: Installed "Xcode Update 2003-11-03" (1.0.1)

After I click "send" the progress bar goes to ~50% and stops. I've waited over
an hour and tried multiple smtp servers.

After going back to 1.5 all is fine again.


Reproducible: Always

Steps to Reproduce:
1.compose email
2.select sign and encrypt
3.click send

Actual Results:  
Progress bar advances to ~50% and stopped.

Expected Results:  
completed send

A co-worker with an identical configuration (including the fixes from Apple) has
reproduced the problem.

Comment 1

[Wan-Teh Chang]

Julien, could this be related to bug 224663?

Larry, could you use Edit->Preferences->Privacy & Security
->Certificates->Manage Certificates->Your Certificates to
look at the certificate in question and see what its status
is under the Purposes column?

Comment 2

[Wan-Teh Chang]

Assigned the bug to Julien.

Comment 3

[Larry Riffle]

Signing was no problem only encryption.

My cert has "client,sign,encrypt" as did the certs for the several recipients I
tried. I tried sending to a recipient with a Thawte freemail cert in addition to
several with PSU/CREN issued certs. 

All of these had worked previously and do again with 1.5.

Comment 4

[Julien Pierre]

Larry,

We need to distinguish the problem here. Is the failure occurring when the
e-mail is being signed and encrypted, or when it is being sent over SMTP ?

To determine that, please try to encrypt your e-mail again, and select "file" /
"save as" / " draft" rather than clicking the "send" button. This will save the
encrypted e-mail in your "Drafts" folder. If this works, it means the encryption
is working fine, and the failure is at the SMTP networking level.

Also, who are you encrypting the e-mail to ? Is it to yourself, or somebody else
? Please try both cases.

Comment 5

[Larry Riffle]

I tried saving the encrypted email. It worked. Only send was a problem and then
only encrypted.

I sent to several different ids in our system and at external ISPs. No difference.

The coworker who duplicated the problem said he did some tracing and the "hang"
was at the end of the transmission to SMTP. I've ask him to provide his trace
data. He's on the CC list.

Comment 6

[Larry Riffle]

MacOSX 10.3.1 and 10/29 nightly - no change

Comment 7

[Larry Riffle]

It took a while to climb the learning curve but I now have a debug build from
source checked out of CVS this morning up under MacOSX 10.3.1 (per instructions
at http://www.mozilla.org/build/mac.html) on the same machine where I
encountered the problem. It exhibits the same symptoms. All is still ok with 1.5.

Somebody will have to walk me thru it but if I can help debug this I'm willing.
I'll also RTFM if somebody will point me to the right FM.

Comment 8

[Phil Pishioneri]

Attachment: ethereal packet trace of failing smtp transaction

Here's an ethereal packet trace of a smtp transaction with 1.6a that gets
stuck.

Comment 9

[Phil Pishioneri]

Attachment: ethereal packet trace of successful smtp transaction

ethereal packet trace of good smtp transaction (for comparison against failing
one).

Comment 10

[Phil Pishioneri]

I've attached two ethereal packet trace files showing a good vs. a hung smtp
transaction.

Decoding the TCP streams with ethereal, the last data in the stuck connection
(which is ACK'd by the smtp server) is the last line of the base64 encrypted
message, while the good message continues with the ending Mime separator and the
rest of the smtp conversation.

Ending part of hung conversation:
wRRTjkRjH5YRt70pY1foL9QO3mb1Urc6CyD0JpdnBkZ4+NEJGh+E6guqCKmmEgJgdN+EsuWa
fPP761SqZLyj3mFuJkPXaCWZJDOlSyVQjYJINr+AVo2pbkAYGCqCzZVDOze9fQzb8v40Uf48
0ZV7Ad+ziiuYXrZdBAgOtpZTHB92KAAAAAAAAAAAAAA=.
[end of ASCII part of stream]

Ending part of good conversation:
tQ1jAe6hnzzmZ98vdw0XesFjonJxJ+naphyfL4bPCAmbGcuot3HGRFx2nwSayYybvrVcL567
N9O3DRbT+3aoHSoAAAAAAAA=
--------------ms050708000809040507090102--
.
250 2.0.0 hA5JnmWU032632 Message accepted for delivery
QUIT
221 2.0.0 f05n03.cac.psu.edu closing connection
[end of connection]

Comment 11

[Phil Pishioneri]

Attachment: Mozilla protocol log file of stuck smtp transaction, logging level 5.

Comment 12

[Phil Pishioneri]

Attachment: Mozilla protocol log file of good smtp transaction, logging level 5.

Comment 13

[Julien Pierre]

The product/component for this bug should not be NSS/Libraries. Please reassign
to the appropriate networking component (sorry, I don't know which one that
would be).

Comment 14

[Nelson Bolyard (seldom reads bugmail)]

Changing Product to mailnews for this apparent SMTP regression

Comment 15

[Nelson Bolyard (seldom reads bugmail)]

Reassigning bug to mailnews owner of SMTP.

Comment 16

[Nelson Bolyard (seldom reads bugmail)]

Changing subject to show that the problem is not that encryption fails, but
rather that the succesfully encrypted message is (reportedly) not sent.

Comment 17

[Larry Riffle]

I did a fresh checkout and build with the recently checked in fix for 224138. It
works now.

Not sure of the etiquette here but since I opened this in the 1st place, I'm
marking it as a duplicate of 224138. 

(I swear I did a search before I opened this and didn't find the dup.)

*** This bug has been marked as a duplicate of 224138 ***