109115 - Unable to connect to SMTP server (sending mail)

Status: VERIFIED DUPLICATE of bug 108912

(MailNews Core :: Networking: SMTP, defect)

Description

[Laurie Snyder]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Mac_PowerPC)
BuildID:    2001110808

The mail in .0.9.5 worked fine but after I upgraded to .0.9.5+, I was unable 
to send mail. 

Reproducible: Always
Steps to Reproduce:
1. Create new profile
2. Try to send mail

Actual Results:  It says something like: "Unable to connect to SMTP 
server. The server may be down or settings misconfigered."

I've created numerous new profiles and re-typed my mail preferences 
several times and nothing seems to work. I don't see any weird behavior 
on the front end, either. 

I'm running all my mail through another mail application right now so I 
know that the server isn't down or the settings are wrong.

This only happened after I installed .9.5+. The .9.5 mail worked fine but 
has a pretty signifcant glitch with the browser so I can't go back.

I'm not a programmer, but I can open the source files in BBEdit and look 
for stuff if you have anything you want me to look for.

Comment 1

[Matthias Versen [:Matti]]

Can you provide a log file ?
see -> http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 2

[Laurie Snyder]

I made a log file and checked and tried to send mail. Now when I open the log
file that's been created in the Mozilla folder, it's blank. Now what? Is this
the correct stuff to put in the text file when I create the log (obviously using
POP)?

ARGS: -mail
ENV:NSPR_LOG_MODULES=POP:5
ENV:NSPR_LOG_FILE=[Laurie_Log]

Comment 3

[Jacek Piskozub]

I've seen this behavior on WindowsME on builds later than 10/29. I could
reproduce this by just changing Use Secure Connection (SSL) from When Available
to Never (or the other way). Both settings should work, so this was a bug. 

I checked the communication with a TCP/IP sniffer. There were no packets
whatsoever exchanged with the server. That's why the reporter had a blank log.

Workaround: for me starting a 10/29 build and changing the Use Secure Connection
(SSL) setting revived the mail sending. I understand that any change to the SMTP
server settings would jump start this feature if you use the right Mozilla build.

One more observation: the prefs.js settings for SMTP looked OK at the time SMTP
did not work (that is, of course, after quitting Mozilla).

Confirming and changing to All/All. Will check this for today build and come back.

Comment 4

[Jacek Piskozub]

Yes, it happens still with 2001110809 build. To restore sending mail capability
I had to touch the SMTP setting with 20011029 build (as described above). Funny
thing : build 1029 crashed during sending mail test but it still corrected the
behavior for 1108. One more proof that this is not the settings (the pref files
were not touched as Mozilla died before the quit).

I wonder about upgrading the bug to Critical. The rules say that it is Major (a
major feature is broken but no crash or data loss) but I believe this feature is
so important that possibly worth Critical.

Comment 5

[Jacek Piskozub]

Changing summary to reflect that this is not a Mac only bug.

Comment 6

[Scott MacGregor]

I just upgraded to todays build (2001110803) and now I can't send either!
doesn't look like we are ever getting to the smtp protocol that's why the log is
empty.

Comment 7

[Scott MacGregor]

I bet this is a dup 108912. You guys should try looking at your account again,
clicking on the advanced tab and re-selecting the stmp server for that account.
That work around just got me sending again. Until the patch in that bug lands
try that out. 

Comment 8

[Laurie Snyder]

OK. You might be right. I just noticed a "Null" account AND my SMTP server in
the Advanced settings. (Don't know how I missed that before. Oh well.) I tried
deleting the Null account and it won't let me. Then I clicked on my SMTP server
and it let me send an email. I guess I'll see if it acts up again tomorrow.

Comment 9

[Jacek Piskozub]

It's not exactly a dup of 108912 as I have only one SMTP server and can
reproduce it easily without adding a second one, but I do agree that the
underlying problem may be identical.

Comment 10

[Laurie Snyder]

NOTE: Just checked out Bug 108912. I only had ONE mail account and started
several new profiles with only one account. 

My SMTP server and my incoming mail servers are different though (if that
matters) since I'm accessing my personal account from work.

This is also similar to my previous bug: 91633 in which I was working with a
migrated account.  

Comment 11

[Jacek Piskozub]

I had only one account. Messing with advanced (the workaround from bug 108912)
did not help. Neither simply toucing and confirming the setting, nor setting a
second one nor deleting and restoring. The only result is multiplication of
phantom accounts (I'll send an attachement). Notice the empty lines between the
two identical accounts. It must be something with reading and writing the SMTP
settings.

My workaround: using an Octber build to sort outbthe setting, still works.

Comment 12

[Jacek Piskozub]

Attachment: Results of messing with advanced SMTP settings

Before trying the workaround for bug 109115, this looked normal.

Comment 13

[Jacek Piskozub]

WFM with a fresh CVS build (WindowsME) after the patch for bug 108912. It seems
I was wrong this is different. Making this one a dup of 108912. If you disagree,
please reopen.

When checking this bug with a new build, please check also the original 108912
situaltion (two SMTP servers).

*** This bug has been marked as a duplicate of 108912 ***

Comment 14

[Ninoschka Baca]

Verified Duplicate.

Comment 15

[Ninoschka Baca]

Note: bug# 108912 mentions that the send problem also occurs with 1 account.
Just open the Account Settings dialog, select the OK button and you won't be
able to send. Workaround: Go into Account Settings, select the identity panel,
select the Advanced button, click on the down arrow to choose the server
(instead of using 'use the default server' option.