Alerting

Alert not sending email

terryloar
Path Finder
  • I copied alert_actions.conf [email] stanza from .../default to .../local directory as alert_actions.conf

  • I set up an alert to fire on the hour + 30. It does this successfully, however the email does not get sent.

  • When I created the alert the mailserver = was successfully changed in the alert_actions.conf

  • To make sure that the email could be sent, I successfully did a telnet 25 and sent an email from splunk@ to the recipient.

  • I noticed that after the alert fires, this entry changed in the alert_actions.conf file, even though I opted for no authentication:
    auth_password =
    auth_password = $1$0A==

  • python.log entry:

2014-03-27 11:30:03,019 Central Daylight Time ERROR sendemail:357 - Sending email. subject="Splunk Alert: Load Avg > 2",

results_link="http://WKGSSSPLKAPCP01:8000/app/capacity/@go?sid=scheduler__admin__capacity__RMD5264977cbcc6fb61e_at...",
(this worked from a browser)

recipients="['my valid email address']"

Tags (2)
0 Karma

terryloar
Path Finder

Solved. The problem was in the documentation stating that the sender could be just 'splunk' and the system would add the domain. Not so, and there are two places where you have to define the sender and it needs to be a full splunk@

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...