smtp connection is lost after recieving banner message

RESOLVED WORKSFORME

Status

MailNews Core
Networking: SMTP
--
major
RESOLVED WORKSFORME
15 years ago
9 years ago

People

(Reporter: Ross Kirk, Assigned: Scott MacGregor)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3; MultiZilla v1.4.0.3e) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3; MultiZilla v1.4.0.3e) Gecko/20030312

If the banner message sent by the smtp server is contained within more than one
packet mozilla 1.3 will drop the connection to the server.  If the banner
message is sent in only one packet mozilla correctly communicates with the smtp
server.

This has been verified by changing the server to send using one packet or
multiple (two) packets.

This did not affect the mozilla 1.2 release, which worked correctly with
multi-packets

Reproducible: Always

Steps to Reproduce:
1.select an smtp server that sends a banner message in more than one packet
2.compose and send a new message
3.mozilla establishes connection to server and drops connection without sending
any data

Actual Results:  
A generic error message was displayed saying that the server could not be
connected to/wasnt available

Expected Results:  
it should have sent the email

This was verified by changing the server to send a one packet banner message and
a multiple (two) packet banner message, the config of mozilla was not changed

Comment 1

14 years ago
using 20031003 I wasn't able to reproduce
please try a more recent build
if the bug is still there please reopen this bug

if you can provide an SMTP server where this is the case then we can reopen,
otherwise it's really really hard to reproduce this bug. it's also more than 6
months ago than this bug was reported.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 2

14 years ago
Tested with Mozilla 1.4 and this is no longer an issue
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.