I don't know if the submitter's claim is the right thing or not, but we should find out what the standard is, and what other clients do. --- Subject: - Mac OS (8.1) - improper use of HELO protocol Resent-Date: Tue, 30 Mar 1999 14:39:00 -0800 (PST) Resent-From: security-flaw@netscape.com Date: Tue, 30 Mar 1999 14:36:21 -0800 From: jdl@cais.com To: security-flaw@netscape.com Submitter name: Jonathan Loo Submitter email address: jdl@cais.com Acknowledgement checkbox: on Product: Communicator 4.x Operating system: Mac OS OS version: 8.1 Issue summary: improper use of HELO protocol Issue details: When sending outgoing e-mail from the Macintosh version of Netscape 4.07, Netscape uses the hostname from the return address when issuing the HELO command to the SMTP server. However, in many cases, the hostname from the return address is not the same as the name of the user's computer. The hostname in the HELO command should reflect the name or IP address of the user client. I would suggest that Netscape behave the same way as Microsoft Outlook Express: Netscape should send the user's IP address in the HELO command, instead of the host name from the user's computer. I believe that Microsoft Outlook Express includes the IP address in square brackets. Additional computer info: Open Transport.

M8

triaging to m10.

Moving all Mail/News Networking bugs to Mail/News Networking-Mail This may re-open previously Verified bugs due to a Bugzilla bug...if so, I will fix those bugs.

Triaging to post beta 1. Not being a mac expert, does anyone know how to get the ip address from the mac?

Triage to M16 since 4.x worked this way. I bet Paul knows how to get the IP address

Mass moving M16 to M17 - look for nsbeta2 before anything else.

moving to future milestone.

adding john to the cc list.

Um, if you want some help with this I can show you a nice packet grabber for the Mac that would let you see exactly what other apps are doing in this instance. And this isn't exactly a must have fix but futured Mac bugs are a pet peeve of mine :-)

I see this same thing on a Linux build, so it doesn't seem to be Mac specific, and also this bug looks identical to bug 68877, which has more information about the problem, the RFC that defines EHLO/HELO, and possible fixes.

*** This bug has been marked as a duplicate of 68877 ***

v