<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why are mailserver settings in alert_actions.conf not being followed? in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Why-are-mailserver-settings-in-alert-actions-conf-not-being/m-p/353615#M6204</link>
    <description>&lt;P&gt;I have configured alert_actions.conf in $SPLUNK_HOME/etc/system/local/ but some alerts are still using “localhost” and not being received.  I have configured that there are no other alert_actions.conf besides the default ones and btool output confirms that the settings are being applied correctly.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;/opt/splunk/etc/system/local/alert_actions.conf                [email]
/opt/splunk/etc/system/local/alert_actions.conf                mailserver = testmailhost.com
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Looking in python.log I show both the new mail server and localhost being applied.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Working&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2017-06-14 15:45:02,017 -0400 INFO  sendemail:124 - Sending email.subject="Splunk Alert: Test_Alert_01", results_link="http://hostname:8000/app/search/@go?sid=scheduler__admin__search__&amp;lt;SID&amp;gt;", recipients=“[u’user@mydomain.com']", server="testmailhost.com"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Not Working&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2017-06-14 15:45:02,017 -0400 INFO  sendemail:124 - Sending email. subject="Splunk Alert: Test_Alert_02", results_link="http://hostname:8000/app/search/@go?sid=scheduler__admin__search__&amp;lt;SID&amp;gt;", recipients=“[u’user@mydomain.com']", server=“localhost”
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What could be causing this behavior?&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 14:30:15 GMT</pubDate>
    <dc:creator>jcrabb_splunk</dc:creator>
    <dc:date>2020-09-29T14:30:15Z</dc:date>
    <item>
      <title>Why are mailserver settings in alert_actions.conf not being followed?</title>
      <link>https://community.splunk.com/t5/Reporting/Why-are-mailserver-settings-in-alert-actions-conf-not-being/m-p/353615#M6204</link>
      <description>&lt;P&gt;I have configured alert_actions.conf in $SPLUNK_HOME/etc/system/local/ but some alerts are still using “localhost” and not being received.  I have configured that there are no other alert_actions.conf besides the default ones and btool output confirms that the settings are being applied correctly.  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;/opt/splunk/etc/system/local/alert_actions.conf                [email]
/opt/splunk/etc/system/local/alert_actions.conf                mailserver = testmailhost.com
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Looking in python.log I show both the new mail server and localhost being applied.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Working&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2017-06-14 15:45:02,017 -0400 INFO  sendemail:124 - Sending email.subject="Splunk Alert: Test_Alert_01", results_link="http://hostname:8000/app/search/@go?sid=scheduler__admin__search__&amp;lt;SID&amp;gt;", recipients=“[u’user@mydomain.com']", server="testmailhost.com"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;Not Working&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2017-06-14 15:45:02,017 -0400 INFO  sendemail:124 - Sending email. subject="Splunk Alert: Test_Alert_02", results_link="http://hostname:8000/app/search/@go?sid=scheduler__admin__search__&amp;lt;SID&amp;gt;", recipients=“[u’user@mydomain.com']", server=“localhost”
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;What could be causing this behavior?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:30:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Why-are-mailserver-settings-in-alert-actions-conf-not-being/m-p/353615#M6204</guid>
      <dc:creator>jcrabb_splunk</dc:creator>
      <dc:date>2020-09-29T14:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: Why are mailserver settings in alert_actions.conf not being followed?</title>
      <link>https://community.splunk.com/t5/Reporting/Why-are-mailserver-settings-in-alert-actions-conf-not-being/m-p/353616#M6205</link>
      <description>&lt;P&gt;Mailhost settings can be applied in both alert_actions.conf and savedsearches.conf.  If you have applied alert_actions.conf globally (this configuration can be applied at an app or user level) but some alerts are going to a different mail host than specific there, it could be configured under savedsearches.conf.  If you review the spec file, you will find it also has a mail server setting:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.1/Admin/Savedsearchesconf" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.1/Admin/Savedsearchesconf&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[savedsearch-name]
action.email.mailserver = &amp;lt;string&amp;gt;
* Set the address of the MTA server to be used to send the emails.
* Defaults to &amp;lt;LOCALHOST&amp;gt; (or whatever is set in alert_actions.conf).
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;As demonstrated above, this can be applied to a search and will take precedent over the setting in alert_actions.conf.  Confirm that the affected alerts do not contain this potential configuration.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:30:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Why-are-mailserver-settings-in-alert-actions-conf-not-being/m-p/353616#M6205</guid>
      <dc:creator>jcrabb_splunk</dc:creator>
      <dc:date>2020-09-29T14:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Why are mailserver settings in alert_actions.conf not being followed?</title>
      <link>https://community.splunk.com/t5/Reporting/Why-are-mailserver-settings-in-alert-actions-conf-not-being/m-p/353617#M6206</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have a similar issue. &lt;/P&gt;

&lt;P&gt;I am declaring  &lt;CODE&gt;action.email.subject = REMINDER: Cur&lt;/CODE&gt; in my savedsearches.conf in one of my apps. But when the email is getting triggered the subject isnt getting changed. Its still taking from the default alert_actions.conf file i.e. SplunkAlert-.&lt;/P&gt;

&lt;P&gt;Why my subject is not getting changed ?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jun 2018 14:15:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Why-are-mailserver-settings-in-alert-actions-conf-not-being/m-p/353617#M6206</guid>
      <dc:creator>surekhasplunk</dc:creator>
      <dc:date>2018-06-14T14:15:26Z</dc:date>
    </item>
  </channel>
</rss>

