The MailLogger captures all output logged through DefaultLogger (standard Phing output) and will send success and failure messages to unique e-mail lists, with control for turning off success or failure messages individually.
Table I.1: Properties controlling the operation of MailLogger:
| Property | Description | Required |
|---|---|---|
phing.log.mail.from
| Mail "from" address | Yes, if mail needs to be sent |
phing.log.mail.replyto
| Mail "replyto" address(es), comma-separated | No |
phing.log.mail.properties.file
| Filename of properties file that will override other values. | No |
phing.log.mail.success.cc
| Address to send success messages to carbon copy (cc) | No |
phing.log.mail.failure.cc
| Address to send failure messages to carbon copy (cc) | No |
phing.log.mail.success.bcc
| Address to send success messages to blind carbon copy (bcc) | No |
phing.log.mail.failure.bcc
| Address to send failure messages to blind carbon copy (bcc) | No |
phing.log.mail.success.body
| fixed text of mail body for a successful build, default is to send the logfile | No |
phing.log.mail.failure.body
| fixed text of mail body for a failed build, default is to send the logfile | No |
phing.log.mail.success.subject
| Subject of successful build | No - default to Build Success |
phing.log.mail.failure.subject
| Subject of failed build | No - default to Build Failure |
phing.log.mail.success.to
| Address to send success messages to | required if success mail to be sent |
phing.log.mail.failure.to
| Address to send failure messages to | required if failure mail to be sent |
phing.log.mail.success.notify
| Send build success e-mails? | No - default to true |
phing.log.mail.failure.notify
| Send build failure e-mails? | No - default to true |
phing -logger "Phing\Listener\MailLogger"