Hello,
I'm stumped regarding how to include ATT into my SPF record.
1) I use ATT DSL for my internet connection.
2) I use my own domain's mail server for outgoing mail.
3) I use Spamarrest for inbound mail so I can use that to test
for SPF failures by sending mail to myself.
4) Because I send mail from my local machine it must go through
ATT's network before being sent from my domain at my hosting
company.
5) ATT randomly assigns an IP# to my local router. That is causing
SPF failures. That makes it impossible to include that IP# into my
record. I cannot do an IP4 mechanism to include all of ATT's many
IP#s because 10 lookups is the max before failure. I cannot use an
'include mechanism because ATT apparently doesn't have an SPF
record.
ATT told me how to establish a dedicated IP in Win XP and thereby
prevent my machine from allowing ATT to assign a random IP. That
does not work.
ATT has told me to get a dedicated IP# but that's costly and it'd
only be needed for this purpose. They cannot guarantee that ti
would even work. If my mail must hit ATT's network before reaching
my server, I doubt it would.
First-level support at ATT has no idea what SPF is. Advanced
support does seem to know but has no idea how to fix this problem
to stop the failures.
Surely I must be missing something here.
Thanks for your help.
Wade
6)
Wade Smith
Artistdomain.net
-------------------------------------------
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
I'm stumped regarding how to include ATT into my SPF record.
1) I use ATT DSL for my internet connection.
2) I use my own domain's mail server for outgoing mail.
3) I use Spamarrest for inbound mail so I can use that to test
for SPF failures by sending mail to myself.
4) Because I send mail from my local machine it must go through
ATT's network before being sent from my domain at my hosting
company.
5) ATT randomly assigns an IP# to my local router. That is causing
SPF failures. That makes it impossible to include that IP# into my
record. I cannot do an IP4 mechanism to include all of ATT's many
IP#s because 10 lookups is the max before failure. I cannot use an
'include mechanism because ATT apparently doesn't have an SPF
record.
ATT told me how to establish a dedicated IP in Win XP and thereby
prevent my machine from allowing ATT to assign a random IP. That
does not work.
ATT has told me to get a dedicated IP# but that's costly and it'd
only be needed for this purpose. They cannot guarantee that ti
would even work. If my mail must hit ATT's network before reaching
my server, I doubt it would.
First-level support at ATT has no idea what SPF is. Advanced
support does seem to know but has no idea how to fix this problem
to stop the failures.
Surely I must be missing something here.
Thanks for your help.
Wade
6)
Wade Smith
Artistdomain.net
-------------------------------------------
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