There seems to be a bug in vSphere 6.7 that whenever you update you vCenter appliance, that the e-mail notifications from vCenter no longer works. You had previously set-up alarm definitions that sent an e-mail to a recipient when the alarm is triggered, but you don’t receive the e-mail message. There are no error messages in vCenter, you just don’t receive any mail alerts anymore.

You can correct this by temporary editing the SMTP server entry in vCenter and then edit the entry again to the original SMTP server.

vCenter SMTP settings

Detailed instructions:

  • Log on to the HTML-5 Web Client or the Flex client
  • Select your vCenter instance then browse to Configure – Settings -General
  • Under vCenter Server Settings you will see your configured mail configuration
  • Choose Edit (at the right top of the screen) and select Mail in the Edit vCenter general settings
  • Edit your Mail server to something different, doens’t matter that it doesn’t exist, just as long as the current entry get modified.
  • Click Save and repeat the same and now re-enter your original mail server configuration
  • After that, e-mails should be working again.
  • This issue could also be existing on vCenter 6.5, I’m not sure.
Edit vCenter general settings
  1. Thank you for sharing the info, Marco !
    I was trying to find a reason during last 2 weeks, but never may thought that so primitive bug could exist in such a serious product..

  2. Hi! I could have sworn I’ve visited this website before but after looking at a few of the posts I
    realized it’s new to me. Nonetheless, I’m definitely happy
    I came across it and I’ll be bookmarking it and checking back

  3. I just migrated to the VCSA 6.7u3, but it was not sending emails. The setting you reference was/is correct, however, when I go to change the from address (as a test) it will not let me save. “Operation failed! A specified parameter is not correct.” Any ideas?

  4. I am not sure if my upgrade to 6.7 U3 from 6.0 broke it or if the subsequent Patch to U3f broke it? Anyone know?

  5. Good find! I already wasted enough time tracking this down. I am not sure if the upgrade to 6.7 U3 broke it or if the subsequent patch to U3g may have broke it. Any ideas?

Leave a Reply

Your email address will not be published.