208581 - cannot send email when I login to the SMTP server

Status: RESOLVED INVALID

(MailNews Core :: Networking: SMTP, defect)

Description

[Kim Ong]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529

The SMTP function in the Mozilla 1.4 RC1 appears to be broken compared to the
last stable version 1.3.1. I have set up my SMTP login username and password
correctly in 1.3.1 and has no problem sending email. However, after I installed
1.4 RC1, I will receive the following error message:
"Sending of message failed.

The message could not be sent because connecting to SMTP server
smtp.vs.moe.edu.sg failed. The server may be unavailable or is refusing SMTP
connections. Please verify that your SMTP server setting is correct and try
again, or else contact your network administrator."

I have tried re-entering my email account information in 1.4RC1 but it does not
solve the problem. 

The SMTP server is "smtp.vs.moe.edu.sg" and the port is "8080" as this is a
school network and the default smtp ports are already blocked. The mailserver
was reconfigures to accept port 8080.


Reproducible: Always

Steps to Reproduce:
1. Setup the SMTP account information in the Outgoing SMTP Menu. Enter in the
SMTP server "smtp.vs.moe.edu.sg" port "8080" my username "kimfong". The SSL
setting is set to "Never".
2. Type an email and click send. 
3. Fail

Actual Results:  
The error message pops up.

"Sending of message failed.

The message could not be sent because connecting to SMTP server
smtp.vs.moe.edu.sg failed. The server may be unavailable or is refusing SMTP
connections. Please verify that your SMTP server setting is correct and try
again, or else contact your network administrator."

Expected Results:  
The version in 1.3.1 is working perfectly.

Comment 1

[Kim Ong]

I can still reproduce this problem with 1.4RC2. 

Comment 2

[Kim Ong]

The bug is still present in 1.4RC3!!

Should I be trying the latest daily build?

Comment 3

[Kim Ong]

Attachment: Login failed

A SMTP Log of a failed send.

Comment 4

[Kim Ong]

The SMTP Log was taken from the 1.4 Final. The email is still not sent out.

Comment 5

[Christian Eyrich]

The log shows that it's clearly a server error.

Starting with 1.4b Mozilla knows the CRAM-MD5 authentication mechanism. This one
is used preferably if the server knows it to. Your server says it does:
  250-AUTH LOGIN CRAM-MD5 PLAIN
in the log, but answers with
  421 child crashed (#4.3.0)
after Mozilla sent it's login information.

421 means "<domain> Service not available, closing transmission channel". As the
server closes the connection, Mozilla has no chance to fall back to a weaker
mechanism and try again.

Because that's the servers problem I close this bug. Please contact your admin
to configure the server properly (get CRAM-MD5 working right or disable it).
If think that's wrong, please reopen this bug.

Comment 6

[Christian Eyrich]

*** Bug 211108 has been marked as a duplicate of this bug. ***

Comment 7

[Gabriel Barros]

The problem in my case (Bug 211108) was that the server (a q-mail) didn't needed 
any indentification when the request came from the intranet. All i had to do was 
to disable "use name and password" on my smtp settings.

I just don't know how mozila 1.3.1 handled it since it had the "use name and 
password" checked too. Anyway, everything is ok with 1.4, thanks Christian.

Comment 8

[Christian Eyrich]

Gabriel, as I wrote Moz before 1.4b didn't know CRAM-MD5 authentication (like
e.g. Outlook does). So it didn't try it and the server didn't run into his
child-crash-problem.

If you disabled uthentication now from the intranet it works fine, yes. The
server doesn't reach the point where it crashes. But I think it would be good to
nevertheless contact your admin to solve the prob.