OVHcloud Community

Welcome to your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.

Unable to receive mail from certain addresses


#1

Hello I have a domain registered with OVH. I’m currently hosting my website on Netlify.
I’ve also configured some email redirections from OVH to a Gmail account. I have MX Plan 1.

This is the message that some of my senders are getting while sending emails:
This is the mail system at host mo557.mail-out.ovh.net.

I’m sorry to have to inform you that your message could not
be delivered to one or more recipients. It’s attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

               The mail system

*********@gmail.com: host gmail-smtp-in.l.google.com[173.194.76.26]
said: 550-5.7.26 This message does not have authentication information or
fails to 550-5.7.26 pass authentication checks. To best protect our users
from spam, the 550-5.7.26 message has been blocked. Please visit 550-5.7.26
https://support.google.com/mail/answer/81126#authentication for more 550
5.7.26 information. g5-20020a5d64e5000000b0020c829ce30fsi11949933wri.949 -
gsmtp (in reply to end of DATA command)

where ***** is my other gmail address.

My DNS zone is configured in Netlify account as following:

mydomain.it 3600 IN MX 1 mx0.mail.ovh.net.
mydomain.it 3600 IN MX 5 mx1. mail.ovh.net.
mydomain.it 3600 IN MX 50 mx2.mail.ovh.net.
mydomain.it 3600 IN MX 100 mx3.mail.ovh.net.
mydomain.it 3600 IN MX 200 mx4.mail.ovh.net.
mydomain.it 3600 IN NETLIFY mydomain.netlify.com
www.mydomain.it 3600 IN NETLIFY mydomain.netlify.com
_dmarc.mydomain.it 3600 IN TXT v=DMARC1; p=none; rua=mailto:postmaster@mydomain.it
mydomain.it 3600 IN TXT v=spf1 include:mx.ovh.com ~all

mydomain is just an example domain.

I’m assuming that the DMARC record is correct because if I test mydomain with some MX Tools, it get verified correctly.

So why am I getting this error??

Below there is a detail of the error directly from Gmail help guide:
550, “5.7.26”, " Unauthenticated email from domain-name is not accepted due to domain’s DMARC policy. Please contact the administrator of domain-name domain. If this was a legitimate mail please visit Control unauthenticated mail from your domain to learn about the DMARC initiative. If the messages are valid and aren’t spam, contact the administrator of the receiving mail server to determine why your outgoing messages don’t pass authentication checks.

I’ve missed some important emails, and I can’t figure out why this happens only from certain senders, which by the way are not blocked by Gmail, because if they send emails directly to my Gmail address, there are no problems…

Please advise some help


#2

Same problem


#3

I have the same problem. Please advise us.


#4

Any suggestion for this? It’s very frustrating. And keeps happening very often.
OVH please advise some solution. This is unaccettable.


#5

I also have problems with the RECEIVING of messages - there is feedback “user is over quota” and in fact, whether in the rouncube or in the OVH panel, it is 27%. The second box is the same, but it’s 5% there. And so for 3 days.


#6

Same problem here. Can anyone share a working SPF/DMARC config for email forwarding from ovh domains to gmail?


#7

Add your domain (ex: oberlo.com) to Postmaster Tools
https://postmaster.google.com/managedomains?pli=1
Verify your domain:
To prove that you own this domain, click Verify.
Tip: After verification, it may take some time before your domain’s verification status updates to “Verified.”
during veryfication you have to:
Add the TXT to the DNS configuration for ex: oberlo.com
TXT record: (example: google-site-verification=rG6rwV1Lu9S8OKQGpU0e0yWioY78HQ8q0OsaElNyPBc)

Info from supoort
https://support.google.com/mail/answer/9981691?hl=en

After that you have to Create & use App Passwords
https://support.google.com/accounts/answer/185833?hl=en
select an application as: other
select a device as: (choose system)
copy the generated password
and change the password in ovh email using this generated password
then change the password in gmail setup > Accounts and Import
section: Check email on other accounts (POP3)


#8

Also having this problem.
Domain (ex: example.com) managed by OVH with email forwarding (ex: info@example.com => myemail@google.com).
The domain example.com is correctly configured (SPF and DMARC).
But when i get messages from other people, ex: otherpeople@gmail.com, when the message is forwarded from info@example.com to myemail@gmail.com Google Mail thinks the message is coming from an OVH mail server which doesn’t match with the sender (otherpeople@gmail.com) and SPF fails

In the message headers (Google Mail > Show original) I can see two SPF test results. The first passes, but the second fails:

First SPF check is ok:

Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.208.173; helo=mail-lj1-f173.google.com; envelope-from=otherpeople@gmail.com; receiver=info@example.com

IP 209.85.208.173 is mail-lj1-f173.google.com

Second SPF check fails:

Received-SPF: softfail (google.com: domain of transitioning otherpeople@gmail.com does not designate 46.105.37.156 as permitted sender) client-ip=46.105.37.156;

IP 46.105.37.156 is 8.mo552.mail-out.ovh.net

The second and failed SPF check is the one that counts for Google SPF check.

Looking at https://support.google.com/a/answer/10685928?hl=en

Check message forwarding
Even if SPF is correctly set up for your domain, forwarded messages can fail SPF. This is usually because of the way the forwarding server forwards messages.

Recommended steps:

To verify the message was forwarded and get the original recipient address, get message details with Email Log Search. If the person reporting a message as spam isn’t the original recipient, it’s likely the message was forwarded.
Contact the third party that forwarded the message to find out if they can change how they forward messages.

This is where I think the problem resides. Maybe OVH is not correctly forwarding messages and can fix this?