289731 - Illegal IP address in EHLO argument on SMTP connection over SOCKS

Status: RESOLVED INCOMPLETE

(MailNews Core :: Networking: SMTP, defect)

Description

[Thomas Henlich]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.6) Gecko/20050321 Firefox/1.0.2
Build Identifier: Thunderbird Version 1.0.2 (20050317)

Using PuTTY's SOCKS dynamic port forwarding to connect to a SMTP server, random
numbers appear in the EHLO argument instead of the IP address, e.g. [0.0.0.0],
[48.69.39.0], [240.59.117.4]

Reproducible: Always

Steps to Reproduce:
1. Setup dynamic port forwarding in PuTTY 0.58 (D127.0.0.1:1080)
2. Setup SOCKS host in TB prefs (host 127.0.0.1, port 1080)
3. Send a mail message

Actual Results:  
Message header shows illegal IP addresses, e.g.:

Received: from [141.XX.XX.XX] (helo=[0.0.0.0])
	  by XXXXXXXXXXXXXXXXXXXXXXXX with esmtp (exim-4.22)
	  for <XXXXXXXXXX@XXXXXXXXXXXXXXX>
	  id 1DKLsh-0006E8-Gp; Sat, 09 Apr 2005 21:44:35 +0200

Spamassassin complains about this illegal IP address.

Expected Results:  
Put valid IP address (of local interface) in EHLO command argument

Comment 1

[Gervase Markham [:gerv]]

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/

Comment 2

[Thomas Henlich]

Reproduced with Thunderbird 1.0.6 and 1.5beta1
Reproduced with PuTTY 0.58 and 2005-09-28:r6358

Comment 3

[Thomas Henlich]

(In reply to comment #2)
Reproduced with Thunderbird 1.5.0.7

Bug shouldn't be too hard to fix.
Unfortunately this bug makes the whole proxy business kind of useless for some people.

Comment 4

[David :Bienvenu]

in trunk builds, we're sending the hostname, not the ip address. Does that help?

Comment 5

[Philip Prindeville]

Just out of curiosity, does this also happen when using OpenSSH instead of Putty?

Comment 6

[Thomas Henlich]

Reproduced with:
TB 2.0.0.4
PuTTY 0.60

Bug also occurs with:
OpenSSH 3.8.1p1

Comment 7

[Thomas Henlich]

Reproduced with:
Thunderbird 3.0a1pre (2007082104)

Comment 8

[Mark Banner (:standard8)]

Please see the discussion on bug 244030, I think this bug is a duplicate of that one.

Comment 9

[Philip Prindeville]

(In reply to comment #6)
> Reproduced with:
> TB 2.0.0.4
> PuTTY 0.60
> Bug also occurs with:
> OpenSSH 3.8.1p1

Ok, next step is to gather a tcpdump/ethereal/wireshark/netmon trace on both end of the SSH connection (i.e. the clear portions of the connection, not the encrypted tunnel)... for the same connection.

Please attach these as text (not .cab or .pcap) files.

Comment 10

[Thomas Henlich]

After additional research, the problem is not specific to SSH SOCKS forwarding, but occurs with normal SOCKS too.

Reproduced with:
TB 2.0.0.14
proxymini 0.2b

Connection dumps attached
log-in.txt (Mail client <-> SOCKS proxy)
log-out.txt (SOCKS proxy <-> SMTP server)

Comment 11

[Thomas Henlich]

Attachment: Connection dump client<->SOCKS proxy

Comment 12

[Thomas Henlich]

Attachment: Connection dump SOCKS proxy<->SMTP server

Comment 13

[Thomas Henlich]

Reproduced with TB 3.0 (Shredder alpha 1)

Comment 14

[[:Aureliano Buendía]]

Thomas, you agree with comment #8: this is a dupe of (fixed) bug #244030?

Comment 15

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.