198068 - Connection Fail error when sending to IMAP server

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: SMTP, defect)

Description

[Michael Whately]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

After upgrading from version 1.3a to 1.3, I receive a send message error when
sending email. It says "The message could not be sent because connecting to the
SMTP server failed." 
The messages go through, but a copy is not sent to my Send folder.


Reproducible: Always

Steps to Reproduce:
1.Compose an e-mail
2. Send it
3.

Actual Results:  
I get the above error message. The program does not think the email was sent.




This just start after upgrading to Vers. 1.3 from 1.3a

Comment 1

[Patrick]

No clue if it'll solve anything, but did you try to install into a fully clean
(manually cleaned out!) Mozilla folder?

any time-out setting that can play a role?

Comment 2

[bruno]

I get the same results using Mozilla 1.4b, but the prob. does not occur 100% of
the time -- I would guestimate about 20% of the time. I'm connecting to an IMAP
server where the 'sent' folder resides on the server. (sending/receiving email
both require SSL, and authentication -- port 993=receiving, port 25=sending ).
Your message gets sent, but it *seems that the message was not sent/fails
because of the following:
i. the error message appears when sending
ii. the message is *not copied to the 'sent' folder on the imap server

My System: Windows 2000 Pro -- SP3, Office 2000 -- SP3 

I've had 2 other users experience the same issue, but using Mozilla 1.3 on
Windows 2000 SP3.

For important email I often find myself sending the message 2 or 3 times because
I am not sure if the message was sent successfully. Obviously, this is *not a
good thing....

Comment 3

[Erich Bremer]

BUG # 213817 seems to be a duplicate of this one....

Comment 4

[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 5

[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.