Further testing: Running this directly on the server: echo test | /usr/sbin/sendmail -f hu@club.ringpi.top test-xxx@mail-tester.com
The message arrives signed (selector devil, matching the published DNS key), but mail-tester.com reports the DKIM signature as invalid — not missing. This means the message body/headers are being altered after DKIM signing somewhere in Exim's pipeline (e.g. SpamAssassin, footer injection, content filtering) — before final delivery.
No Gmail or external relay is involved in this reproduction; it's fully server-side.
Also noting: .eximrc has selector=default set, but outgoing mail is still signed with s=devil — suggesting the account's mail submission doesn't read ~/.eximrc as expected.
Could you check the order of DKIM signing relative to content filtering for this account, and confirm which config file actually governs signing?