MSA Storage
1846673 Members
3120 Online
110256 Solutions
New Discussion

MSA 2040: Sending mail notifications needs correct HELO

 
SOLVED
Go to solution
Larsen0815
Occasional Advisor

MSA 2040: Sending mail notifications needs correct HELO

Hi,

unfortunately, our MSA 2040 doesn't send a HELO when connecting to our mail server:

postfix/smtpd[58746]: connect from unknown[192.168.120.27]
postfix/smtpd[58746]: NOQUEUE: reject: RCPT from unknown[192.168.120.27]: 504 5.5.2 <none>: Helo command rejected: need fully-qualified hostname; from=<msa2040@example.com> to=<jdoe@example.com> proto=ESMTP helo=<none>

This could probably (not sure, not tested) be circumvented by using port 26 which in Proxmox Mail Gateway is designed for accepting mail from internal servers. However, it's not possible to specify a port number: If I try to enter an IP with port (192.168.120.5:26) I get: 

 

Correct the errors below:
Enter an IP address (nnn.nnn.nnn.nnn)

 

How can I change any of this?

System: msa2040
Version: GL220P008

Best regards,
Lars

4 REPLIES 4

Re: MSA 2040: Sending mail notifications needs correct HELO

@Larsen0815 

Are you able to ping Email server from any of the MSA controller and vice versa ? if not then try to troubleshoot at the network layer.

At MSA end you can follow "Configuring email notification" and "To change email notification settings" sections and do the necessary changes,

https://support.hpe.com/hpesc/public/docDisplay?docId=c04220794

 

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
JonPaul
HPE Pro

Re: MSA 2040: Sending mail notifications needs correct HELO

@Larsen0815 
What are the email parameters you are currently using?
CLI> show email-parameters
I think your first problem is that you did not set a 'Domain' as it appears that your SMTP server is stating it's getting a user of 'MSA2040' and not 'MSA2040@example.com'.  The MSA uses the 'Sender' and concatenates that with the 'Domain' to come up with:  Sender@Domain
Secondly, if you need to change to a different port this is available by using the port field in the email settings rather than manually adding to the end of the SMTP server IP address.
Changes to email parameters can be done in the CLI and the SMU(WebUI)
CLI:  see  'help set email-parameters'  
SMU:  from the HOME topic, Click the ACTION button and then 'Set up Notifications', select the Email tab.



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
JonPaul
HPE Pro

Re: MSA 2040: Sending mail notifications needs correct HELO

Sorry forgot.  Please check the MSA Health Check site, www.hpe.com/storage/msahealthcheck , and update your system firmware as appropriate it looks like the running firmware is quite old.  Current firmware is: GL225P002-02



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
Larsen0815
Occasional Advisor
Solution

Re: MSA 2040: Sending mail notifications needs correct HELO

# show email-parameters
Email Parameters (SMTP)
-----------------------
Email Notification: Enabled
Email Notify Filter: warn
Email Address 1: jdoe@example.com
Email Address 2:
Email Address 3:
Log Destination:
Email Server: 192.168.120.5
Email Domain: example.com
Email Sender: msa2040
Persistent Alerts: Disabled
Include Logs: Enabled

Success: Command completed successfully. (2022-07-18 11:59:16)

There is no separate field to enter a port number. I guess it's due to the older firmware. We are only a small company that bought the SAN used and we don't have an active support contract, so no firmware download.

Proxmox proposed to use a firewall redirect from port 25 to 26 which is actually working already.

Thanks for your help, though!