Hello,
I have recently deployed a vCenter 5.0 appliance. I set up a test alert for suspending a VM, and uppon testing, I was not getting any email alerts. I checked the connectivity to the mail server as well as sending from the mail server (internal) to my email and that worked fine. I then SSH'd into the vCenter server and checked the mail queue. I saw there was a DNS resolution issue. Also, I could not resolve anything with ping either. I checked my network settings and, duh, I didn't set up DNS settings (left IPv6 as DHCP, not SLAAC). So, I changed that and then resolution via ping was working properly. I then cleared the mail queue and reactivated the alarm. I checked the mail queue and it gave a Deferred: 450 4.1.8 which means domain of recipient does not resolve. What could be causing this issue?
Just a quick guess, I don't know if that applies:
Do you have a mx record for your mail domain?
AWo
Yes I do. I also tested with a gmail account to rule out any DNS issues for our domain.
You're talking about mails send from within the (which) appliance?
AWo
The vCenter Server appliance.
You have configured the mail settings in the vCenter settings?
If yes, go to the vCenter server and try to open a connection to the designated mail host:
telnet <FQDN of mail host> 25
Do you get a reply?
AWo
I have configured the email settings in vCenter.
Unfortunately with the appliance, it seems as though there is no telnet client installed.
EDIT:
I added a Suse repo and installed a telnet client and I do get the appropriate 220 response when you telnet to the email server on port 25.
For now...
AWo
Does the email host accept SMTP mails from the sending domain (what's behind the @). If it is not configured as an open relay the sending domain must be listed there.
AWo
It seems like it is being blocked because the dnsdomainname is mydomain.local. Any mail server will reject this. How can I change that to mydomain.com.