iLO Amplifier fails to send E-Mails due to SMTP EHLO

[SCORELab]

Hi all

[This is similar to other issues regarding Email in this forum, but I think I've found a root cause for our environment]

Our iLO Amplifier Pack 2.16 does not send E-Mails.

I tracked it down (via tcpdump) that iLO Amplifier does NOT use a fqdn for EHLO during SMTP, which our SMTP server reject.s Dear @HPE, how can I convince the iAP to actually use an FQDN for EHLO?

Best regards

  -Tobias

[support_s]

System recommended content:

1. iLO Amplifier Pack 1.60 User Guide

2. iLO Amplifier Pack 2.16 Release Notes

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[SCORELab]

Hi.

Thanks for these considerations.

Neither document contains relevant information to my post.

Moreover, the release notes state:

NOTE: For any product feedback, send an email to iloamplifiersupport@hpe.com.
For any product queries or issues, refer to our support channels

• The email address bounces with "550 5.1.1 User Unknown"
• I've tried numerous support channels, and  nobody seems to be in charge.

This is a bit frustrating.

[Mamatha_J]

Hello,

Depending on your network environment, SMTP server may be reachable only through a proxy. Ensure that you have specified the proxy. If the SMTP server is local to your network environment and a proxy is specified, ensure that the Bypass Proxy is enabled and the SMTP server is specified in the Bypass Proxy list.

Ensure that you have MS Exchange or GMAIL configured as your mail server.

For more information please refer to the mentioned guide

iLO Amplifier Pack 2.16 User Guide

Thanks!

I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

[SCORELab]

Dear @Mamatha_J 

Thanks for your consideration.

I have a very good Idea how our E-Mail setup has to look like.

The thing is: Our local Email Server REQUIRES an FQDN during SMTP EHLO, otherwise rejects email. This is not configurable.

iLO Amplifier under no cirumstances uses the hosts FQDN but ALWAYS the nodes short hostname.

So when I configute the amplifier as iap.example.com, it sends to the Mailserver:

EHLO iap

when it should send

EHLO iap.example.com

I have verified that via network package inspection.

The guide is of no help in this circumstance.

[Mamatha_J]

Greetings of the day!

My apologies, 

Please check the naming convention of the downloaded amplifier pack if it is named in a short form this problem may come into the picture. 

For further assistance please reach out to HPE Support Portal for more information,  support.hpe.com

[SCORELab]

Hi

What do you mean by "naming convention".

The iAP has an fqdn, yes, but does not use it in SMTP.

You said:  "For further assistance please reach out to HPE Support Portal for more information,  support.hpe.com".
Where exactly? I know the docs, they don't help here. I cannot open a case. How would the portal help?

[SCORELab]

Hi all

Per private message i was informed that a Case 5370515674 was created for me, but I cannot access that.

What to do?

Best regards

  -Tobias

[techin]

AFAIK, these are free cases and not tied to the serial numbers of your product because serial number is confidential information and cannot be shared in public forums. Thats why they do not show up in support center. So if the issue requires proper log analysis then you need to call technical support and create a case. That case will show up there. This was what was explained to me. 

[SCORELab]

Hi

thanks for sharing that info. Do you know what i can do with that case then? Why do they tell me the case number/creation if I cannot look at it anyways...

anyway, I'll probably have to wait.

[Mamatha_J]

Hello, 

This will require further analysis, so we would recommend logging a support ticket using the following links so that the support team can assist you further:
https://www.hpe.com/psnow/doc/A00039121ENW

https://support.hpe.com/hpesc/public/docDisplay?docId=cep-help_en_us&page=index.html

[Hariom]

Hi Tobias

Could you please share the details of SMTP mail server? There was an advisory published on supported mail servers, find the link for your reference:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00118000en_us

If mail server listed in compatible list is working fine & does not expect FQDN in EHLO/HELO then through support case request an enhancement request can be made. 

Regards

Hariom

[SCORELab]

Hi Mamatha_J.

I tried filing an issue but I was stuck. Maybe I have luck on the next try.

Hi Hariom

The server is a rechent Exchange Server. I have no control over it but have to use it.

It is listed as compatible.

[SCORELab]

Hi all

Has anybody a hint how to proceed here?

[Hariom]

Hi Tobias

I am not sure if this is being investigated through a HPE support ticket.  I was just going through SMTP RFC 2821 (Section : 4.1.1.1) which reads as below:

4.1.1.1  Extended HELLO (EHLO) or HELLO (HELO)

   These commands are used to identify the SMTP client to the SMTP
   server.  The argument field contains the fully-qualified domain name
   of the SMTP client if one is available.  In situations in which the
   SMTP client system does not have a meaningful domain name (e.g., when
   its address is dynamically allocated and no reverse mapping record is
   available), the client SHOULD send an address literal 

https://www.ietf.org/rfc/rfc2821.txt

This sounds no *must* requirement in the argument field to have FQDN. In the absense of FQDN, SMTP server should also accept address literal. 

Also please verify that port 25/587 are no where blocked in the firewall during EHLO/HELO.

https://learn.microsoft.com/en-us/exchange/plan-and-deploy/deployment-ref/network-ports?view=exchserver-2019

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

My recommendation would be to have this investigated through a support request so that we look back into traces, iLO AP logs, & get this reviewed through Product support teams.

Regards

Hariom

[SCORELab]

[edit: replied to wrong person]

[SCORELab]

Hi Hariom

I was told via PM that there is a ticket, bu I cannot access it:

Query Id: #26936 Case Created
This is to inform you that HPE Support case 5370515674 has been created and an HPE Support representative will assist you further to resolve your issue/query.

I may be true that the RFC does not Require EHLO with FQDN. But Microsoft Exchange in most configurations *does*. And your iAP documentation states that Exchange is supported...

Firewall is not the problem, if necessary I have a TCPDUMP capture for the interaction between iAP and Exchange.

What do you all need to get this moving?