Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Emails are not sent from vCenter Server Appliance 6.5 or 6.7 after an Alert/Event is triggered. (54375)

Last Updated: 2/17/2023Categories: TroubleshootingTotal Views: 64125Language:
Chinese (Simplified)JapaneseEnglish

31 like this article

Subscribe to get an email
newsletter with new updates

31 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Alert/Event is triggered but action mail is not being sent from vCenter Server Appliance 6.5.

In /var/log/vmware/messages, you see entries similar to

sendmail[24224]: w0VHA0uD024224: from=[email-masked], size=548, class=0, nrcpts=1, msgid=<[email-masked]>, relay=root@localhost
sendmail[24224]: w0VHA0uD024224: to=[email-masked], delay=00:01:05, mailer=esmtp, pri=30548, dsn=4.4.3, stat=queued

sendmail[918]: w2M2CHDc000918: from=xxx.com, size=516, class=0, nrcpts=1, msgid=<xx.domain.com>, relay=root@localhost

sendmail[920]: w2M2CHqc000920: ruleset=check_mail, arg1=<[email-masked]>, relay=photon-machine [127.0.0.1], reject=451 4.1.8 Domain of sender address [email-masked] does not resolve
sendmail[918]: w2M2CHDc000918: to=[email-masked], [email-masked] (0/0), delay=00:01:07, xdelay=00:01:07, mailer=relay, pri=30516, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: 451 4.1.8 Domain of sender address [email-masked] does not resolve

Cause

This issue occurs when sendmail is failing to resolve the configured recipients domain or if the relay host is rejecting the senders email address (root@localhost).

Resolution

To resolve the issue follow the below steps:

Note1: Prior to applying resolution ensure you take a offline backup or snapshot of the vCenter Server Appliance.
Note2: The applied configuration change may be lost after upgrade. In such case, Please apply the steps again.

1. Connect to vCenter Server Appliance via ssh.
2. Edit sendmail.service using the vi editor.

vi /etc/systemd/system/sendmail.service

In recent releases, the file may be at different directory.

Case you do not find the sendmail.service under /etc/systemd/system, check the path beneath:

/lib/systemd/system/sendmail.service

3. Alter the After entry under [Unit] section to be as follows:

[Unit]
:
After=syslog.target network.target systemd-resolved.service

4. Save the changes and close the editor.
5. Open sendmail.mc using vi editor:

/etc/mail/sendmail.mc

6. Add following entry after OSTYPE:

FEATURE(`nocanonify')dnl
define(`SMART_HOST', `[Your_mail_host]')dnl

Note: change Your_mail_host to reflect the correct mail server hostname.

7. Save the change and close the editor.
8. Next, edit submit.mc using the vi editor.

vi /etc/mail/submit.mc

9. Add the following line at the end of the define entries:

define(`confDIRECT_SUBMISSION_MODIFIERS', `C')dnl

10. Save the change and close the editor.
11. Verify that local hostname is present and is resolvable in hosts file.

/etc/hosts

12. Execute following command and generate new .cf file

cd /etc/mail
m4 m4/cf.m4 sendmail.mc > sendmail.cf
m4 m4/cf.m4 submit.mc > submit.cf

13. Reload system daemon and restart sendmail.

systemctl daemon-reload
systemctl restart sendmail

At this point, the vCenter should be able to send emails to the mail server; however, the emails will be sent as root@localhost. Validate it by sending a test alarm and checking the messages log under /var/log/vmware/.

Once validated:

Make a backup copy of the submit.cf file

Submit.cf is a read-only file. The permissions on this file must first be changed with this command:

chmod 644 /etc/mail/submit.cf

 Edit submit.cf with the vi editor

vi /etc/mail/submit.cf

After the "DS", enter the FQDN of the mail server

Save the file

Change the file's permission back to the original permissions:

chmod 444 /etc/mail/submit.cf

For example, if the mail server FQDN is: mailserver.xyzdomain.com

​# "Smart" relay host (may be null or contain IP address)
DS [mailserver.xyzdomain.com]

Restart sendmail daemon using systemd.

systemctl restart sendmail

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server 8.0.x

VMware vCenter Server 7.0.x

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant