No reverse name ptr for your sender ip

Get answers from your peers along with millions of IT pros who visit Spiceworks.

Best Answer. Verify your account to enable IT peers to see that you are a professional. We found 6 helpful replies in similar discussions:. Fast Answers!

  • Table of Contents.
  • property records search dayton oh.
  • Welcome to our Plesk Community;

Was this helpful? Ghost Chili. Muhammad Bilal Nov 18, Go to below link for dns resolution. See below link for reverse lookup. See all 6 answers. Popular Topics in Email Servers. Which of the following retains the information it's storing when the system power is turned off? Carl Holzhauer This person is a verified professional. Did you check the reverse lookup? Fix RDNS and you should be fine. Cory Aug 24, at UTC. Thai Pepper. Reverse lookup is based on the IP from which your mail server is sending from. Say you have a block of IPs at HQ.

Your PTR record, mail. This is an anti-spam mechanism. If so, I would recommend you use a smart host for sending out mail. This way, your smart host sends out the mail for you on your behalf. That is what mail.

[SOLVED] Reverse DNS Not Working on some Email servers - Spiceworks

Our static IP is setup as We only have a single IP, not a block. But it does already. Case Studies Learn from stories of other customers like you. Podcasts A podcast about how we communicate with each other. Videos See what Mailgun's all about, watch our webinars, and more.

Reverse DNS

Guides Learn the ins and outs of email and sending best practices. Log In Sign Up. Featured Stories Popular Stories Categories. Best practices. Customer success. Email DIY. For devs. Quick tips. What's new. Sign Up For Free. Related posts Recent posts Top posts. Mailgun Team. Patrick Tilley. What's new Spooky Sending - Halloween What's new Where is my email going? Introducing Inbox Placement. Whereas with legitimate situations, you can ask the other domain administrator to make the appropriate change on their side as well. Home Questions Tags Users Unanswered. Does a PTR record prove anything about the sender's email domain?

Ask Question. Asked 8 years, 1 month ago. Active 3 years, 9 months ago. Viewed 6k times.

23 Replies

Peter Mortensen 2, 5 5 gold badges 22 22 silver badges 24 24 bronze badges. Jake Jake 5 5 gold badges 19 19 silver badges 47 47 bronze badges. Want to say a big thank you to all who spent time posting answers and comments at length to help me. I would give more up votes if I could.

Now back to your original question: Receiving mail servers check none, one, many or all of the following: Is the HELO name equal to the hostname A record? Does the sender's domain have at least one MX record? Reverse DNS must be in the form of a fully-qualified domain name. Reverse DNS containing in-addr. Reverse DNS consisting of IP addresses are also not acceptable, as they do not correctly establish the relationship between an IP address and its associated domain.

Sorry, I think I am too dumb to understand. So what even if the forward and reverse DNS matches?

Reverse DNS White Labeling — Hello, My Name Is…

It doesn't say anything about the sender or the sending MTA. I can set up mydomain. So I can set up an honest PTR for x. It says the server admin had a clue how to set up properIP networks - which is different from "some bot on a home machine just being spamming over an end user ADSL connection". TomTom I know I just have to do it. But I am still not convinced of the value of checking the PTR!! Must be missing some important link. I sent the reasoning AOL gives for checking this information.

The value is that it tells the receiving server that the sender is established properly. Other than that, it's a best-practice.

Your Answer

It proves that you are who you say you are. Update: Some history and clarification. You need to know that none of this is guaranteed to work. It doesn't stop me from sending as me gmail. Which incidentlaly is the job of SPF.

So why doesnt it simply just check the SPF for gmail. Because as email goes, SPF is relatively new. That's what I don't understand too. In practice, my outgoing and incoming could both be different. It is not, as the domain in the email has nothing to do with the host name. Hosts may send tons of different domomains from one computer. The PTR just has to point back to the name the hosts identifies ITSELF as not the email - otherwise it is assumed you area dial up host and people dont want to deal with botnet spam from private computers via DSL, pretty much.

PTS to Host name is basic network setup, not email. It is used to check you have your network under control.

But my public IP is. The receipient server sees the connection coming from.