Closed Bug 47835 Opened 25 years ago Closed 25 years ago

Changing SMTP servers may not cause state machine reset

Categories

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

x86
Linux

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dmosedale, Assigned: mscott)

Details

(Whiteboard: [nsbeta3+])

Set your SMTP server to obob.netscape.com, and try to send a message. It will fail with an error message about authentication, because obob is not configured to accept messages on an unauthenticated SMTP connect. This is fine. Now, go set your SMTP server xwing.netscape.com; this is an example of a machine which is configured to require a HELO handshake. Then try and send the message. It will fail with an error along the lines of "Polite people say HELO first." What seems to be happening is that despite the change in SMTP server, Mozilla is not resetting the state machine, so it believes that it doesn't need to restart the protocol handshake.
This must be what's causing 47324 and 47811
I have a fix for this. Some smtp capabilities caching code jeff checked in back in june broke this stuff.
Keywords: correctness, nsbeta3
Target Milestone: --- → M18
.
Whiteboard: [nsbeta3+]
Fix checked in.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
QA Contact: lchiang → esther
I am using 2000092809 branch builds on windows and mac and linux. I am seeing the message for non authentication appear on mac and windows but not linux. the HELo message is sent in all the cases
I take some of my words back. We do have cert management in place.
Oops ... Wrong bug...
verifying
works !
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.