community.general.mail callback – Sends failure events through email
Note
This callback plugin is part of the community.general collection (version 10.7.3).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.general
.
You need further requirements to be able to use this callback plugin,
see Requirements for details.
To use it in a playbook, specify: community.general.mail
.
Callback plugin
This plugin is a notification callback. It sends information for a playbook run to other applications, services, or systems. See Callback plugins for more information on callback plugins.
Synopsis
This callback will report failures through email.
Requirements
The below requirements are needed on the local controller node that executes this callback.
whitelisting in configuration
Parameters
Parameter |
Comments |
---|---|
BCC’d recipients. Configuration:
|
|
CC’d recipients. Configuration:
|
|
The domain name to use for the Message-ID header. The default is the hostname of the control node. Configuration:
|
|
Mail Transfer Agent, server that accepts SMTP. Default: Configuration:
|
|
Mail Transfer Agent Port. Port at which server SMTP. Default: Configuration:
|
|
Mail sender. This is required since community.general 6.0.0. Configuration:
|
|
Mail recipient. Default: Configuration:
|
Note
Configuration entries listed above for each entry type (Ansible variable, environment variable, and so on) have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up. The entry types are also ordered by precedence from low to high priority order. For example, an ansible.cfg entry (further up in the list) is overwritten by an Ansible variable (further down in the list).