Config Files: tagmail.conf

This version is out of date. For current versions, see Puppet packages and versions.

The tagmail.conf file configures the optional tagmail report processor.

Note: If you use Puppet Server and want to enable and configure the tagmail report processor, install and use the puppetlabs/tagmail module. The built-in tagmail report processor has a known issue with Puppet Server and was removed in open source Puppet 4.0 and Puppet Enterprise 3.8.

What is the Tagmail Report Processor?

Puppet agent nodes can be configured to send reports to a Puppet master server. The master will then use its configured report processors to handle those reports.

The tagmail report processor sends targeted emails to different admin users whenever certain resources are changed.

Enabling Tagmail

To enable tagmail, you must:

  • Enable reporting: On agent nodes (and Puppet apply nodes), set report = true.
  • Enable the tagmail processor: On Puppet masters (and Puppet apply nodes), set reports = tagmail.
  • Configure email: On Puppet masters (and Puppet apply nodes), set the reportfrom email address and a value for either smtpserver or sendmail.
  • Configure tags: On Puppet masters (and Puppet apply nodes), create a tagmail.conf file at the location specified in the tagmap setting.

The tagmail.conf File


The tagmail.conf file is located at $confdir/tagmail.conf by default. Its location is configurable with the tagmap setting.

The location of the confdir varies; it depends on the OS, Puppet distribution, and user account. See the confdir documentation for details.


webserver, !mailserver:
emerg, crit:,,

This tagmail.conf file will mail any resource events tagged with webserver but not with mailserver to the httpadmins group; any emergency or critical events to to James, Zach, and Ben, and all events to the log-archive group.


The tagmail.conf file is series of lines. Each line should consists of:

  • A comma-separated list of tags and !negated tags; valid tags include:
    • Explicit tags
    • Class names
    • all”, which is a special value matching all events
    • Any valid Puppet log level (debug, info, notice, warning, err, alert, emerg, crit, or verbose)
  • A colon
  • A comma-separated list of email addresses

The list of tags on a line defines the set of resources whose messages will be included in the mailing; each additional tag adds to the set, and each !negated tag subtracts from the set.

See an issue? Please file a JIRA ticket in our [DOCUMENTATION] project
Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.