public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: CU198 Testing - first feedback on Suricata alert email sending
Date: Mon, 29 Sep 2025 16:44:44 +0100	[thread overview]
Message-ID: <C86FE248-C3E0-4C0C-A599-50E7956A4305@ipfire.org> (raw)
In-Reply-To: <82147ae8-47c7-4556-885e-f7c18d335f51@ipfire.org>

Hello,

Thanks for testing this. So let’s go through this step by step…

First of all, is the companion daemon running? It is a process called suricata-reporter.

If so, can you check if the configuration file has emails enabled? It is in /var/ipfire/suricata/reporter.conf.

And finally, can you run “mailq” to see if the emails have been sent and maybe have bounced?

-Michael

> On 29 Sep 2025, at 13:58, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Forgot to mention, I pressed the test button on the Mail Service WUI page and immediately received the test mail message.
> 
> I use a mail server I have running on my local network.
> 
> Regards,
> 
> Adolf.
> 
> 
> On 29/09/2025 14:52, Adolf Belka wrote:
>> Hi All,
>> I just ran the update for CU198 Testing on my vm systems.
>> The update itself went fine without any error messages or hiccups.
>> I then went to test the IPS emailing of alerts.
>> I used the same sender and recipient email addresses as I have specified on the Mail Service WUI page.
>> I set the alert severity to All, Including Informational Alerts.
>> I then followed the suricata testing process as defined in
>> https://docs.suricata.io/en/suricata-8.0.1/quickstart.html#alerting
>> and I ended up with alerts in the IPS-Logs but no email message received.
>> I checked the System logs for the mail system and there was no message trying to be sent. I ran the test 7 times, so ended up with 7 messages in the IPS-Logs.
>> I then checked the IPS system Logs and there was no mention of detecting the alerts and trying to send an email.
>> I ran the command tail -f /var/log/messages so I could see any additional log entries when I triggered the IPS alerts but again nothing was shown when I triggered the alerts, although the messages did end up in the IPS Logs section.
>> Regards,
>> Adolf.
> 
> 



  reply	other threads:[~2025-09-29 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 12:52 Adolf Belka
2025-09-29 12:58 ` Adolf Belka
2025-09-29 15:44   ` Michael Tremer [this message]
2025-09-29 16:10     ` Adolf Belka
2025-09-29 16:37       ` Adolf Belka
2025-09-29 16:50         ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C86FE248-C3E0-4C0C-A599-50E7956A4305@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox