239376 - SMTP AUTH fails to port 25

Status: RESOLVED INVALID

(MailNews Core :: Networking: SMTP, defect)

Description

[benc]

Mozilla 1.6f, Win XP
SMTP w/ "TLS, if available" on port 25.

(Server requres auth via TLS handshake, so other choices for "user Secure
Connection" are not viable.)

Sending mail results in an error from the SMTP server. The logs show a failure
to use SMTP AUTH.

The odd piece of info was that we found the problem to be port 25 specific.
(Working from home, my admin set me up w/ an SSH tunnel. When the tunnel ran on
localhost:25, the error occurred. When the tunnel ran on localhost:26, sending
mail worked.

Comment 1

[Christian Eyrich]

I'm somewhat confused by this and can't say if it's your description or the case
itself.
To get started what about a nice log? Please create one (see
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#smtp on how to)
and attach it here (please use the link above to do this).

Comment 2

[benc]

I created a log, and what I saw was STARTTLS returned an error (425?)
temporarily unavailable or something like that.

I'm negotiating w/ my sys admin right now about why, and if this is client vs.
server.

Comment 3

[Christian Eyrich]

BTW, are you using any anti virus software? If yes, please have a look at
http://www.eyrich-net.org/mozilla/mozvsav.html#two.

Comment 4

[Marius Strumyla]

for me SMTP auth is also failing. was testing with mozilla1.7b and tbird0.6 on
win2k.
i'll attach my SMTP logfile

Comment 5

[Marius Strumyla]

Attachment: smtp log

I have set to use username and password for STMP. tbird0.6 asks me for a
password and then I get relaying prohibited error. It used to work some time
ago but then it stopped. 
If I select save password with passwd manager, the passwd manager contains
smtp:// entry but it doesn't have a username, only <>.

Comment 6

[Christian Eyrich]

Thanks for the log.
Your problem doesn't look like a Mozilla problem. The login suceeded as you can
see but the server nevertheless throws the error. There's nothing a client could
do. I'd contact the admin and present the log to him if he says something like
"Mozilla is unsuported".
But if you say another client (Eudora, The Bat, OE or whatever) can send this
message via this server it's getting very interesting.

Username <> is ok for smtp, the username is in the left column before the @.

Comment 7

[Marius Strumyla]

I can send emails with Outlook. It may very well be that our admin chaged
something on Exchange server.

Comment 8

[Christian Eyrich]

But if something was changed it must have been changed for every client. As long
as the standard protocol is used, the server doesn't know which client is connected.
Maybe you can activate logging in Outlook (see
http://support.microsoft.com/?kbid=240347) and you/we can look for differences.

Comment 9

[Marius Strumyla]

> As long as the standard protocol is used

ok, it seems that Outlook is using a different protocol to deliver messages.
reading the kb article, i was not able to create a STMP log. netstat showed me
these ports were being used 1042 and 1053.

Outlook Express fails in the same way tbird0.6 does.

Comment 10

[Christian Eyrich]

Huh, well, I'd say time to call the admin.

Comment 11

[Mel]

I had this PORT 25 Problem - then I used PORT 587 and ot worked out sending Mail
OUT.

Mel.

Comment 12

[Matt Taggart]

I think the anti-virus comment was on the right track. Some anti-virus/anti-spyware software silently intercepts STARTTLS. I guess it's watching all outbound mail to ensure that the machine hasn't become a spam zombie and since encryption would prevent it from scanning mail it just intercepts the client sending STARTTLS. Pretty evil and hard to debug.

Comment 13

[Wayne Mery (:wsmwk)]

Christian, can this be closed based on comment  10?

Comment 14

[Christian Eyrich]

Yes, looks both problems are/have been server problems.