Backport of #387 to 2026.x. One commit, cherry-picked from main's d2b41a93. Patch by @StefanSa (#385).
Check now on the Deliverability page used the same cached DNS answers as normal mail traffic, so a report made right after fixing reverse DNS or adding a DMARC record could still show the old state. A manual check now skips this server's DNS caches for PTR, A/AAAA, SPF, DKIM, DMARC, TLS-RPT, blocklists and the MTA-STS record and policy, without reading or writing them. Unchanged: the scheduled daily check, SMTP delivery, and the ten-minute limit on manual checks.
The only conflict was the import line: this branch still has the VerifyPolicy import that main dropped. With it kept, the three files are byte-identical to Stefan's patch on v2026.11.11, which is what he tested.
Checked on this branch:
cargo test -p services --lib inbuxa_deliverability: 4 passed
cargo test -p tests --lib --no-run, cargo fmt --all --check, the four fork checks and changelog-check.py: clean
Backport of #387 to 2026.x. One commit, cherry-picked from main's d2b41a93. Patch by @StefanSa (#385).
**Check now** on the Deliverability page used the same cached DNS answers as normal mail traffic, so a report made right after fixing reverse DNS or adding a DMARC record could still show the old state. A manual check now skips this server's DNS caches for PTR, A/AAAA, SPF, DKIM, DMARC, TLS-RPT, blocklists and the MTA-STS record and policy, without reading or writing them. Unchanged: the scheduled daily check, SMTP delivery, and the ten-minute limit on manual checks.
The only conflict was the import line: this branch still has the `VerifyPolicy` import that main dropped. With it kept, the three files are byte-identical to Stefan's patch on v2026.11.11, which is what he tested.
Checked on this branch:
- `cargo test -p services --lib inbuxa_deliverability`: 4 passed
- `system::deliverability::deliverability_tests` (RocksDB): passed
- `cargo test -p tests --lib --no-run`, `cargo fmt --all --check`, the four fork checks and `changelog-check.py`: clean
A manually requested check now skips this server's DNS caches for every
DNS-backed finding: PTR, A/AAAA, SPF, DKIM, DMARC, TLS-RPT, blocklists,
and the MTA-STS record and policy. The caches are neither read nor
written, so normal SMTP delivery and the scheduled daily check keep
their cached behavior. The ten-minute limit on manual checks is
unchanged.
The MTA-STS policy fetch is split so the check can fetch a policy
without touching the SMTP policy cache.
Fixes#385
(cherry picked from commit d2b41a93f3)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Backport of #387 to 2026.x. One commit, cherry-picked from main's
d2b41a93. Patch by @StefanSa (#385).Check now on the Deliverability page used the same cached DNS answers as normal mail traffic, so a report made right after fixing reverse DNS or adding a DMARC record could still show the old state. A manual check now skips this server's DNS caches for PTR, A/AAAA, SPF, DKIM, DMARC, TLS-RPT, blocklists and the MTA-STS record and policy, without reading or writing them. Unchanged: the scheduled daily check, SMTP delivery, and the ten-minute limit on manual checks.
The only conflict was the import line: this branch still has the
VerifyPolicyimport that main dropped. With it kept, the three files are byte-identical to Stefan's patch on v2026.11.11, which is what he tested.Checked on this branch:
cargo test -p services --lib inbuxa_deliverability: 4 passedsystem::deliverability::deliverability_tests(RocksDB): passedcargo test -p tests --lib --no-run,cargo fmt --all --check, the four fork checks andchangelog-check.py: clean