hyland.cl
550
550 utg6thtUM1vNyutg6tuTiO - [email protected] message rejected AUP#SNDR
All sent mails being rejected
DNS diagnostic tools report incorrect DMARC, MX, SOA and SMTP warnings
DNS records
Send mail from my domains
What does your email provider have to say about the problem?
According to your screenshot, - that rejection was done by “eig-west.smtp.a.cloudfilter.net”.
Note it says CloudFILTER, NOT CloudFLARE.
My email provider did some changes/updates to the DNS records, but the problem persisted.
The actual datacenter where de hosting is locates (Namescheap I seem to recall, in Jacksonville, FL) has also come back stating that nothing is wrong at their end
Thanks DarkDevil for your prompt reply. I am well aware that apparently the rejecting service/server is cloudfilter.net, that is not associated in any way with Cloudflare.
Checks for IP blocklisting associated to my domain only reports one lesser entry out of 72 lists consulted.
Furthermore, if it was a IP blocklist issue all domains on that IP would be affected (more than 2500 I was informed) witch is not the case.
Searching my domain for blocklisting, did not come up positive.
The rejection is for “violation of the recipient’s Acceptable Use Policy (AUP)” but unfortunately does not state what specific violation (incorrect DMARC entry, wrong SPF text, invalid DKIM or SOA records, or a time out for not receiving this info in time) ??
Not clear either if the rejection occurs on the cloudfilter.net server, or on the final recipients server (gmail or yahoo mail in this instance). Or maybe clouffilter.net flags the message “suspicious” and the gmail/yahoo/whoever rejects ???
One suggestion was to move the DNS to a different server, hence Cloudflare.
But the issue still remains, so the question is if it is an DNS issue (and I believe it is, mainly because I can’t think of anything else, o the other possibilities have been explodes with negative results. i.e. it is not blocklisted, it is not SPAM, does not contain profane/indecent language or images, does not contain executables, etc., and I don’t send bulk mail.
Finally running diagnostics some “issues” do show up (see attached screenshots)
So, can this be resolver here?
Not necessarily the recipient’s, but more likely that specific mail server( infrastructure)'s AUP.
We are kept as much in the dark as you are here.
No one from CloudFLARE will ever be able to see what happens on infrastructure belonging to CloudFILTER, or any other third parties.
It is however a well known practice in the email industry, to be “mysterious”, or in other words, “vague”, with error messages, in order to avoid e.g. spammers playing games with you.
The rejection occurs on the CloudFILTER server.
To get more specific than that, such as e..g the reason behind, you will need to reach out to CloudFILTER.
It isn’t technically impossible that your hosting provider may be relying on a third party for their email deliveries, such as e.g. in this case, using CloudFILTER, behind the stage, as a middleman, to relay their messages, and perhaps filter them for spam / phishing / viruses, before passing them on to the (final) recipient (e.g. Gmail, or whichever recipient it may be).
In case your hosting provider are relying like that, on CloudFILTER, it could be as simple as a configuration from your hosting provider, that hasn’t been synchronised correctly from their systems, and over to CloudFILTER’s infrastructure, and therefore CloudFILTER is not allowing you (or your domain) to send messages out at the moment.
In such cases, you will have no other ways than to escalate the problem through your hosting provider.
There is one issue with your DNS, but it it is related to inbound messages (those that are sent TO your domain), not with outbound messages (the ones that are being rejected).
In your DNS, you’re pointing the MX record to a host name, let’s say your destination is “mail.hyland.cl”.
However, in that example, the DNS record for “mail” is currently Proxied (
).
Set the Proxy status to Unproxied (
) / DNS-only, for all email related DNS records .
The MxToolbox website do unfortunately have a strange opinion, such as e.g. the SOA Serial Number, that it claims is invalid, but which isn’t matching reality, at all.
I would suggest you to ignore the SOA warnings you see on their website.
The “mandate” for Reverse DNS (PTR) records are for outbound email servers.
The IP address “104.21.29.100” is one of Cloudflare’s IP addresses, used by their HTTP Proxies for Proxied () records, and have nothing to do with email traffic. Running any kind of blocklist checks as well as Reverse DNS (PTR) record checks on these IP addresses will be therefore completely irrelevant to any email issue you may have.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
