commongroundwa
asked on
SPF record affecting delivery to comcast.net?
I am the system admin for a small non-profit. I took over their network just several months ago. I have a Windows SBS 2003 server running Exchange on the office T1 connection. Web hosting is done off-site at a hosting company. Several weeks ago users began complaining that comcast.net mail recipients were not receivng mail sent from our domain. Typically, within 12 hours my Exchange server will send a "Delivery Notification" DELAY Action: delayed Status: 4.4.7" message. Then, within about 48 hours we get an Undeliverable message.
I have begun looking closely at our DNS records set up with our hosting company (not with our registrar). I noticed that the SPF record pointed to two old IP addresses. They were also referenced at mail2 and mail2 in the A records, which I already removed.
Here is the old SPF Record:
Prefix Value
@ v=spf1 a mx/24 ip4:63.134.207.1/24 ip4:216.119.112.155 -all
This is the new one I created:
Prefix Value
v=spf1 mx mx:mail.commongroundwa.org
I used the MS SPF Wizard, but I didn't fully understand some of the questions. Does this look correct? 64.81.2.226 is the IP on our T1 used to host mail, and it's the only server that will legitimately send and receive mail for our domain.
I have begun looking closely at our DNS records set up with our hosting company (not with our registrar). I noticed that the SPF record pointed to two old IP addresses. They were also referenced at mail2 and mail2 in the A records, which I already removed.
Here is the old SPF Record:
Prefix Value
@ v=spf1 a mx/24 ip4:63.134.207.1/24 ip4:216.119.112.155 -all
This is the new one I created:
Prefix Value
v=spf1 mx mx:mail.commongroundwa.org
I used the MS SPF Wizard, but I didn't fully understand some of the questions. Does this look correct? 64.81.2.226 is the IP on our T1 used to host mail, and it's the only server that will legitimately send and receive mail for our domain.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Why do you want to close this? Your question was answered.
ASKER
No, it wasn't. I placed it in a more appropriate catagory and it WAS answered there.
Well, you gave us not a whole lot of feedback and still haven't fixed your SMTP Greeting...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is the new SPF record that I created:
v=spf1 mx mx:mail.commongroundwa.org
This is the correct, and singular mail server IP for our domain
This is the previous SPF record that I originally found:
@ v=spf1 a mx/24 ip4:63.134.207.1/24 ip4:216.119.112.155 -all
Neither of these IP addresses are valid and haven't been for some time, since before I took over.
I do understand what the SPF record is, I just want to be sure that the new SPF record that I created is correct. The old IPs (63.134.207.1 & 216.119.112.155) are no longer valid.