Spamfoo stopped working?
Question asked by Richard Roderick - 8/5/2026 at 9:21 AM
Locked
Unanswered
Yesterday my spamfoo stopped detecting all Spam. Is that just me? Some way to figure out why?

Scott Johnson Replied
Based on our install it would have stopped around 8/3 2026-08-03 12:08:32.774 -06:00 [WRN] Client update available: 0.7.121 -> 0.7.127. Seems the people writing the code did not think about requirements, On Linux it will show /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found
Richard Roderick Replied
Ooh, nice find. If this helps I am running on Debian 12:
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm

Richard Roderick Replied
In the SpamFoo error log:

System.DllNotFoundException: Unable to load shared library '/opt/smartermail/SpamFoo/bin/runtimes/linux-x64/native/libfastmime.so' or one of its dependencies. In order to hel
p diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /opt/smartermail/SpamFoo/bin/runtimes/linux-x64/native/libfastmime.so)

   at System.Runtime.InteropServices.NativeLibrary.Load(String libraryPath)
   at SpamFoo.Core.Email.FastMimeLoader.Resolve(String name, Assembly assembly, Nullable`1 searchPath)
   at System.Runtime.InteropServices.NativeLibrary.LoadLibraryCallbackStub(String libraryName, Assembly assembly, Boolean hasDllImportSearchPathFlags, UInt32 dllImportSearchP
athFlags)
   at SpamFoo.Core.Email.FastMimeNative.fm_options_default()
   at SpamFoo.Core.Email.FastMimeNative.fm_options_default()
   at SpamFoo.Core.Email.EmailMessage.Load(ReadOnlySpan`1 data)
   at SpamFoo_Ninja.Services.ReviewContentExtractor.TryExtract(ReadOnlySpan`1 message, ILogger logger)

Scott Johnson Replied
You are correct it no longer runs.  Very poor dependency management by those writing the code. Hidden updates are a killer.  SmarterTools and SpamFoo need to do better than this.  It took me two days to get them to understand in my ticket.  Code release/versioning not well done.  Way too many regression issues.  Need to go back to the old way we were taught in CS.  Updates/Upgrades never the two shall be mixed.  Updated fixed released versions.  Upgrades changed the version with functional changes and new functions. 
Richard Roderick Replied
Since this isn't a totally critical system for myself, I upgraded to Debian 13 and it works again. Yeah, the hidden update which broke a dependency, not ideal. 

Thanks for the clue Scott!
Scott Johnson Replied
Yep, sadly though SpamFoo claims: 

Supported Operating Systems

PlatformSupported Versions
Windows Server2016 R2, 2019, 2022, 2025+
Windows Desktop10, 11+
Ubuntu22.04+ (LTS version)
Debian11+
RHEL8+
CentOS Stream9+
AlmaLinux8.10+
Rocky Linux8.1+
DockerLinux x64 containers (see Docker Requirements)
Scott Johnson Replied
Seems this requirement has been there. They just forgot to compile with libc directly within the compiled binary, they needed to perform a static linkage rather than the standard dynamic linkage.

Old versions had a static linkage. Bad processes lead to bad results.  You can copy the 0.7.121 libfastmime.so file in and it will all work
terry Replied
So, will there be an updated fix for this? I am currently away with limited connectivity to my server.

Terry

Tim Uzzanti Replied
Employee Post
Yes, SpamFoo has the issue resolved.  I do believe there will be an update today. Keep in mind, this is in BETA and that is why we are able to offer it for FREE.   The integration of SpamFoo is a significant undertaking.  For those who have purchased Cyren or Message Sniffer, we are also trying to get SpamFoo FREE for the term of your maintenance and support after the BETA ends.  

Scott, sounds like what you develop is always bug free. :) 
Tim Uzzanti
CEO
SmarterTools Inc.
Scott Johnson Replied
Tim,

Nope but after 30 years doing this, we spend time making sure not to have this issue by using good processes.  In this case not using static links to add the required glibc to cover the dependencies means a manual process was used that will always create these issues.   Compilation accuracy should not be left to the focus of the moment.

Are you sure the example you set with statements like this ("sounds like what you develop is always bug free")  is the one you want the company to portray?  I spent way to much time with the help desk and had show them before they would address this.  This is just one of many times hours are spent debugging code that was not considered "BETA".

As for the fix.  It could have been done in a few minutes.  Just recompile libfastmime.so with static links

If you step back, look objectively not defensively, at the common theme in these thread discussions on your forum, your users are try desperately to alert you to the issue.  Like all, you either will or won't see it, will or won't change and will or won't succeed but attacking the messenger is a losing strategy. I know, been there, done that.  Accountability can feel like an attack when you're not ready to acknowledge the issue.   Be different, move past the "close enough is good enough of Google".

"Perfection is not attainable, but if we chase perfection we can catch excellence." — Vince Lombardi
Tim Uzzanti Replied
Employee Post
This isn’t a discussion about a bug; it’s about being rude. We’re all over it when you tell us about an issue, but if you want us to tell us we’re idiots, go find another company to work with. 

We support many millions of users and do it really well. You complained about talking to support, how about giving us kudos that you can talk to support within hours, not days and weeks like our competitors.

I can't stand people who need to put others down.  We do what we do because we care, and we will not spend time on people who are rude.  If you don't like it, find another company to work with. This thread has been locked.
Tim Uzzanti
CEO
SmarterTools Inc.