After I checked all the options that the MEG offer, I only found the following way to get the MEG running with the use of the PTR name for the HELO.
We use the MEG in "Explicit Proxy" mode. At "Email | Email Configuration | Protocol Configuration | Protocol Settings (SMTP)"
you can set at the "Message processing" and "Transparency options (router and bridge mode only)" options the name that will be used for the SMTP communication. The
"Message processing" works for receiving messages but not when sending.
For sending mails only the hostname set under "System | Appliance Management | General | Basic Settings" is used for the HELO command.
Maybe someone can tell my, why the "Enforce RFC compliant EHLO / HELO" are not working/possible for the "Explicit Proxy" mode.
Is there really no other way to force the MEG in Explicit Proxy mode to use not the hostname for the EHLO?
In order to use a hostname on the EHLO part of the SMTP transaction you need to tell MEG to do so, this is done on the Virtual Hosting section (part of the System dashboard section).
Edit the Outbound Address Pool and you will find where the option can bem changed.
Hope this helps.
The ehlo response is different than the 220 banner/welcome message. If you need to modify the ehlo response, please follow the instructions in the follwong KB:
if you do not want to go through the extraction of the backup and reimport it, you can call into support and we can edit the file directly through SSH. Let me know if that clarifies things for you. Thanks.
I kept our MEG configuration simple and don't used the Virtual Hosting. I will test this options with our second appliance the next days.
@Jake, I will also test your instruction.
I got this problem solved with the KB77131 solution to edit the smtp-config.xml.
Now the appliances using the EHLO name correct.
Thank you Jake