SpamFoo next steps needed

Problem reported by Douglas Foster - 7/5/2026 at 7:23 PM

Submitted

SpamFoo is a content filtering system, but only that. Senders that are block listed do not need to go through content filtering. Similarly, senders that are allow listed do not need to go through content filtering.

It does not appear that the SpamFoo implementation has options for bypass. That limitation increases the risk of false positives and increases the overhead of using SpanFoo

4 Replies

Reply to Thread

Gabriele Maoret - SERSIS Replied

7/5/2026 at 11:35 PM

Agree

Gabriele Maoret - Head of SysAdmins and CISO at SERSIS

Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)

Douglas Foster Replied

7/6/2026 at 7:14 AM

I opened a feature request ticket on this.

I also asked if there is a way to launch SpamFoo from within Declude, rather than within SmarterMail, because I should be able to build the conditional processing there.

John Quest Replied

7/10/2026 at 3:50 PM

I also asked if there is a way to launch SpamFoo from within Declude, rather than within SmarterMail, because I should be able to build the conditional processing there.

Now that is an idea worth exploring.

Brian Bjerring-Jensen - VonBjerring GmbH Replied

7/11/2026 at 1:29 AM

Another with Spamfoo.

Able to add categories to spamrules like a campaign. Whenever it detects its a campaign it goes to the spamfolder.

Back to Community Threads

Please leave this box unchecked

Reply to Thread

Enter the verification text