SMTP incorrect behavior - HELO identification
Posted: Sun Jun 07, 2020 5:21 am
Can someone at Netonix explain why the switch, when running the SMTP test, connects to the remote SMTP server and identifies itself as that server?
i.e. If I have (just as an example) the HOST set to 1.1.1.1, when I run the SMTP test, the switch will connect to 1.1.1.1 and then issue a "HELO 1.1.1.1".
This is absolutely incorrect behavior. The switch should not be identifying ITSELF as the remote server in the HELO string. One of the easiest ways to cut down on spam is to drop the connection from any remote client identifying itself as the server in the HELO string.
There is a setting for "Local Hostname", but the switch is not using it. To wit, if I have "switch.example.com" set in the "Local Hostname" field, then the Netonix SHOULD issue a "HELO switch.example.com"
I'm currently running firmware 1.5.5.
If y'all need, I can provide logs and screenshots to show you what I'm talking about, but I'd rather not post them publicly.
i.e. If I have (just as an example) the HOST set to 1.1.1.1, when I run the SMTP test, the switch will connect to 1.1.1.1 and then issue a "HELO 1.1.1.1".
This is absolutely incorrect behavior. The switch should not be identifying ITSELF as the remote server in the HELO string. One of the easiest ways to cut down on spam is to drop the connection from any remote client identifying itself as the server in the HELO string.
There is a setting for "Local Hostname", but the switch is not using it. To wit, if I have "switch.example.com" set in the "Local Hostname" field, then the Netonix SHOULD issue a "HELO switch.example.com"
I'm currently running firmware 1.5.5.
If y'all need, I can provide logs and screenshots to show you what I'm talking about, but I'd rather not post them publicly.