Looking for an email notification solution

%3CLINGO-SUB%20id%3D%22lingo-sub-1729071%22%20slang%3D%22en-US%22%3ELooking%20for%20an%20email%20notification%20solution%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1729071%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EOur%20company%20uses%20Office%20365%20for%20their%20email%20product.%20I%20want%20to%20send%20an%20email%20notification%20from%20Jenkins%20if%20a%20build%20fails.%20We%20use%20an%20API%20to%20send%20jobs%2C%20so%20the%20user(s)%20are%20not%20seeing%20the%20actual%20job.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EThe%20problem%20is%20the%20users%20want%20these%20emails%20sent%20to%20(preferably)%20a%20Slack%20channel%2C%20or%20(not%20as%20preferable)%20an%20MS%20Teams%20channel.%20Both%20of%20the%20email%20addresses%20for%20these%20channels%20end%20in%20a%20non-corporate%20domain%20name.%20While%20we%20can%20send%20email%20from%20our%20email%20to%20those%20addresses%2C%20Jenkins%20is%20configured%2C%20for%20security%20reasons%2C%20to%20not%20be%20able%20to%20send%20email%20to%20anything%20that%20does%20not%20end%20in%20a%20corporate%20domain.%20%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3ENo%2C%20it%20is%20not%20possible%2C%20under%20corporate%20policy%20to%20change%20the%20Jenkins%20behavior%2C%20so%20we%20need%20a%20work%20around%20solution%20to%20this.%20Thanks%20for%20any%20input.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1729071%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1738903%22%20slang%3D%22en-US%22%3ERe%3A%20Looking%20for%20an%20email%20notification%20solution%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1738903%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F597966%22%20target%3D%22_blank%22%3E%40JimBob%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eone%20solution%20that%20comes%20to%20my%20mind%20is%20to%20work%20with%20redirections%20from%20corporate%20e-mail%20addresses%3A%3C%2FP%3E%3CP%3E-%20create%20shared%20mailboxes%20in%20Exchange%20Online%20with%20a%20corporate%20email%20address%20(do%20not%20require%20a%20license)%3C%2FP%3E%3CP%3E-%20create%20an%20inbox%20rule%20for%20each%20shared%20mailbox%20which%20redirects%20incoming%20mails%20to%20the%20respective%20Slack%20channel%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Our company uses Office 365 for their email product. I want to send an email notification from Jenkins if a build fails. We use an API to send jobs, so the user(s) are not seeing the actual job.

The problem is the users want these emails sent to (preferably) a Slack channel, or (not as preferable) an MS Teams channel. Both of the email addresses for these channels end in a non-corporate domain name. While we can send email from our email to those addresses, Jenkins is configured, for security reasons, to not be able to send email to anything that does not end in a corporate domain.

No, it is not possible, under corporate policy to change the Jenkins behavior, so we need a work around solution to this. Thanks for any input.

1 Reply
Highlighted

Hi @JimBob ,

 

one solution that comes to my mind is to work with redirections from corporate e-mail addresses:

- create shared mailboxes in Exchange Online with a corporate email address (do not require a license)

- create an inbox rule for each shared mailbox which redirects incoming mails to the respective Slack channel