Hello,
MagicSpam is blocking a few incoming messages with reason '550 5.7.0 Your server IP address does not have a valid reverse DNS entry'.
After some user complaints for not receiving certain emails, I investigated with the help of external tool https://www.debouncer.com/reverse-dns-check just to find that according to it, these examples that I gave had a correct reverse DNS entry.
So I turned off "Require Mail Servers to have rDNS configured" in the maginspam configuration while trying to find a solution.
Today I rechecked and I've realized that magicspam is still blocking certain incoming emails for not having valid reverse dns.
So my incidence is double:
1) Is there anything else to do in order to stop performing reverse DNS checking, in addition to switch off option "Require Mail Servers to have rDNS configured" in maginspam configuration?
2) The tool is determining then the following IPs (only as an example) do not have valid reverse DNS, altough both pass the test in https://mxtoolbox.com/ReverseLookup.aspx and https://www.debouncer.com/reverse-dns-check
85.214.221.156 (h2582090.stratoserver.net)
86.109.162.135 (h0125.hostytec.com)
Incorrect reverse DNS entry detection?
Re: Incorrect reverse DNS entry detection?
Hello alowebs,
Thank you for your post.
To be able to assist you better, would you please post the original rejection message that will tell us exactly which rule has been triggered for this message to be rejected.
Considering MagicSpam has four rDNS checks available, this will help us to determine which one exactly is the culprit here.
Looking at the examples you have provided:
85.214.221.156 (h2582090.stratoserver.net)
86.109.162.135 (h0125.hostytec.com)
it appears that both records are of dynamic kind; dynamic PTR records may have been reported as the spam source in the past which could explain why messages were rejected.
If you do not prefer to post the rejection message in reply to this post, feel free to send it in an email to our support team at:
support@magicspam.com
Please let us know if you have any questions in the meantime.
Thank you for your post.
To be able to assist you better, would you please post the original rejection message that will tell us exactly which rule has been triggered for this message to be rejected.
Considering MagicSpam has four rDNS checks available, this will help us to determine which one exactly is the culprit here.
Looking at the examples you have provided:
85.214.221.156 (h2582090.stratoserver.net)
86.109.162.135 (h0125.hostytec.com)
it appears that both records are of dynamic kind; dynamic PTR records may have been reported as the spam source in the past which could explain why messages were rejected.
If you do not prefer to post the rejection message in reply to this post, feel free to send it in an email to our support team at:
support@magicspam.com
Please let us know if you have any questions in the meantime.
-- MagicSpam Support Team --
Who is online
Users browsing this forum: No registered users and 4 guests