On 11/11/2015 01:23 AM, Eric Broch wrote:
Hi Jim,
A client of mine had an issue where it was the ISP that was causing
the "220***" banner...something you might
consider.
EricB
This is known to happen with Cisco Pix firewalls. The fixup smtp code
they implement
I need to correct a typo i had to ReMove the smtp fixup for 25
so i do a
*no* fixup protocol smtp 25
and a write mem
and -- now good
This could also be seen if I telenet to my server Inside my firewall i
get the banner as expected but outside i got
"220***"
