[bug]: spam filter stopped working after some time

[urbaniak]

What happened?

started receiving spam, when checked the headers - haven't found the X-spam-status header there

in the logs the following errors related to spam filtering:

2024-10-25T06:44:37Z DEBUG Store not found while evaluating expression (eval.store-not-found) listenerId = "smtp", localPort = 25, remoteIp = 192.30.252.207, remotePort = 53055, id = "spam-block"
2024-10-25T06:44:37Z WARN Sieve script not found (sieve.script-not-found) listenerId = "smtp", localPort = 25, remoteIp = 192.30.252.207, remotePort = 53055, id = "spam-filter"

haven't modified the sieve scripts, in the UI I can see those scripts:

• greylist
• spam-filter
• track-replies
• train

what may be the reason that spam filtering stopped working? it was working for sure when started using stalwart a month ago

How can we reproduce the problem?

I can reproduce the problem by doing the following steps:

Version

v0.10.x

What database are you using?

SQLite

What blob storage are you using?

Filesystem

Where is your directory located?

Internal

What operating system are you using?

Linux

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[mdecimus]

Try setting the log level to trace and check if there are any errors in the logs when starting the server. There was a recent change in the filter rules and perhaps you accidentally updated the spam filter without upgrading Stalwart.

[urbaniak]

you're right, there's error at startup, after upgrading binary to the latest version it's gone

thanks for quick reply!

cannot the spam filter rules be embedded in the binary to avoid issues like that? so there's no way of upgrading the spam rules to incompatible version?