Emails deliverability (ongoing emails are not delivered

What is the name of the domain?

vlladers.com

What is the issue you’re encountering

Hi, so i am not assuming that i configured everything as it should but i followed every step by step guide provided by Cloudflare onboarding, yet the Emails are not leaving the origin server, i have two emails from one form on for me (forwarded to gmail) and one confirmation email that goes to the one who fill the form, sometimes i receive just one email after 30mn of time, i don’t know where to look

What feature, service or problem is this related to?

I don’t know

This looks like a DNS configuration, email routing or SMTP server issue to me. Have you checked whether the MX record has been verified? The mail-related DNS entries should not be proxied.
It’s also worth to check the SMTP server because it should be configured to go through the intended email server (gmail in this case). Eventually, the email security from Cloudflare could be enable so that the email deliverability would be at fault. Hope this could help.

Blockquote This looks like a DNS configuration, email routing or SMTP server issue to me. Have you checked whether the MX record has been verified? The mail-related DNS entries should not be proxied.

For that part i think its all good, can i share a screen of my DNS set up ? so you can see whats going on.

The mail entries are not proxied, the MX there is only one my domain name set on dns only.

Now the Emails are delayed and i dont receive the Emails that i configured only one Email no confirmation to the sender of the form, and i have also that signature in te head of the Email that says sent Via “Origin server”

When i check the Emails on cpanel i find Mail delivery failed: returning message to sender

Sounds like your Gmail is rate limiting the sender.

All those free mail providers such as Google’s Gmail, Microsoft’s Hotmail/Outlook, Yahoo, et al, are doing that, often for various reasons, such as e.g. what they consider to be too many messages in a short time, to something within the email message content that they don’t like, and so forth.

You’re currently pointing your MX record towards a Proxied (:orange:) record.

Therefore, Cloudflare is replacing your “MX” with this:

vlladers.com.           300     IN      MX      0 _dc-mx.f5f588f2138b.vlladers.com.

DNS records are generally public information, - if you wish to keep certain data (e.g. IP addresses of Proxied (:orange:) records private), you can redact them.

However, it makes no sense to redact DNS records related to email traffic, as they will be publicly available anyway.

$ dig TXT vlladers.com
vlladers.com.           300     IN      TXT     "v=spf1 -all"

The TXT (SPF) record here is instructing other mail servers about that your domain name, “vlladers.com”, does NOT send email traffic.

$ dig TXT _dmarc.vlladers.com
_dmarc.vlladers.com.    300     IN      TXT     "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;"
_dmarc.vlladers.com.    300     IN      TXT     "v=DMARC1; p=none; rua=mailto:[email protected];"

The TXT (DMARC) records here, are conflicting with each other, as you cannot have two of them.

The first one, with the “reject” policy, is instructing other mail servers to refuse email deliveries, that claims to be from your domain name, “vlladers.com”, but where the the email authentication status cannot be validated and connected to your domain name (e.g. DKIM w/Alignment, SPF w/Alignment).

If you’re actually trying to send emails with a “From:” header, that contains an email address under the “vlladers.com” domain name, then the configuration for “vlladers.com” is heavily misconfigured.

In addition, -

The OVH server that you seem to be pointing traffic towards, it is currently having one of these dynamic/generic-looking reverse DNS (PTR) records.

E.g. in the format “ip123.ip-192-0-2.eu”, assuming the example IP address “192.0.2.123”.

Most mail servers out there will refuse deliveries from hosts with such dynamic looking PTR records, or at least, treat your email traffic as suspicious, assuming you’re sending out messages directly from your OVH server (or any other server) with a such “strange” name.

What exactly does that message tell you?

There will be much more information, embedded within that error message.

Sounds like your Gmail is rate limiting the sender.

All those free mail providers such as Google’s Gmail, Microsoft’s Hotmail/Outlook, Yahoo, et al, are doing that, often for various reasons, such as e.g. what they consider to be too many messages in a short time, to something within the email message content that they don’t like, and so forth.

It worked just fine before i try configuring Cloudflare, i am just saying

You’re currently pointing your MX record towards a Proxied (:orange:) record.
Therefore, Cloudflare is replacing your “MX” with this:

what is the right m x to have ?
here is a screenshot of my DNS

How can i fixed that, it seems like it’s all messed up :slight_smile:

This is what the message says about the delivery failure :

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

vlladers . co @ gmail . com
(ultimately generated from contact @ vlladers dot com)
host gmail-smtp-in.l.google.com [66.102.1.27]
SMTP error from remote mail server after end of data:
550-5.7.26 Your email has been blocked because the sender is unauthenticated.
550-5.7.26 Gmail requires all senders to authenticate with either S P F or DKIM.
550-5.7.26
550-5.7.26 Authentication results:
550-5.7.26 DKIM = did not pass
550-5.7.26 S P F [srv90 . octenium.net] with ip: [51.91.25.49] = did not pass
550-5.7.26
550-5.7.26 For instructions on setting up authentication, go to
550 5.7.26 Email sender guidelines - Google Workspace Admin Help ffacd0b85a97d-39d894115f7si1238946f8f.647 - gsmtp

Can i delete one of the conflicting, and wich one ?
Hope there is enough information to get my Emails running again

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.