Thank you, BriTim.
I believe you are correct.
None of the three offending FM SMTP servers IP addresses come up when "spf.messagingengine.com" is searched:
Code:
~ $ host spf.messagingengine.com |sort
spf.messagingengine.com has address 64.147.123.17
spf.messagingengine.com has address 64.147.123.18
spf.messagingengine.com has address 64.147.123.19
spf.messagingengine.com has address 64.147.123.20
spf.messagingengine.com has address 64.147.123.21
spf.messagingengine.com has address 64.147.123.24
spf.messagingengine.com has address 64.147.123.25
spf.messagingengine.com has address 64.147.123.26
spf.messagingengine.com has address 64.147.123.27
spf.messagingengine.com has address 64.147.123.28
spf.messagingengine.com has address 64.147.123.29
spf.messagingengine.com has address 66.111.4.221
spf.messagingengine.com has address 66.111.4.222
spf.messagingengine.com has address 66.111.4.224
spf.messagingengine.com has address 66.111.4.225
spf.messagingengine.com has address 66.111.4.229
spf.messagingengine.com has address 66.111.4.230
spf.messagingengine.com has address 66.111.4.25
spf.messagingengine.com has address 66.111.4.26
spf.messagingengine.com has address 66.111.4.27
spf.messagingengine.com has address 66.111.4.28
spf.messagingengine.com has address 66.111.4.29
~ $
The SPF RR TTL is 79,146 seconds or a few minutes short of 22 hours.
Since all the SPF IP addresses are in the "64.147.123.0" and "66.111.4.0" IP ranges, adding "ipv4:64.147.123.0/24" to SPF RR should do the trick (at least for now until FM decides to fix what ain't broke).
Thank you again.
--
Jacinto