[bug]: All mail marked as spam due to sieve runtime error in spam-trap

[mwinters0]

trace.log

What happened?

Issue

All mail is currently being marked as spam.

Logs

When the log level is set to "info" there is a WARN emitted in the logs:

2024-08-24T18:56:39Z WARN Sieve runtime error (sieve.runtime-error) listenerId = "smtp", protocol = smtp, remoteIp = 209.85.166.54, remotePort = 49196, id = "spam-trap", details = Unknown store, details = Sieve runtime error

When changing the log level to "trace" there is no WARN emitted, but I instead see this:

2024-08-24T19:37:56Z DEBUG Not enough training data for spam filter (spam.not-enough-training-data) listenerId = "smtp", localPort = 25, remoteIp = 209.85.160.47, remotePort = 54691, details = [3, 3, 200]

I've attached (at the top of this comment) some trace logs of a message from gmail getting marked as spam. Apologies that they're a little bit noisy, and note that I've redacted the relevant fields with strings that start with "REDACTED_".

Version

I'm currently running v0.9.2 in a docker container on Debian 12:

$ podman version
Client:       Podman Engine
Version:      4.3.1
API Version:  4.3.1
Go Version:   go1.19.8
Built:        Thu Jan  1 00:00:00 1970
OS/Arch:      linux/amd64

$ podman run -d -ti --network=host  --volume /data/stalwart:/opt/stalwart-mail 'docker.io/stalwartlabs/mail-server:v0.9.2'

I originally saw this under v0.9.1 and upgraded in the hopes of a bugfix, with no change observed.

Config

Perhaps critically, I am using entirely default sieve scripts and spam configurations. I thought I might solve the problem by creating a spam trap address, so I did that and restarted but saw no change.

Form

How can we reproduce the problem?

Not sure. It's 100% consistent for me but no idea how I got into this state.

Version

v0.9.2

What database are you using?

RocksDB

What blob storage are you using?

RocksDB

Where is your directory located?

Internal

What operating system are you using?

Debian 12

Code of Conduct

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

[mwinters0]

I should add - I'm not sure whether the sieve error is what caused emails to be marked as spam. But I trained some HAM in the admin GUI and now the error is gone, and emails are going to inbox again.

[mdecimus]

You can safely ignore the Unknown store warning, in this case it means that you don't have any spam traps configured.
Check the headers of the messages placed in your Junk Mail folder to find out why they're being classified as SPAM.