Skip to main content

Issue with receiving emails has me stumped.

mvandemar
So I am at a loss on this one. I am switching a client over from Google hosted emails to using cpanel emails. Using 3rd party nameservers (Namecheap). The domain works fine, I have mail.domain.com set up as an A record pointing to the same ip as the main domain, and I have mail.domain.com as the MX record with a priority 10 (no other MX records, so it's the highest). I can dig @nameserver.com and see the records are there, and I can ping the mail. subdomain just fine. I have 2 emails in cpanel, info@domain.com and clientname@domain.com. I mirrored the dns entries in the cpanel Zone Editor just to be safe. I can send from the accounts using webmail just fine. However, when I try to send to them, they always bounce. This includes trying to send from the server using webmail from one local email account to the other. When I am on the server sending, the Track Delivery error comes back as "fail_remote_domains". I tried updating the dns resolvers to 8.8.8.8 and 4.4.4.4 based on a thread I found, but that did not solve the issue. When I try and send to either account from an outside email (and I tested from several different email accounts) I get "Transport: rejected", and in both cases I get this in the bounce: The mail server could not deliver mail to info@domain.com. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries.
Any thoughts on how to fix or further debug this would be appreciated, thanks. -Michael

Comments

6 comments

Date Votes
  • cPanelLauren
    Hi @mvandemar What is the setting for the Mail Exchanger in the DNS zone file? Is it set to Automatic or Remote? If so, switch it to local and let us know if you're able to send mail to them.
    0
  • mvandemar
    Hi @mvandemar What is the setting for the Mail Exchanger in the DNS zone file? Is it set to Automatic or Remote? If so, switch it to local and let us know if you're able to send mail to them.

    @cPanelLauren - thank you. It was set to Automatic: Local, but when I switched it explicitly Local it started working. Shouldn't Automatic: Local have worked? -Michael
    0
  • ffeingol
    Things always get tricky when you're using 3rd party name servers and not the cPanel server. Automatic only works correctly if the cPanel DNS has the MX record set correctly.
    0
  • mvandemar
    Things always get tricky when you're using 3rd party name servers and not the cPanel server. Automatic only works correctly if the cPanel DNS has the MX record set correctly.

    If that's true, cpanel knows if it's controlling the dns or not so it would be cool if when that's not the case "Automatically Detect Configuration" wasn't the recommended setting. -Michael
    0
  • ffeingol
    It's not quite as simple as you think to determine if cPanel controls DNS. We (for example) use cPanel clustered DNS on dnsonly servers. How would cPanel know that it controls DNS in that situation? Either way, feel to put in a
    0
  • cPanelLauren
    Automatically Detect: Local should have been enough to receive mail locally so I'm not sure why it was requiring strictly Local. The only thing I can think of is that for some reason the domain remained in /etc/remotedomains in error.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post