Cnetralized list in admin panel to see all the email that is caught in spamfilter and rejected??
Problem reported by Brian Bjerring-Jensen - VonBjerring GmbH - 6/10/2026 at 2:08 PM
Submitted
Is that possible to make such a list so we can see and check from within the smartermail admin interface?

Check headers, mark them as safe senders asf.
Craig Edmonds Replied
Well, in SmarterMail itself I don’t believe there is currently a centralized administrator view showing all messages that were classified as spam and delivered to users’ Junk folders across all domains. That would probably need to be submitted as a feature request.

On my Linux installation, I have started building something similar externally. I scan the SMTP logs for events such as spam_detected, extract the relevant information, and store it in a MySQL database. This gives me a searchable history of spam detections, including sender, recipient, IP address, spam score, headers, subject, body, action taken, authentication results, and other metadata.

The long-term goal is a broader “mail intelligence” platform where I can:

  • View spam activity across all domains in one place.
  • Identify spam campaigns and abusive networks.
  • Analyse trends by sender IP, CIDR range, domain, country, and subject.
  • Investigate false positives.
  • Automatically build trusted sender lists from legitimate communication patterns.
  • Correlate spam events with authentication failures, greylisting events, and firewall activity.
I have also recently deployed a remote Rspamd server, which provides another valuable source of data. Between the SmarterMail SMTP logs and the Rspamd history, there is a lot of useful information available for analysing spam trends and improving filtering decisions over time.

Having a native SmarterMail administrator dashboard for all spam-detected messages, with the ability to inspect headers, review scores, release messages, and add safe senders directly from the interface, would certainly be useful.
Douglas Foster Replied
Yes, feeding message metadata to a database enables you to see patterns that are not apparent when examining individual messages.   

I use a Barracuda appliance for reviewing individual messages because it has an adequate interface and a rollong 90 day history of everything it has seen.(Summary and full EML).   In front of the Barracuda, I use a server running custom code acting as a pre filter. It sets a message header telling Barracuda how to disposition.   The prefilter logs metadata to a database.   Then a post filter runs after the Barracuda, and it logs metadata about allowed messages to a second database.

Reply to Thread

Enter the verification text