I am testing my mail server setup, when telnetting to port 25, I receive this 
interaction when I type 'helo myserver.com'

220 *******************************************************************
helo myserver.com
502 5.5.2 Error: command not recognized

Connection to host lost.



  1.  The client I am telnetting from is in a subnet that is in mynetworks.

BUT

  1.  A different client that is in a different subnet in mynetworks connects 
to this same mail server and will get 220 <the server hostname ESMTP Postfix 
(Red Hat). The helo and other commands will work.

This postfix installation is on aws.  It is an ec2 redhat instance. And elastic 
load balancer is also configured.

The client that gets the 220 response with ********************** in the 
banner, is connecting like this:

on prem client (internal private ip)-> site to site vpn to aws -> elastic load 
balancer (internal private ip)-> ec2 instance (internal private ip)

The client that works fine has this network flow:

Ec2 server in same vpc (internal private ip) -> elb (internal private ip) -> 
ec2 instance (internal private (ip)

My current thought is that the reason the banner is 220 ********************* 
is why the client cannot sent email through this server.  Please help!

Reply via email to