277380 - Intermittently unable to send messages

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Mustafa Jamil]

Distro: FC3
Kernel: 2.6.9-1.681_FC3smp
RPM: thunderbird-0.9-1.fc3

I have to restart thunderbird at least two or three times a day to send messages
successfully.  On the occasions when I have issues, I press Send and the
"connecting to <smtp server>..." dialog box opens, and stays that way till the
send attempt times out.  Restarting thunderbird solves the problem every time; I
connect almost instantaneously to the server, send the message, and save the
message to my Sent items.

On most of these occasions, I just decide to save to my Drafts folder, restart
thunderbird, and resend the message.  On some rare occasions, even that doesn't
work; saving to the Drafts folder has the same issue.  I'm forced to paste my
message to an editor, restart thunderbird, re-paste my message into a new
compose window, and then send the message.  

As you can imagine, this is getting to be a PITA.

The incoming mail server uses IMAP.  Both the IMAP server and the SMTP server
are hosted on the same machine.  The machine is 17 hops away.

I ran imap and smtp logging at debug level 5 to see whether this would shed some
light on the issue.  It didn't.  The only entry relevant seems to be:

-151082656[881a538]: SMTP Connecting to: mail.linuxcare.com

followed by periodic imap lookups (so repeats of the following excerpt):

-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:SendData: DONE^M
-188744784[f5037848]: ReadNextLine [stream=f4c7fa88 nb=22 needmore=0]
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:CreateNewLineFromSocket:
40 OK IDLE completed^M
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:ProcessCurrentURL: entering
-188744784[f5037848]:
f4fc5a98:mail.levanta.com:S-INBOX:ProcessCurrentURL:imap://[e-mail]:143/select%3E/INBOX:
 = currentUrl
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:SendData: 41 check^M
-188744784[f5037848]: ReadNextLine [stream=f4c7fa88 nb=23 needmore=0]
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:CreateNewLineFromSocket:
41 OK CHECK completed^M
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:SendData: 42 UID fetch
18004:* (FLAGS)^M
-188744784[f5037848]: ReadNextLine [stream=f4c7fa88 nb=48 needmore=0]
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:CreateNewLineFromSocket:
* 1514 FETCH (UID 18003 FLAGS (\Recent \Seen))^M
-188744784[f5037848]: ReadNextLine [stream=f4c7fa88 nb=27 needmore=0]
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:CreateNewLineFromSocket:
42 OK UID FETCH completed^M
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:SendData: 43 IDLE^M
-188744784[f5037848]: ReadNextLine [stream=f4c7fa88 nb=20 needmore=0]
-188744784[f5037848]: f4fc5a98:mail.levanta.com:S-INBOX:CreateNewLineFromSocket:
+ Waiting for DONE^M

The dialog box hung around for over two hours on this last error until I finally
cancelled the operation (I wanted to see whether it would time out; doesn't look
like it).

If there's any other info I can provide, please let me know.

Comment 1

[Mustafa Jamil]

Looking at the mail server log, I see logs of the following form:

Jan  7 09:49:51 mail sendmail[21199]: STARTTLS=server,
relay=node-d8e90d1e-aus-onnet.us.uu.net [216.233.16.30] (may be forged),
version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-SHA, bits=256/256

Jan  7 09:49:52 mail sendmail[21199]: j07Hnp5c021199: from=<[e-mail]>,
size=1087, class=0, nrcpts=1, msgid=<[e-mail]>, proto=ESMTP,
daemon=IPv4, relay=node-d8e90d1e-aus-onnet.us.uu.net [216.233.16.30] (may be forged)

when a send request goes through successfully, but I see no logs regarding a
connection attempt on the times my connect request fails.

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.