235400 - unable to send long mail over SSMTP.

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: SMTP, defect)

Description

[Jan Luehr]

User-Agent:       
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040123 Debian/1.6-1.he-1

Greetings,

situation.
Client: Mozilla 1.6 on Windows (also reproduceable on linux - other OS's I
havent checked, cause I don't have access to 'em)
Server: Debian Woody with standard exim installation, including SMTP-auth and
tunneled over SSL.
Problem:
If trying to send an E-Mail, more than a bunch of line long, mozilla complaints:
An error occured while sending mail. The mail server responded p15149772 SMTP
incoming data timeount - closing connection. Please check the message in try again.

This isn't a server problem in my opion, cause KMail and Mozilla 1.5 delevire
even longer E-Mails using the same server without any problems.

Regards. J.Luehr

Reproducible: Always
Steps to Reproduce:
1.Use a SMTP Server with SMTP-auth and SSL
2.Compose a Message longer than 170 Lines fully written (I don't know the exact
limit, I send log-files to reproduce it)
3.Try to send it.

Actual Results:  
The error described above occured.

Expected Results:  
The mail should have been send without any problem.

Have no ;)

Comment 1

[Sven Krohlas]

I've had a similar problem during tha last few days, and now I finally found
out what it was: a routing problem, but the symptoms were similar to yours.
My network interfaces all used an mtu of 1500, but my router dropped such
long packets, because the ppoe line behind could only carry packages up to
1492.
Debugging was really annoying, I was able to send messages using telnet (!),
but Mozilla wasn't...
Anyway, could you possibly see a similar problem?

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.