Tracking Center not showing all received emails

[Peter Nielsen]

Hi

I have noticed that email are not alway shown in the tracking center, even though email actually are comming through.
In the screenshot below there is a gap of 1½ where mail are not shown (no filters have been applied). I rebooted the pmg server around 9:40 and then mails started appearing again.

Any suggestions?




/Peter Nielsen

 

[Stoiko Ivanov]

PMG's Tracking Center fetches it's data from the syslog files (/var/log/syslog, /var/log/syslog.1, /var/log/syslog.*.gz)

What do the logs contain (from postfix, pmg-smtp-filter) around the missing timeframe?

 

[Peter Nielsen]

Well it appears that somthing is going on with the syslog. I've attached a part of the syslog and can see that from 6:28 - 08:02 events are logged, then it jumps from 08:02 to 06:35 and then from 6:36 to 09:43 (time of reboot).
I can't quite make out what is going on.

 

[Stoiko Ivanov]

Well it appears that somthing is going on with the syslog.

I tend to agree - maybe cross check with the system journal if persistent journalling is enabled - if it isn't - please consider enabling it (`mkdir /var/log/journal ; systemctl restart systemd-journald`

since I saw in the logs that you're running ntpd (which does not just jump the clock by 1.5 hours, afaik) - maybe any other timesyncing software (systemd-timesyncd, chrony,...) is causing the problem - or maybe a mistyped `date` or `hwclock` command? Maybe the hypervisor changed it's system-time?!

Apart from that (out of curiosity) - why are you running spamd in addition to/on PMG (it is not used by PMG's stack (which does the spamchecking inside pmg-smtp-filter)?

 

[Peter Nielsen]

I tend to agree - maybe cross check with the system journal if persistent journalling is enabled - if it isn't - please consider enabling it (`mkdir /var/log/journal ; systemctl restart systemd-journald`

since I saw in the logs that you're running ntpd (which does not just jump the clock by 1.5 hours, afaik) - maybe any other timesyncing software (systemd-timesyncd, chrony,...) is causing the problem - or maybe a mistyped `date` or `hwclock` command? Maybe the hypervisor changed it's system-time?!

Apart from that (out of curiosity) - why are you running spamd in addition to/on PMG (it is not used by PMG's stack (which does the spamchecking inside pmg-smtp-filter)?

Hi Stoiko

Thanks for your help, but I didn't manage to figure out what the issue was, so I ended up installing a fresh pmg.

The spamd I think it maybe come from some experimentation/tweeking of the spam detection , from a while back.

Br.
Peter