Customer-configured Email-based alerting is a first-class workflow supported by Splunk. We know how vital alerting can be to our customers. To help ensure that you continue receiving any configured email-based alerts from your stacks, please take a moment to review a summary of changes being introduced.
Splunk Cloud Platform is enhancing its outbound email delivery capabilities to provide a more robust, multi-region email delivery service with increased limits on the email payload size.
(Splunk will notify our customers the changes prior to the rollout by cohort by email)
Change |
Description |
Customer Impact |
Custom MAIL FROM |
Standard stacks: The MAIL FROM value in the SMTP envelope of emails originating from Splunk Cloud Platform and SOAR stacks will change from pm.mtasv.net to mail.splunkcloud.com. Emails will continue having the From field set to alerts@splunkcloud.com FedRAMP Moderate stacks: MAIL FROM value in the SMTP envelope of emails originating from Splunk Cloud stacks will change from pm.mtasv.net to mail.splunkcloudgc.com. Emails will continue having the From field set to alerts@splunkcloudgc.com |
No downtime expected. If you need clarification on any existing network policies at your end, please contact Customer Support so we may work with you to help ensure that you continue receiving email-based alerts. |
Dynamic IP addresses for origin mail server |
The origin email server is expected to have a dynamic IP address range in the future compared to the current state of a well-known IP address range. |
Enhancement |
Description |
Customer Impact |
Multi-region Support |
Email originating from customer stacks will now be routed via servers that are region-local to customer stack. |
None. No action required. |
Email size |
Email size, including body/text/images/ attachments, will be increased from 10MB to 40MB. |
None. No action required. |
We are also excited to let you in on some of our future roadmap initiatives following this change:
There have been cases where domains/email addresses have been reported as erroneously blocked resulting in undelivered emails for customers. With the eventual goal of self-service, we will start automating remediation workflows for email suppression use cases.
Customers are currently able to send an email notification for alerts to multiple customer-configured recipients not exceeding a count of 50 (Sum of the number of recipients in To, CC, BCC fields). We will allow this number to be adjusted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.