A few of the emails being sent from my account are getting rejected. These are the error messages:
Server response: 550 550 Requested action not taken: mailbox unavailable invalid DNS MX or A/AAAA resource record
From: Domain is invalid. Please provide a valid From: IB506 http://x.co/srbounce
Is this issue on my end or their (the receivers) end? How should I fix this problem?
You need to add the following MX records to your DNS and associate them with the subdomain mg.yourdomain.com
mxa.mailgun.org 10
mxb.mailgun.org 10
Likely you are seeing those errors because certain email servers do an MX lookup on the domain of the sender of the email (in this case mg.yourdomain.com). If those MX records do not exist, the server will reject the mail.
You likely set up an MX record for your domain but not the subdomain from which the email is being sent. You need to set up an MX record for the subdomain also.
Related
How can I circumvent spam errors when using a mail forwarder in cPanel?
I have a domain which I have configured an email forwarder to forward all emails sent to me#mydomain.com -> me#gmail.com so all my emails land in my Gmail Inbox.
I am receiving emails from trusted external sources but they are going to spam more often than not AND the email address in Gmail shows sender#senderdomain.com via mydomain.com
This also results in bad headers where it fails:
Failed: DMARC Compliant (No DMARC Record Found)
Ok: SPF Alignment
Failed: SPF Authenticated
Failed: DKIM Alignment
Failed: DKIM
Authenticated
I have contacted my server host but they dont know what is happening. Is there anyway to fix this or is there a recommended workaround?
I have a mail server with the domain mail.creoconcept.com
I have many clients that use my email service, each with their own domain. I'm setting up DMARC and SPF records for my server. I've added the following records to the domain creoconcept.com:
Host: #
Type: TXT
Content: v=spf1 mx a ip4:194.65.78.182 mx:mail.creoconcept.com -all
Host: _dmarc
Type: TXT
Content: v=DMARC1; p=none; rua=mailto:postmaster#creoconcept.com; ruf=mailto:postmaster#creoconcept.com;
But my question is: do I need to add these records to all domains that are using my email service?
The domains right now have the MX record mail.creoconcept.com. Is this enough? Will the records at creoconcept.com be reflected on the domains that have this MX record?
I know this is probably a noob question but I can't find the answer on Google.
Both SPF & DMARC are domain specific.
As a minimum you will need to have an SPF record for each of the domains.
On this if the IP address of your mail server is as you have entered into the A record section of the SPF you can remove this value like wise for the MX value making your SPF record:
Host: # Type: TXT Content: v=spf1 mx a -all
This is just removing any duplications from your SPF record entry. However, if the IP address '194.65.78.182' is neither your web site or your eMail server you will need to add it back in but only if it send eMails on behalf of your domain.
For example if you have a contact form on your web site.
As for the DMARC rules again you should add a rule for each domain, changing the 'rua' and 'ruf' values for each of the domains (if you want them to go to a different address'
Everything has been working good untill today, when we had an issue with our SSL certificate when it expired and we changed it for another.
Since that happened, we can properly send emails but not receive them, unless they are emails from our own domain.
The installed SSL is not a Wildcard SSL.
We have not added the subdomain "mail.domain.com" on the Plesk domains list.
We assigned the non Wildcard SSL to work also on email on the Plesk domain settings.
We have no information regarding the non-receiving emails on the Plesk logs.
If i go to the following SMTP tester: https://www.wormly.com/test-smtp-server and send an email checking that it has to be an SMTP email, then that email is received correctly even if it comes from a different domain.
By the other side, if i do not check the SMTP email checkbox, the email is never received
Our DNS records are the following:
domain.com. TXT v=spf1 +a +mx -all
smtp.domain.com. A SERVER.IP
pop.domain.com. A SERVER.IP
pop3.domain.com. A SERVER.IP
imap.domain.com. A SERVER.IP
domain.com. MX(1) mail.domain.com
What can be going wrong?
It has been apparently been fixed after changing the MX record from "mail.domain.com" to "domain.com".
These DNS records have been working for a year since our last update, and the only thing that has changed is the SSL certificate. Im not really sure how this has been affected, maybe the previous SSL certificate was a Wildcard one, while this wasnt, and that made the email not receive properly.
Not really sure about this theory though, but it seems to work.
I have configured office 365 for sending email from my application. Email is sent successfully, but when I check in received email header it shows me like Received-SPF: Fail (protection.outlook.com: domain of mydomain.com does not designate 192.185.45.210 as permitted sender). I have change SPF in my domain like
v=spf1 a mx include:spf.protection.outlook.com -all
but still, I got the same error message in the email. I have also try below code too.
v=spf1 include:spf.protection.outlook.com include:mydomain2.com -all
and there is also message like
Received: from gateway21.websitewelcome.com
why websitewelcome.com is there though I am not using this type of setting in my whole application. I have integrated office365 email account in laravel application.
The IP it's complaining about does belong to websitewelcome.com, presumably because your site is hosted there, so I suggest you add their SPF too:
v=spf1 a mx include:spf.protection.outlook.com include:websitewelcome.com -all
It's always worth checking your SPF on Scott Kitterman's site.
We have a client with a website hosted on AWS and he is using Google apps to send notification emails. These emails are marked as spam/junk.
We have set an SPF record as per Google's documentation. Clicking on view messege source I found SPF:softfail. From what I understand, setting up reverse DNS/PTR record can also help, but we have 2 production instances behind an ELB and we're not sure how to set that up as it doesn't have a public IP.
This is how our Route53 setup looks:
example.com A ALIAS ***.elb.amazonaws.com.
example.com MX 1 ASPMX.L.GOOGLE.COM.
example.com TXT "v=spf1 include:_spf.google.com ~all"
mail.example.com CNAME ghs.googlehosted.com
Apparently, the client was sending all of his emails through local smtp without using Google Apps. I've added his IP to the SPF record temporarily until he moves the emails over to go through google. We have also set a DKIM record.
PTR records and ELBs had nothing to do with it.