-
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: haven't modified the sieve scripts, in the UI I can see those scripts:
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: Versionv0.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 outputNo response Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Try setting the log level to |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
Not at the moment because we need to be able to update the spam filter rules without having to recompile the binary. |
Beta Was this translation helpful? Give feedback.
Try setting the log level to
traceand 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.