I've noticed that the email-ext plugin will not send out notifications to emails beginning with a '#', even though the job console states that it is doing so. For example:
Build step 'Execute shell' marked build as failure Discard old builds... Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Sending email to: #jenkin...@company.com Finished: FAILURE
The email-ext plugin is fine if the email does not being with a '#'.
I've noticed that the email-ext plugin will not send out notifications to emails beginning with a '#', even though the job console states that it is doing so. For example:
{quote}Build step 'Execute shell' marked build as failure
Discard old builds... Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Sending email to: #jenkin...@company.com Finished: FAILURE
{quote} The email-ext plugin is fine if the email does not being begin with a '#'.
If it says sending then it at least tried to send to that address. Have you checked your mail servers logs to see what happened to it? Chances are it was either spammed or sender restrictions on the destination address dropped it.
The mail server I'm using is administered by my organisation's IT department. Emails to names in the same domain without the hash are delivered successfully, so why those beginning with a hash are being handled differently is a mystery. I'll contact our IT dept. to take a look at the server logs.