#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Aug 2016
    Posts
    3
    Rep Power
    0

    Reverse DNS Not Working on some Email Recipients


    We host our email for thecomputerguy.co on an internal server.
    Everything has been working fine for several years, but recently we have started getting bouce backs from various other servers.
    They all seem to have the following error:

    Reason: Remote SMTP Server Returned: 550 Sender IP reverse lookup rejected

    I have checked all the blacklists and we don't seem to be listed on any.
    I have done a reverse lookup from several sites and they all seem to be responding with the correct rDNS.
    Does anyone have any suggestions?

    Thank you!
  2. #2
  3. Lazy Moderator
    Devshed Supreme Being (6500+ posts)

    Join Date
    Mar 2007
    Location
    Washington, USA
    Posts
    16,436
    Rep Power
    9645
    It does look right. Are you sure the emails are being sent from that mail server and not somewhere else? Is there a NATting router or something else in the way? If you hit up api.ipify.org (eg, with wget or curl) what IP address does it report?
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Aug 2016
    Posts
    3
    Rep Power
    0
    There is nothing between my server and the internet except our Firewall. And the email is sent directly from my server. We don't have a 3rd party smarthost.
    The IP I get returned is 71.2.114.246.
  6. #4
  7. Lazy Moderator
    Devshed Supreme Being (6500+ posts)

    Join Date
    Mar 2007
    Location
    Washington, USA
    Posts
    16,436
    Rep Power
    9645
    I assume the mail server that rejected you didn't happen to include more information, right? Like the hostname it resolved?

    The only other thing I can think of is that your mail server is being used to send spam - or even just relay mail for another domain. Can you see what emails are being bounced and confirm they're from you?
  8. #5
  9. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Aug 2016
    Posts
    3
    Rep Power
    0
    This has been fixed...
    I was able to get in touch with a few of the domains that could not receive our mail and they were all using a Barracuda device.
    It turns out the Barracuda saw the .co and assumed it was coming from Columbia and blocked our mail. So we renamed our server with a .org address and reconfigured the RDNS with the same .org address and all is well now.

    Thank you for your help!

IMN logo majestic logo threadwatch logo seochat tools logo