problem send emails with wingate proxy

RESOLVED EXPIRED

Status

MailNews Core
Networking: SMTP
RESOLVED EXPIRED
14 years ago
9 years ago

People

(Reporter: Thiago Serra, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031019
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031019

when i try send a email with wingate proxy (smtp service activate for redirect
the email to a real smtp account) the mozilla mail tell me:

"Sending of message fail.
The message could not be sent because connection to smtp server 192.168.1.8
failed. The server may be unavailable or is refusing smtp connections..."

on the log of proxy the error is:

"03/03/04 10:50:10 192.168.1.42 Guest 0000209816 Error: Client closed
connection unexpectedly expecting HELO - terminating"

the configuration of the smtp server is:

server name: 192.168.1.8
port: 25
use name and password: not marked, not necessary
use secure connection (SSL): Never

the error was ocurred in versions 1.5 and 1.6

Reproducible: Always
Steps to Reproduce:
1. with proxy wingate installed and smtp server activate 
2. configure smtp server name on mozilla mail with the ip of wingate proxy and
port (25)
3. send a email...

Actual Results:  
the error describe on details...

Expected Results:  
send a email with proxy

Comment 1

14 years ago
I installed WinGate to test this issue but it worked without problems.

I hope a communications log will give a hint what goes wrong on your config. 
Please see http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#smtp
how to create such a log and attach it here.

Comment 2

14 years ago
*** Bug 237017 has been marked as a duplicate of this bug. ***
(Reporter)

Comment 3

14 years ago
(In reply to comment #1)
> I installed WinGate to test this issue but it worked without problems.
> 
> I hope a communications log will give a hint what goes wrong on your config. 
> Please see http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#smtp
> how to create such a log and attach it here.

I try create a log with information in
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#smtp but the
archive created is empty.

I am a user of Linux Slackware 9.1 with mozilla 1.6 (Mozilla/5.0 (X11; U; Linux
i686; en-US; rv:1.6) Gecko/20040123) instaled.

what version of wingate you try? (my version is 5)

Comment 4

14 years ago
I just downloaded the 5.2.3 evaluation on their website.

For the log, did you replace the IMAP with SMTP in the environment variable to
set? On Linux, when you set the variable in one console, you should start
Mozilla from this console then. Did you?
(Reporter)

Comment 5

14 years ago
(In reply to comment #4)
> I just downloaded the 5.2.3 evaluation on their website.
> 
> For the log, did you replace the IMAP with SMTP in the environment variable to
> set? On Linux, when you set the variable in one console, you should start
> Mozilla from this console then. Did you?

no.. i forgot... !

the log generate was:

bash-2.05b# more /tmp/mozilla-log

--- begin ---
16384[80ac0a8]: SMTP Connecting to: 192.168.1.8
16384[80ac0a8]: SMTP entering state: 0
16384[80ac0a8]: SMTP Response: 220 SMTP Server Service ready
16384[80ac0a8]: SMTP entering state: 14
16384[80ac0a8]: SMTP Send: EHLO yahoo.com.br
16384[80ac0a8]: SMTP entering state: 0
16384[80ac0a8]: SMTP Response: 220 SMTP Server Service ready
16384[80ac0a8]: SMTP entering state: 14
16384[80ac0a8]: SMTP Send: EHLO yahoo.com.br
16384[80ac0a8]: SMTP Connecting to: 192.168.1.8
16384[80ac0a8]: SMTP entering state: 0
16384[80ac0a8]: SMTP Response: e ready
16384[80ac0a8]: SMTP entering state: 14
16384[80ac0a8]: SMTP entering state: 12
16384[80ac0a8]: SMTP entering state: 13
16384[80ac0a8]: SMTP Connecting to: 192.168.1.8
16384[80ac0a8]: SMTP entering state: 0
16384[80ac0a8]: SMTP Response: 220 SMTP Server Service ready
16384[80ac0a8]: SMTP entering state: 14
16384[80ac0a8]: SMTP Send: EHLO mt.senac.br
16384[80ac0a8]: SMTP entering state: 0
16384[80ac0a8]: SMTP Response: 220 SMTP Server Service ready
16384[80ac0a8]: SMTP entering state: 14
16384[80ac0a8]: SMTP Send: EHLO mt.senac.br
16384[80ac0a8]: SMTP Connecting to: 192.168.1.8
16384[80ac0a8]: SMTP entering state: 0
16384[80ac0a8]: SMTP Response: 220 SMTP Server Service ready
16384[80ac0a8]: SMTP entering state: 14
16384[80ac0a8]: SMTP Send: EHLO ig.com.br
16384[80ac0a8]: SMTP entering state: 0
16384[80ac0a8]: SMTP Response: 220 SMTP Server Service ready
16384[80ac0a8]: SMTP entering state: 14
16384[80ac0a8]: SMTP Send: EHLO ig.com.br
--- end ---

ok?

Comment 6

14 years ago
Hm, quite weird log. But it looks like what I expected from the proxies error
message in your report.
The proxy seems to be irritated by our EHLO (extended HELO) and reissues the 220
ready response.
But according to RFC if a server/proxy doesn't understand a command it should
issue a 5xx (in this case I guess 500) response. In this case Mozilla would try
the old HELO.

But in any case, when testing WinGate here I get the expected 250 response after
EHLO. Are you using a version < 5.2.3 (though I didn't find I fix in the history)?

And a test you could do, if you enter "telnet 192.168.1.8 25" in the console,
you should get the 220 line and answer with "EHLO yahoo.com.br". Is the answer 220?
(Reporter)

Comment 7

14 years ago
(In reply to comment #6)
> Hm, quite weird log. But it looks like what I expected from the proxies error
> message in your report.
> The proxy seems to be irritated by our EHLO (extended HELO) and reissues the 220
> ready response.
> But according to RFC if a server/proxy doesn't understand a command it should
> issue a 5xx (in this case I guess 500) response. In this case Mozilla would try
> the old HELO.
> 
> But in any case, when testing WinGate here I get the expected 250 response after
> EHLO. Are you using a version < 5.2.3 (though I didn't find I fix in the history)?
> 
> And a test you could do, if you enter "telnet 192.168.1.8 25" in the console,
> you should get the 220 line and answer with "EHLO yahoo.com.br". Is the answer
220?

here is the log of test that you propouse (telnet 192.168.1.8 25):

-- begin ---

bash-2.05b# telnet 192.168.1.8 25
Trying 192.168.1.8...
Connected to 192.168.1.8.
Escape character is '^]'.
220 SMTP Server Service ready

421 Try using an SMTP agent to send valid SMTP commands. Goodbye
Connection closed by foreign host.
bash-2.05b# telnet 192.168.1.8 25
Trying 192.168.1.8...
Connected to 192.168.1.8.
Escape character is '^]'.
220 SMTP Server Service ready
EHLO yahoo.com.br
502 Command not implemented
"EHLO yahoo.com.br"
421 Try using an SMTP agent to send valid SMTP commands. Goodbye
Connection closed by foreign host.

-- end --

seems that erros is on proxy, no?
my version of wingate is 5.0.0 (build 734)...


thank you for help!

thiago

Comment 8

14 years ago
> 220 SMTP Server Service ready
> EHLO yahoo.com.br
> 502 Command not implemented

Hm, that's what it should answer if EHLO isn't implemented. We would handle this
response and try HELO then. But the logs shows another behaviour.

> "EHLO yahoo.com.br"
> 421 Try using an SMTP agent to send valid SMTP commands. Goodbye
> Connection closed by foreign host.

" ist not valid, so this answer is quite ok.

> seems that erros is on proxy, no?

From the logs its behaviour is at least inconsistent.

> my version of wingate is 5.0.0 (build 734)...

I'd really try updating to the current version and try again.
Product: MailNews → Core
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
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.