Domain: tatsumi-cs.co.jp
SPF: v=spf1 ip4:61.127.163.130 ip4:20.37.101.223 include:spf.tmems-jp.trendmicro.com include:spf.protection.outlook.com -all
FromIP: 52.101.229.82
SenderAddress: xxx@tatsumi-cs.co.jp

For the above condition,the xeams check SPF fail. but check from dmarcly,spf-record website,both return no problem for spf record.

Xeams spf seems not working for net mask: /26

SPF Mechanism: include mechanism found
SPF Mechanism: include mechanism result evaluated was CIDR length out of bounds

SPF Query DNS Lookup Data
DNS Lookup Performed type was TXT; against : spf.tmems-jp.trendmicro.com
DNS Result: v=spf1 ip4:18.176.203.128/26 ip4:18.176.203.192/26 ip4:18.177.156.0/26 ip4:18.177.156.64/26 ip4:15.168.56.0/25 ip4:15.168.49.64/26 ip4:15.168.56.128/26 ~all

All 4 of the Possible /26 Networks for 18.176.203.*

No follow up for the bug???

Tommy,

We are investigating this. I may take some time.

You can set up an subdomain to test,for example (xxxx@test.synametrics.com)

Host: test

Type: TXT

Value: v=spf1 ip4:144.202.24.128/26 ip4:104.192.6.64/26 ip4:70.35.197.192/26 ip4:208.167.249.192/26 a mx -all

Then you send email from subdomain to support@synametrics.com,you can see the result.

Tommy,

We are unable to recreate this problem. Here is what we did:

• Use the same SPF record you pasted in your post with one additional ip4 containing the actual IP address. This ip4 had a CIDR notation of /26
• Our initial test failed. However, the reason for that failure was a DNS lookup failure.
• Once the DNS was in sync, an SPF lookup was passed for emails originating from the IP.

Click the tools,at the SPF Wizard,you input: tatsumi-cs.co.jp and proceed,then you get the spf record: v=spf1 ip4:61.127.163.130 ip4:20.37.101.223 include:spf.tmems-jp.trendmicro.com include:spf.protection.outlook.com -all

Then click the Verify on the left,input below infomation and submit:

Email Address: xxx@tatsumi-cs.co.jp
Sending host IP: 52.101.229.82

You will see the result.

I will also setup a subdomain to test it

maybe you can try set subdomain SPF to be: v=spf1 ip4:61.127.163.130 ip4:20.37.101.223 include:spf.tmems-jp.trendmicro.com include:spf.protection.outlook.com -all

then test it again to see any error

Seems the problem: SPF Mechanism: ip6 is not yet supported ??

This happens because there is an error related to tatsumi-cs.co.jp in their DNS. They publish two records: TXT and SPF. Try the following commands:

• dig tatsumi-cs.co.jp txt
• dig tatsumi-cs.co.jp spf

They have two different values in both. Xeams is using the one in SPF and not in TXT, causing this problem.