Project

General

Profile

Actions

Bug #443

closed

Notifications HELO uses IP rather than FQDN

Added by Oscar Francia about 14 years ago. Updated almost 14 years ago.

Status:
Resolved
Priority:
Very Low
Assignee:
-
Category:
Notifications
Target version:
Start date:
03/23/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

php: /system_advanced_notifications.php: Could not send the message to -- Error: 504 5.5.2 <192.168.1.x>: Helo command rejected: need fully-qualified hostname

Actions #1

Updated by Chris Buechler about 14 years ago

  • Subject changed from Error when trying sending notification to Notifications HELO uses IP rather than FQDN
  • Category changed from Web Interface to Notifications
  • Priority changed from Normal to Very Low

That's a problem with your mail server, it's rejecting the connection.

If we can easily send the FQDN of the system in the HELO that would be preferable.

Actions #2

Updated by Jim Pingle almost 14 years ago

Maybe this should be a toggle. Some (many?) mail servers will also reject a system's FQDN if its forward and reverse DNS entries do not match, so supplying an FQDN may hurt in other scenarios.

Actions #3

Updated by Pierre POMES almost 14 years ago

AFAIK (according to RFC) HELO should be a FQDN and should match DNS definition. So maybe we should add a new field for a custom HELO in the advanced setup pages ? By default, IP could be sent (as it is now) but if this field is used, it should be used for HELO.

Actions #4

Updated by Chris Buechler almost 14 years ago

Per RFC 821 on HELO: "The argument field contains the host name of the sender-SMTP."

Anything that rejects a hostname because of DNS or other issues is highly unlikely to accept an IP, so just changing this to FQDN is safe.

Actions #5

Updated by Pierre POMES almost 14 years ago

  • Status changed from New to Feedback

Fix commited.

Actions #6

Updated by Chris Buechler almost 14 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF