doesn't send long messages or attachments "...timing out connection..."



MailNews Core
Networking: SMTP
17 years ago
9 years ago


(Reporter: Mai Mai Tsai, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




17 years ago
I cannot send html pages, attachments or long emails using 6.1.  it says that it
is sending, but it tries for 5 minutes and then sends a message that the message
cannot be sent...

Comment 1

17 years ago
hmm, we just fixed a bug just like this on branch last friday. Any chance you
are using a branch build older than that? If you are using a current build, any
chance I can see the HTML message that is giving you the problem? 
Ever confirmed: true

Comment 2

17 years ago
using the 2001-06-07-13-0.9.1 build
getting this message after 5 minutes or so - 
An error occurred whil sending mail.  The mail server responded:
timing out connection to  Please check the message and try again.

Comment 3

17 years ago
Thanks for the extra information. One more question for ya. Under Edit / Mail
News Account Settings. Click on "Outgoing Server". There should be some text in
that prefs panel saying "Use secure connection (SSL)" * Never * When Available *
Can you tell me which radio button is selected? If it isn't set to Never can you
select never and then try to send the message again? If that works then this is
a dup of 84731

Comment 4

17 years ago
it's set to when available

I'll change to never and let you know if I experience the time outs - but yes
sounds like a dup.
Mai Mai

Comment 5

17 years ago
isn't this bug SMTP and not IMAP?
Please attach a mail log...

Just do this from a command prompt:
c:\moz\mozilla.exe -mail
I also have a similar problem.
I cann't send attachments.
My configuration is the next:
A latop  with Mozilla 1.0 and NetBSD 1.5.3 RC1 on i386

I have defined three accounts:
1. The first one is for the office and it works ok. I use a lan connection
against a Exchange Server. I use IMAP for read e-mails and I use smtp
for send e-mails.There isn't any problem with this account. I can send
attachments without problems
2. I use the second and third accounts at home, using a modem connection
with a external modem.I use the same computer (it is a laptop).I can't send
attachments with these accounts. I obtain this bug when I use a attachment:

An error ocurred while sending mail. The mail server responded: tsmtp1.mail.isp
timing out connection to []

Please check the message and try again

The three e-mails accounts use user/password authentication (both office and home).

The mail transfer always stops and timeouts at the same point of the
 transmission of the e-mail (by example for a 57k email it stops at 19% of the
transfer). It stops always after of the authentication properly the
user/password of my account and a initial transfer of the e-mail. 

I have tried to send the same message with Windows 98/Mozilla 1.0 using the 
same modem and same modem connection and it works ok.
same connection

The component of this bug says Networking IMAP. It must be changed to SMTP bug,

Do you need debug information?


16 years ago
Component: Networking: IMAP → Networking: SMTP
QA Contact: huang → meehansqa

Comment 7

14 years ago
I've got the same problem.
Mozilla version 1.7b and 1.8a (Gecko/20040417)

I also cannot send email with attachement through the yahoo web mail. 
I've got an SMTP connection, never SSL.
For other info just ask.
Product: MailNews → Core

Comment 8

12 years ago
Jacques, Jose, is this still a problem?
Assignee: mscott → nobody
OS: Other → Windows XP
QA Contact: meehansqa
I can't comment about this problem

I don't use the setup of three accounts with mozilla/seamonkey from years ago.

I use now Seamonkey with a only email server (my company email server).

Comment 10

10 years ago
no response from reporter
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
Summary: doesn't send long messages or attachments → doesn't send long messages or attachments "...timing out connection..."


9 years ago
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.