Is there some way within callhome, globally, or in the VRF context to enable/disable how the Smart Callhome client devices choose to initate the "HELO" I have two different clients. Both are having callhome setup issues around "whitelisting" the Callhome equipment on the SMTP server. We have setup the whitelist corretly and I can initate a telnet client from the respective devices (nexus 5k and C3560's) with success. During this testing I have discovered that the C3560's send HELO messages as the FQND and the Nexus 5k's and UCS FI's send the HELO messages as hostname. Typical SMTP dialog #1 client connects to mail server #2 mail server sends back a 220- #3 client sends hello message with it's domain name or FQDN. I have discovered that the IOS based systems differ from the NXOS systems C3560 systems sends "HELO hostname.domain.name" Nexus systems sends "HELO hostname" #4 dialog continues with MAIL FROM:me@hostname.... (what ever you put in transport email from field) #5 dialog continues on with RCPT TO: firstname.lastname@example.org (whae ever you put in the destination-profile email-addr" Issue is this one client Whitelist is instistant on using FQDN during hello. the other is insittant on using Hostname only. What I end up with is the lack of completing relay on 50% of the equipment in each scenario. A nice feature might be inside of the callhome transport section to have a command like this "transport email helo-string fqdn|hostname" or "transport email helo-string WORD"
... View more