🪲: DMARC report sending can't be disabled

[chrisb86]

What happened?

I use SMTP2GO as SMTP relay. The free plan has a 1000 mail limit per month. Because of this I disabled the sending of DMARC reports.

This worked fine for a while. Today I received a notification that 90 % of my quota is reached. I checked the reports and saw that the server again is sending 30 to 60 DMARC reports per day.

I don't know know, since which release this happens.

How can we reproduce the problem?

Use stalwart 0.13.3.

Set

report.dkim.send = false
report.dmarc.aggregate.send = "never"
report.dmarc.send = false
report.spf.send = false
report.tls.aggregate.send = "never"

See that DMARC Authentication Failure Reports and DMARC reports will be sent.

Version

v0.13.x

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?

Docker

Relevant log output

Code of Conduct

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

[mdecimus]

Read the docs about local vs database settings. All report.* keys are database settings by default and if you modify them manually from the toml it might cause conflicts.

[chrisb86]

I know the docs. They talk about keys that must be stored locally but not that some of them explicitly shouldn't.

At the moment I do it the other way around because I like reproducible configs without clicking GUIs. I put everything in the config unless it's blocked.

config.local-keys.0 = "*"
config.local-keys.1 = "!server.blocked-ip.*"
config.local-keys.2 = "!server.allowed-ip.*"
config.local-keys.3 = "!asn.*"
config.local-keys.4 = "!http-lookup.*"
config.local-keys.5 = "!lookup.*"
config.local-keys.6 = "!spam-filter.*"

I let stalwart write the valuse to the file but only modify it in the UI.

When this is not recommended, we maybe should better explain it in the docs?

Which other settings can cause conflicts, when they are modified locally?

[nomadturk]

Disable "Send rate" and "Frequency" from the UI.