Closed Bug 288229 Opened 20 years ago Closed 19 years ago

SMTP settings in Thunderbird correct, however cannot send mail. This is a widespread problem effecting many many users. All documentation on such errors does not solve problem.

Categories

(MailNews Core :: Networking: SMTP, defect)

1.7 Branch
x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bugzilla, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999

Please see this thread for a complete history of the problem:
http://forums.mozillazine.org/viewtopic.php?t=239348

In short, when trying to send mail, I get stuck in a loop when requesting
password as described in the very last paragraph of this KB page:
http://kb.mozillazine.org/Thunderbird_:_Issues_:_Cannot_Send_Mail
However, following the instructions: "The fix is to go to Edit -> Account
Settings -> Outgoing server(SMTP) and turn off your name and password. You ISP's
server does not require these, and it is confused when it gets them." Does not
solve the problem, only leaves me with another error message, stating that I am
not authorized by my server (Obviously because I turned the password function
off.) to send mail via SMTP Relay.

Many many users are having the same exact problem.

1. I have verified, since I own the servers, that all SMTP server information
and settings are entered correctly in Thunderbird.

2. I have followed the instructions listed in the KB, maticulously, as provided
via links in the thread mentioned above, to no avail. 

3. The same exact server settings work fine in Outlook and other mail programs.

The above evidence leads me to believe there is a flaw in Thunderbird 1.0.2, or
we are missing some hidden settings somewhere. Please advise. Thank you.

Reproducible: Always

Steps to Reproduce:
1.Setup SMTP server. 
2.Try to send mail.
3.Repeat from step one until your hair falls out.

Actual Results:  
When trying to send mail, via SMTP, I am asked for my SMTP mail password. Upon
entering it, a Thunderbird tries to authenicate, and fails, again, asking me for
my password. This continues infinately, until I hit "Cancel", to which Im
presented with an error, stating: " Sending of message failed. The message could
not be sent because of connecting to SMTP server [servername] failed. The server
may be unavailable or is refusing SMTP connections. Please verify your server
settings are correct and try again, or else contact your network administrator."

If I uncheck the username and password setting in Server Settings, as instructed
by the KB when encountering this infinate loop, I am presented with this error
message: "An error occured while sending mail. The server responded 5.7.1
[recipient email address here]... Relaying denied. Proper authentication
required. Please verify that your email address is correct in your mail
preferences and try again.

Expected Results:  
Sent mail successfully.
Oops! Suppose I should add that Im using v1.0.2
Version: unspecified → 1.0
PLease create a SMTP log:
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html
(with enabled authentification)
Error Log Follows:
0[2743f8]: SMTP Connecting to: troykristoffer.com
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 220 ensim1.fireberry.com ESMTP Sendmail
8.12.10/8.12.10; Fri, 1 Apr 2005 12:57:07 -0500
0[2743f8]: SMTP entering state: 15
0[2743f8]: SMTP Send: EHLO [192.168.1.104]

0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-ensim1.fireberry.com Hello
c-24-91-70-186.hsd1.ma.comcast.net [24.91.70.186], pleased to meet you
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-ENHANCEDSTATUSCODES
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-PIPELINING
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-8BITMIME
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-SIZE
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-DSN
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-ETRN
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250-DELIVERBY
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 250 HELP
0[2743f8]: SMTP entering state: 4
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334
PDUxNDU1NTMxMC41MDgyMDQ2QGVuc2ltMS5maXJlYmVycnkuY29tPg==
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 18
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 16
0[2743f8]: SMTP Send: AUTH LOGIN

0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334 VXNlcm5hbWU6
0[2743f8]: SMTP entering state: 14
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334 UGFzc3dvcmQ6
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 18
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334
PDQzMjI0NTQ0My41MDgyMDU2QGVuc2ltMS5maXJlYmVycnkuY29tPg==
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 18
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 16
0[2743f8]: SMTP Send: AUTH LOGIN

0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334 VXNlcm5hbWU6
0[2743f8]: SMTP entering state: 14
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334 UGFzc3dvcmQ6
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 18
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334
PDExNTAxNjI4MDUuNTA4MjA2OUBlbnNpbTEuZmlyZWJlcnJ5LmNvbT4=
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 18
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 16
0[2743f8]: SMTP Send: AUTH LOGIN

0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334 VXNlcm5hbWU6
0[2743f8]: SMTP entering state: 14
0[2743f8]: SMTP entering state: 17
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 334 UGFzc3dvcmQ6
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 18
0[2743f8]: Logging suppressed for this command (it probably contained
authentication information)
0[2743f8]: SMTP entering state: 0
0[2743f8]: SMTP Response: 535 5.7.0 authentication failed
0[2743f8]: SMTP entering state: 19
0[2743f8]: SMTP entering state: 22
0[2743f8]: SMTP entering state: 17
0[2743f8]: SMTP entering state: 12
0[2743f8]: SMTP entering state: 13
Assignee: mscott → sspitzer
Component: Account Manager → Networking: SMTP
Product: Thunderbird → Core
Version: 1.0 → 1.7 Branch
Im now 99% sure this is a bug in my client. I've tried several ISP's and all of
them return the same results, even though I have meticulously checked the server
settings to ensure accuracy. The story is the same on the Mozillazine boards for
many users. Since this is preventing us from SENDING mail, which is the whole
point of email service, I upped this to critical. 

Also of note, not sure if its important, but I've tried several nightly builds
back into history, and all have the same problems, suggesting that the bug may
be caused by something local? (Which would explain why, not every user is having
the problem too, just many.) 

If you would like my ISP's SMTP Log (not the one currently posted in this
report) I can probably get it for you, if needed, since I own the server.
Severity: major → critical
no crash, memory leak = not critical
You could/should try a new profile...
Severity: critical → major
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.