SPF problem on forum.k9mail.app

Support
1

Hello there,

I think there’s an issue with the SPF record on forum.k9mail.app. My mailserver doesn’t like it and is sending forum notifications to Junk by default.

2025-03-27 15:57:33 #787(rspamd_proxy) <A8DA19>; spf; parse_spf_a: unresolvable A element for amxip4:109.230.236.132ip6:2a05:bec0:1:3::42-all: forum.k9mail.app

(FWIW this is rspamd v3.11.1 as shipped and configured by docker-mailserver v15.0.2.)

Here’s the record itself, as supplied by one of the authoritative nameservers:

$ dig +short @kia.ns.cloudflare.com. forum.k9mail.app TXT
"v=spf1" "a" "mx" "ip4:109.230.236.132" "ip6:2a05:bec0:1:3::42" "-all"

According to RFC 7208 section 3.3:

If a published record contains multiple character-strings, then the record MUST be treated as if those strings are concatenated together without adding spaces.

So that would be read as:

v=spf1amxip4:109.230.236.132ip6:2a05:bec0:1:3::42-all

Which I wouldn’t expect to work.

It would be helpful if the person responsible for the k9mail.app domain could fix this. What would be a good way to reach them?

Thanks :slight_smile:

1 Like
2

All the popular SPF checkers agree: bad syntax.

2 Likes
3

The SPF should be stored as one single quoted string, not a mutli-part like shown here. They would be reassembled without the required spaces as described in the original post.

I wonder if this is an unintentional side effect of Cloudflare’s recent change to how they handle TXT RRs. They used to not place quotes in the records.

If someone with access to the Cloudflare account sees this, it would be worth checking out that record.

4

I don’t know who is responsible for the domain now that cketti isn’t responsible anymore, but let’s ping the developers @kewisch and @wmontwe. For convenience, here is an sfp checker website showing the problem: https://mxtoolbox.com/SuperTool.aspx?action=spf%3aforum.k9mail.app&run=toolpage

2 Likes
5

Thanks for the ping, I’ll pass it on and see what we can do!

1 Like
6

It has been a while, but this should now be fixed. Let us know if there area any issues.