Buildbot no longer supports Python 2.7 on the Buildbot master. MailNotifier

class buildbot.reporters.mail.MailNotifier

The Buildbot can send email when builds finish. The most common use of this is to tell developers when their change has caused the build to fail. It is also quite common to send a message to a mailing list (usually named builds or similar) about every build.

The MailNotifier reporter is used to accomplish this. You configure it by specifying who mail should be sent to, under what circumstances mail should be sent, and how to deliver the mail. It can be configured to only send out mail for certain builders, and only send messages when the build fails, or when the builder transitions from success to failure. It can also be configured to include various build logs in each message.

If a proper lookup function is configured, the message will be sent to the “interested users” list (Doing Things With Users), which includes all developers who made changes in the build. By default, however, Buildbot does not know how to construct an email addressed based on the information from the version control system. See the lookup argument, below, for more information.

You can add additional, statically-configured, recipients with the extraRecipients argument. You can also add interested users by setting the owners build property to a list of users in the scheduler constructor (Configuring Schedulers).

Each MailNotifier sends mail to a single set of recipients. To send different kinds of mail to different recipients, use multiple MailNotifiers. TODO: or subclass MailNotifier and override getRecipients()

The following simple example will send an email upon the completion of each build, to just those developers whose Changes were included in the build. The email contains a description of the Build, its results, and URLs where more information can be obtained.

