E-Mail Notification SPAM since 23.01
-
@steveits said in E-Mail Notification SPAM since 23.01:
@yanakis 1) is it flapping?
2) install/update the System Patches package and install patch
Fix SMTP notification loop / config.cache write failures (Redmine #14031, Redmine #14061)1 - meaning?
2 - no new packages available
Fix SMTP notification loop / config.cache write failures (Redmine #14031, Redmine #14061) - I am not that advanced :)Seems to happen every night, I got more than 1000 messages
Thanks!
-
@yanakis said in E-Mail Notification SPAM since 23.01:
no new packages available
You already have an old version of the System Patches package installed?
-
@yanakis flapping meaning, is it actually going up and down? Or is this the same alert being resent repeatedly (the bug).
Re: 2, I meant, install that patch using that package.
-
@steveits said in E-Mail Notification SPAM since 23.01:
@yanakis flapping meaning, is it actually going up and down? Or is this the same alert being resent repeatedly (the bug).
Re: 2, I meant, install that patch using that package.
No, is the same alert repeated although I disabled smtp notifications
I just applied the patch. let's see what happens over night. -
@yanakis You have to install the System Patches package I linked above, then go to System/Patches
-
@steveits said in E-Mail Notification SPAM since 23.01:
@yanakis You have to install the System Patches package I linked above, then go to System/Patches
I did but overnight happened again? does it need a restart?
-
You :
... disabled smtp notifications
and installed the patch.
Still, you receive mails from pfSense ?
-
@gertjan I renabled SMTP notifications after the patch
-
@yanakis and just to be clear your system logs show only one WAN drop?
-
@steveits said in E-Mail Notification SPAM since 23.01:
@yanakis and just to be clear your system logs show only one WAN drop?
no WAN drop, just thousands of emails containing the same text:
0:49:00 MONITOR: GSM_DHCP has packet loss, omitting from routing group Failover
1.1.1.1|192.168.8.107|GSM_DHCP|50.998ms|0ms|50%|down|highloss
0:49:01 MONITOR: GSM_DHCP is available now, adding to routing group Failover
1.1.1.1|192.168.8.107|GSM_DHCP|46.107ms|2.507ms|0.0%|online|none
18:04:22 MONITOR: WAN_PPPOE has packet loss, omitting from routing group Failover
8.8.8.8|86.122.163.2|WAN_PPPOE|16.069ms|11.825ms|24%|down|highloss
18:06:07 MONITOR: WAN_PPPOE is available now, adding to routing group Failover
8.8.8.8|86.122.163.2|WAN_PPPOE|14.924ms|2.202ms|4%|online|none
18:06:32 MONITOR: WAN_PPPOE has packet loss, omitting from routing group Failover
8.8.8.8|86.122.163.2|WAN_PPPOE|14.82ms|0.573ms|23%|down|highloss
18:07:56 MONITOR: WAN_PPPOE is available now, adding to routing group Failover
8.8.8.8|86.122.163.2|WAN_PPPOE|16.51ms|13.409ms|10%|online|none -
@yanakis I'd expect 00:49 and 18:04 to be separate email alerts...
You can change monitoring thresholds, monitoring IPs, or even disable monitoring in the System/Routing page if you want to assume they are always up.
-
@yanakis said in E-Mail Notification SPAM since 23.01:
MONITOR: GSM_DHCP
That's the typical WAN type interface that fluctuates.
I friend of my doesn't have ADSL or fiber as he lives to far out in the middle of now where.
He tried all type of satalite access (not yet startlink) and now uses a 4G modem/router.
It's pretty good, but bandwidth isn't stable at all. It's a 0 to 50 Mbit/sec dance all day long.Btw : dpinger monitoring can mail ? I learned something.
-
Does
/var/db/notifyqueue.messagescontain any content right now? If so,rm /var/db/notifyqueue.messagesand see if it happens again. -
@jimp it seems it neeeded a restart after I applied the suggested patches. It just stopped the next day. I will keep an eye on it.
