I've migrated DNS from GoDaddy to AWS, along with MX records. My MX record was set to my G Suite account with Gmail. After migration, I leave the same MX record on AWS as it was set on GoDaddy. My mail wasn't working for 20h - I couldn't receive or send any message. However, I didn't receive any mail about "Not delivered" status.
Few minutes ago, I've updated MX record and I received some messages.
Is it any way to recover mails which could be sent to me during 20h when DNS were wrong?
If you didn't have the Correct MX records set, whoever tried to email you should have gotten a bounce back email that the mailbox is not reachable.
There is no way to recover as the email messages didn't reach the server.
Cheers
Related
I've got a weird setup with my emails that I need someones brain to look at. I've got it setup like this so that most of my emails are on one server (server1) and then 1 single account is setup on a second server hidden from the rest (server2)
Email Sent to user1#domain.me
MX record for domain.me = mail.domain.me
A record for mail.domain.me = server1 (11.11.11.11)
Email forwarding rule forwards all email sent to user1#domain.me to user#2.domain.me
MX record for 2.domain.me = mail2.domain.me
A record for mail2.domain.me = server2 (22.22.22.22) a cpanel server
Email hits my server now addressed to user1#2.domain.me
Domain forwarding rule forwards all email sent to #2.domain.me to #domain.me
This works great however my mail routing in cpanel is set to local, and therefore when sending emails out on server2 (22.22.22.22) to users#domain.me they're always delivered locally first and foremost
Is there any way around this? so that outgoing mail on this domain obey's DNS records (the mx records) and delivers it firstly to server1 (11.11.11.11) as if it was being sent from any other domain, gmail etc. Perhaps if the account isn't found locally then send on out to the web? Or perhaps there is a way to setup an alias somehow to let the local account receive mail for user1#2.domain.me
Thanks for your time & efforts looking into this
Henry
Check if your remote domains are listed in /etc/remotedomains and /etc/secondarymx. Note that if your second server has a dns server, it will try fetch the dns data locally first.
I have 2 servers using cpanel where each server acts as the other's backup and I don't have the issue you described.
I've configured several email addresses using the built-in CPanel email utility, and they're all able to successfully send outgoing mail. Incoming mail however is bounced back, with one of the following two errors:
Address not found:
The response from the remote server was:
550 5.1.1 <email#domain.com> Recipient not found.
Message not delivered:
The response from the remote server was:
550 5.4.1 [nathan#fortunesfavored.com]: Recipient address rejected: Access denied
I believe that these error codes (550 5.4.1 and 550 5.1.1) are Exchange server errors, meaning that incoming mail is being directed to the wrong server. (I'm hosting on a GoDaddy service). Is that correct? If so, is this an issue that I would solve in my DNS settings under the MX entry? Here's what I have now:
Priority Host Points to TTL
10 # mailstore1.secureserver.net 1 Hour
0 # smtp.secureserver.net 1 Hour
yes you have to edit your MX entries.
Login to you cpanel account.
under emails click on MX entries.
if there is no MX entry then add a MX entry.
mail.yourdomainname.com and set priority 10
I currently have a domain name which is set to point to Amazon Cloudfront's nameservers. I also have a dedicated server which uses WHM/cPanel that I want to use for all mail.
On Amazon:
The A record for the domain is set to point to the server IP
The MX record is set up as well
On Server:
I have an A record for "mail" that points to the server IP
However, when I log into cPanel webmail, I can send mail but cannot receive it.
Any help would be greatly appreciated. Some type of routing issue I am assuming? When I send an email via Gmail to myemail#mydomain.com, it does not bounce back.
I fixed it by changing the MX record from mydomain.com. to mail.mydomain.com. and then having the A record for mail point to the server IP.
At our business we are running a server for sending newsletters. Setting up the server and sending bulk e-mails is not the issue. That's all working fine.
I run a test on www.mail-tester.com to see how good the mail will pass spam filters. But unfortunately, we are running stuck on the SPF records.
Our setup:
ISP: Business fiber connection with fixed IP. The ISP has setup our hostname as "mail.ourbusiness.com" (fictional domain name)
Website: Our website www.ourbusiness.com is hosted in a datacenter and has nothing to do with our ISP.
The following errors occur:
You're not fully authenticated
We found an SPF entry on your server but it has still not been propagated
Your message is not signed with DKIM
See list of the complete fault message.
It say's that our business IP is successfully associated with mail.ourbusiness.com (so that's good).
Now my question: What should our SPF record be? I can find enough information about SPF records, but I have totally no clue of what I need to put into it!
Oké, solved this issue regarding the SPF record. mail-tester.com has now validated the mail successfully and gives it a 8.8 out of 10.
I did the following in the DNS of our domain ourbusiness.com.
Added A record form subdomain mail.ourbusiness.com with the content the IP address of our ISP.
Added SPF record for subdomain mail.ourbusiness.com
A record
mail.ourbusiness.com A 123.123.123.123
** SPF record **
mail.ourbusiness.com TXT v=spf1 a include:mail.ourbusiness.com ~all
I have 2 domains, let's call them d1.com and d2.com.
I want mails sent to anyone#d1.com to end up in a mailserver at d2.com.
I want to use DNS to accomplish this and first tried the following to get it to work:
On d1.com I set a MX record "# MX 3600 10 mail.d2.com.". On d2.com I set an A record "mail A 3600 10.10.10.1", where 10.10.10.1 is the IP to the mailserver.
It didn't work, emails sent to someone#d1.com disappeared. So then I tried this:
On d1.com I set a MX record "# MX 3600 10 mail" and an A record "mail A 3600 10.10.10.1", where 10.10.10.1 is the IP to the mailserver at d2.com.
This didn't work either, again emails sent to someone#d1.com disappeared.
Something tells me that I somehow have to tell d2.com to accept mails addressed to anyone#d1.com, since d2.com probably expects mails to be on the format someone#d2.com. Is this "accepting" something I can configure using DNS? Or how should I solve this problem?
I think your on the right track with your first DNS changes, however, as you note towards then end of your question, you must configure the Mail Server at d2.com to accept mail from d1.com - this is something to be configured in the mail server and not in DNS.