Bug #443
closed
Notifications HELO uses IP rather than FQDN
0%
Description
php: /system_advanced_notifications.php: Could not send the message to mail@mail.xyz -- Error: 504 5.5.2 <192.168.1.x>: Helo command rejected: need fully-qualified hostname
Updated by Chris Buechler almost 15 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.
Updated by Jim Pingle over 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.
Updated by Pierre POMES over 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.
Updated by Chris Buechler over 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.
Updated by Chris Buechler over 14 years ago
- Status changed from Feedback to Resolved