|
AlternateAccount posted:
Does your domain have SPF records in the DNS? If you're unsure, run (replace example.net with the name of your actual DNS domain): code:
It might specify IP addresses explicitly, and/or it might include "+mx" indicating that the servers within your domain with MX records associated with them are also valid email senders. In that case, check the MX records too: code:
You said you've already checked your IP and domain against blocklists, but have you checked that your server has a valid _reverse_ DNS mapping? code:
code:
Failing this old test (at least 20 years old at this point!) gets your email treated as "coming from some spammer server that doesn't even have a proper domain registration" - and today, that means your outgoing emails will very likely go to /dev/null without any error reply. Note that all the "dig" commands I showed here have a "@8.8.8.8" at the end. That tells the "dig" command to contact Google's public DNS server and have it query your domain - this way, you'll get an idea of how your domain actually looks "from the outside". If some of the answers are not what you expect, try the commands again without the "@8.8.8.8" at the end - if the answers change when omitting the "@8.8.8.8", you have found a DNS data propagation problem.
|
# ¿ Apr 28, 2016 20:16 |
|
|
# ¿ May 13, 2024 14:11 |