ok lets break it down
your current envelope-domain is artistdomain.net
its SPF record is currently "v=spf1 IP4:69.94.102.4 IP4:192.168.1.25 -all"
now syntactically/based on results "v=spf1 ip4:69.94.102.4 -all" is what you should have
ip4: not IP4: is what the doc says its possible the other is failing you because they are being sensitive about case
the ip4:192.168 .... MUST GO!
no Internet connected host can or will ever present an IP within this range to anyone outside thus it should and must not appear in an SPF record, its possible they are failing you for this?
for bonus points convince your isp to setup an spf for blue.olm.net
actually as we have seen you sending from spamarrest's servers as well {and you don't want these to be junked do you?}
so you also need to include allowances for their domain
so "v=spf1 ip4:69.94.102.4 include:spamarrest.com -all"
would work but seems crazy as they have
"v=spf1 ip4:208.43.54.96/28 ip4:67.228.0.0/16 ip4:74.86.0.0/16 include:paypal.com -all"
thats 65535+65535+16 + whoever paypal trusts {oh thats a lot of ip's}
no-one needs to trust all those to not-impersonate them ;)
i would go with
"v=spf1 ip4:69.94.102.4 ip4:67.228.25.86 -all"
and grow the 67.228.25.86 to 67.228.25.64/26 or 67.228.25.0/25 67.228.25.0/24
as/when you find they send from further ip's /ranges
or see if spamarrest {as it seems to be an after receipt service} offers an interface to send via your own server instead of by there's {as it looks like just a big webmail reader with spamfoldering capacity}
even gmail offers this now
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com
your current envelope-domain is artistdomain.net
its SPF record is currently "v=spf1 IP4:69.94.102.4 IP4:192.168.1.25 -all"
now syntactically/based on results "v=spf1 ip4:69.94.102.4 -all" is what you should have
ip4: not IP4: is what the doc says its possible the other is failing you because they are being sensitive about case
the ip4:192.168 .... MUST GO!
no Internet connected host can or will ever present an IP within this range to anyone outside thus it should and must not appear in an SPF record, its possible they are failing you for this?
for bonus points convince your isp to setup an spf for blue.olm.net
actually as we have seen you sending from spamarrest's servers as well {and you don't want these to be junked do you?}
so you also need to include allowances for their domain
so "v=spf1 ip4:69.94.102.4 include:spamarrest.com -all"
would work but seems crazy as they have
"v=spf1 ip4:208.43.54.96/28 ip4:67.228.0.0/16 ip4:74.86.0.0/16 include:paypal.com -all"
thats 65535+65535+16 + whoever paypal trusts {oh thats a lot of ip's}
no-one needs to trust all those to not-impersonate them ;)
i would go with
"v=spf1 ip4:69.94.102.4 ip4:67.228.25.86 -all"
and grow the 67.228.25.86 to 67.228.25.64/26 or 67.228.25.0/25 67.228.25.0/24
as/when you find they send from further ip's /ranges
or see if spamarrest {as it seems to be an after receipt service} offers an interface to send via your own server instead of by there's {as it looks like just a big webmail reader with spamfoldering capacity}
even gmail offers this now
-------------------------------------------
Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
Archives: https://www.listbox.com/member/archive/1020/=now
RSS Feed: https://www.listbox.com/member/archive/rss/1020/
Powered by Listbox: http://www.listbox.com