How to fix email configuration problems
Your email address warmed on MailReach has been detected to have a configuration problem.
As it's on your end, MailReach can't fix this for you but don't worry, we'll guide you to solve that ASAP.
The symptom is that your email is not reachable, it generates an error message / a bounce. In other words, when other mailboxes try to send an email to your address, the email bounces back.
This address is not able to receive inbound emails : no replies, limited conversations, not enough warming emails are sent : it reduces the power of MailReach and just prevents you from receiving any email.
In most of the cases it's because of your MX records being misconfigured.
In less than 10% of the cases, it can be a false positive alert because of the type of emails bounces detected by MailReach. In all cases, please follow the steps below.
Use another mailbox you own to send a test email to the email address that has the issue.
From a different mailbox (your personal one for example), send a test email to the email address that has the configuration problem
Wait 3 minutes max to make sure the email has enough time to land.
Case 1 : your test email bounced back
A bounced email is an error message telling you that your email couldn't be delivered for any reason. There are many different reasons.
Here's an example of a bounce :
First, read the error message you received. It may give you more info.
In most of the cases it's because of your MX records being not properly configured.
To help you understand :
Mail Exchange (MX) records are DNS records that are necessary for delivering email to your address.
They are set in the DNS zone of your domain, like the SPF, DKIM and DMARC records.
They are different depending on your email provider to receive emails.
For example, Google MX records are different than Microsoft MX records or than any other inbox provider.
Examples depending on use cases :
Let's say you send emails using Sendinblue and you receive the inbound emails / replies in a Gmail inbox, the MX have to be the Google MX records.
If you send emails from a custom SMTP server and receive the inbound emails / replies in a Microsoft inbox, the MX have be the Microsoft MX records.
As MX records are different for every inbox provider, you need to check with your inbox provider to know exactly what to put as MX records in your DNS zone.
To help, you can Google : "How to set [your inbox provider] MX records"
Make sure you set the MX records the right way.
As DNS zones can take time to fully propagate, wait and come back tomorrow to see if you manage to receive emails on your address.
Case 2 : your test email didn't bounce BUT it never landed anywhere (you can't find it anywhere).
If your test email didn't bounce back but didn't land anywhere, it means "there is technically no inbox behind your address being warmed".
That's an IMAP issue. MailReach can't find the emails any inbound email.
You need to link an inbox to your sending address. If not, you can't receive any inbound email. That limits the efficiency of email warming and penalize your deliverability because you have less engagement.
To fix that, it's different for every email provider. You have to set this up with your provider. Contact their support if needed.
Your goal : your sending address should be able to receive emails OR should redirect the emails received to another inbox. And then make sure MailReach has an access to this inbox (connected with IMAP).
Step 2 : wait 24 hours and see
Once you've checked this :
Wait 24 hours
In the inbox linked to your email address, check if you have received emails from MailReach (inbound emails) => check the folder named "To Follow", MailReach emails are stored inside.
The notification shouldn't pop again 48 hours after. If you still get it, it hasn't been fixed.
Updated on: 02/06/2022