Iamshankha/email bounce alert system #1953
Merged
+83
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Email Bounce Alert Script Purpose: This mail script detects bounced-back emails in the Junk module and identifies recipient addresses from the email body. When a bounce is detected, it automatically triggers a notification containing the affected email IDs and a link to the email record. Type: Email Script Trigger: Notification
📧 Email Bounce Alert System 📘 Overview The Email Bounce Alert System automatically detects bounced-back emails in the Junk Mail module and alerts administrators or support teams about affected recipients. It helps identify communication failures quickly and ensures that important client messages aren’t missed due to IP blacklisting or delivery issues. 🧩 Problem Statement In large organizations, emails sometimes bounce back because of mail server issues, blacklisted IPs, or invalid addresses. Currently, identifying which users didn’t receive an important message requires manual checking of the Junk Email module, leading to delays in response and potential loss of critical communication. 💡 Solution This email script automates the detection and notification process. The email script is called from a Notification configured on the sys_email table. Email Script: Extracts affected recipient email addresses from the email body using RegEx pattern matching. Generates an automatic notification alert listing all affected users. Provides a direct link to the bounced email record for quick investigation. Notification settings: When to send: Record inserted or updated Inserted checkbox: Marked Condition: Mailbox is Junk AND Body is not empty Proper recipient(s) and subject line set in the notification. 🚀 Benefits ⚡ Immediate visibility of bounced or undelivered emails. 🧠 Automated extraction of recipient information — no manual tracking required. 📩 Faster communication recovery, ensuring critical business messages reach the intended audience. 🔗 Direct record access for faster troubleshooting and action.
Contributor
|
Looks good to me. Thank you for the contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description:
replace this with your description
Pull Request Checklist
Overview
Code Quality
Repository Structure Compliance
Core ServiceNow APIs/Server-Side Components/Client-Side Components/Modern Development/Integration/Specialized Areas/Documentation
Restrictions