from buildbot.plugins import reporters
mn = reporters.MailNotifier(fromaddr="",

To get a simple one-message-per-build (say, for a mailing list), use the following form instead. This form does not send mail to individual developers (and thus does not need the lookup= argument, explained below), instead it only ever sends mail to the extra recipients named in the arguments:

mn = reporters.MailNotifier(fromaddr="",

If your SMTP host requires authentication before it allows you to send emails, this can also be done by specifying smtpUser and smtpPassword:

mn = reporters.MailNotifier(fromaddr="",
                            relayhost="", smtpPort=587,


If for some reasons you are not able to send a notification with TLS enabled and specified user name and password, you might want to use master/contrib/ to see if it works at all.

If you want to require Transport Layer Security (TLS), then you can also set useTls:

mn = reporters.MailNotifier(fromaddr="",
                            useTls=True, relayhost="",
                            smtpPort=587, smtpUser="",


If you see twisted.mail.smtp.TLSRequiredError exceptions in the log while using TLS, this can be due either to the server not supporting TLS or to a missing PyOpenSSL package on the BuildMaster system.

In some cases it is desirable to have different information then what is provided in a standard MailNotifier message. For this purpose MailNotifier provides the argument messageFormatter (an instance of MessageFormatter) which allows for the creation of messages with unique content.

For example, if only short emails are desired (e.g., for delivery to phones):

from buildbot.plugins import reporters
mn = reporters.MailNotifier(
    messageFormatter=reporters.MessageFormatter(template="STATUS: {{ summary }}"))

Another example of a function delivering a customized html email is given below:

from buildbot.plugins import reporters

<h4>Build status: {{ summary }}</h4>
<p> Worker used: {{ workername }}</p>
{% for step in build['steps'] %}
<p> {{ step['name'] }}: {{ step['results'] }}</p>
{% endfor %}
<p><b> -- The Buildbot</b></p>

mn = reporters.MailNotifier(fromaddr="",
                                template=template, template_type='html',
                                wantProperties=True, wantSteps=True))

MailNotifier arguments


The email address to be used in the ‘From’ header.


(boolean). If True (the default), send mail to all of the Interested Users. Interested Users are authors of changes and users from the owners build property. Override MailNotifier getResponsibleUsersForBuild method to change that. If False, only send mail to the extraRecipients list.


(list of strings). A list of email addresses to which messages should be sent (in addition to the InterestedUsers list, which includes any developers who made Changes that went into this build). It is a good idea to create a small mailing list and deliver to that, then let subscribers come and go as they please.


(list) A list of instances of IReportGenerator which defines the conditions of when the messages will be sent and contents of them. See Report Generators for more information.


(string, deprecated). A string to be used as the subject line of the message. %(builder)s will be replaced with the name of the builder which provoked the message.


(list of strings or string, deprecated). Defines the cases when a message should be sent. There are two strings which can be used as shortcuts instead of the full lists.

The possible shortcuts are:


Always send mail about builds. Equivalent to (change, failing, passing, problem, warnings, exception).


Equivalent to (warnings, failing).

Set these shortcuts as actual strings in the configuration:

from buildbot.plugins import reporters
mn = reporters.MailNotifier(fromaddr="",

If the argument is list of strings, it must be a combination of:


Send mail about builds which were cancelled.


Send mail about builds which change status.


Send mail about builds which fail.


Send mail about builds which succeed.


Send mail about a build which failed when the previous build has passed.


Send mail about builds which generate warnings.


Send mail about builds which generate exceptions.

Defaults to (failing, passing, warnings).


(list of strings, deprecated). A list of builder names for which mail should be sent. Defaults to None (send mail for all builds). Use either builders or tags, but not both.


(list of strings, deprecated). A list of tag names to serve status information for. Defaults to None (all tags). Use either builders or tags, but not both.


(list of strings, deprecated). A list of scheduler names to serve status information for. Defaults to None (all schedulers).


(list of strings, deprecated). A list of branch names to serve status information for. Defaults to None (all branches).


(boolean, deprecated). If True, include all build logs as attachments to the messages. These can be quite large. This can also be set to a list of log names, to send a subset of the logs. Defaults to False.


(boolean, deprecated). If True, include the patch content if a patch was present. Patches are usually used on a Try server. Defaults to True.


(boolean, deprecated). If True, send a single summary email consisting of the concatenation of all build completion messages rather than a completion message for each build. Defaults to False.


(string, deprecated). The host to which the outbound SMTP connection should be made. Defaults to ‘localhost’


(int). The port that will be used on outbound SMTP connections. Defaults to 25.


(boolean). When this argument is True (default is False) MailNotifier requires that STARTTLS encryption is used for the connection with the relayhost. Authentication is required for STARTTLS so the arguments smtpUser and smtpPassword must also be specified.


(boolean). When this argument is True (default is False) MailNotifier connects to relayhost over an encrypted SSL/TLS connection. This configuration is typically used over port 465.


(string). The user name to use when authenticating with the relayhost. Can be a Secret.


(string). The password that will be used when authenticating with the relayhost. Can be a Secret.


(implementer of IEmailLookup). Object which provides IEmailLookup, which is responsible for mapping User names (which come from the VC system) into valid email addresses.

If the argument is not provided, the MailNotifier will attempt to build the sendToInterestedUsers from the authors of the Changes that led to the Build via User Objects. If the author of one of the Build’s Changes has an email address stored, it will added to the recipients list. With this method, owners are still added to the recipients. Note that, in the current implementation of user objects, email addresses are not stored; as a result, unless you have specifically added email addresses to the user database, this functionality is unlikely to actually send any emails.

Most of the time you can use a simple Domain instance. As a shortcut, you can pass as string: this will be treated as if you had provided Domain(str). For example, lookup='' will allow mail to be sent to all developers whose SVN usernames match their account names. See master/buildbot/reporters/ for more details.

Regardless of the setting of lookup, MailNotifier will also send mail to addresses in the extraRecipients list.


(optional, deprecated) This is an optional instance of the reporters.MessageFormatter class that can be used to generate a custom mail message.


(dictionary). A dictionary containing key/value pairs of extra headers to add to sent e-mails. Both the keys and the values may be a Interpolate instance.


This is a list of names of workers, which should be watched. In case a worker get missing, a notification is sent. The value of watchedWorkers can also be set to all (default) or None. You also need to specify email address to which the notification is sent in the worker configuration.


(optional, deprecated) This is an optional instance of the reporters.messageFormatterMissingWorker class that can be used to generate a custom mail message for missing workers.


If set to True, all completely formatted mails will be dumped to the log before being sent. This can be useful to debug problems with your mail provider. Be sure to only turn this on if you really need it, especially if you attach logs to emails. This can dump sensitive information to logs, and make them very large.