l have this message
host gmail-smtp-in.l.google.com[142.250.138.26] said:
550-5.7.1 [129.159.98.193 19] Our system has detected that this
message is 550-5.7.1 likely suspicious due to the very low reputation of
the sending 550-5.7.1 domain. To best protect our users from spam, the
message has been 550-5.7.1 blocked. Please visit 550 5.7.1
Yes. If you would like to share your sending domain, you can post or PM me.
Otherwise, it may be difficult to help as this issue is not directly related to MiaB.
You should also review the Authentication-Results headers in ‘Show original’. Note to view the headers in the header section, not the summary at the top.
my server is box.1001h.store
There isn’t much you can do if a receiving server simply doesn’t like you.
It could be that the domain is too new or has a TLD that Google has identified as being commonly used by spammers, or both.
The only thing you don’t currently have configured is the DS record, although that does mean that TLSA is invalid. You need to go into GoDaddy and enable DNSSEC then add the DS record. I’m pretty sure they should accept option 1 from the MiaB dashboard.
Also, is the email address being sent from an email address with the same domain as the server domain?
Does the MiaB dashboard print any other errors or problems?
1 Like
I have add DS record
yes i sent from email address with the same domain as the server domain
There are zero errors in my MiaB dashboard.
Could this not have anything to do with the provider?
I use Oracle cloud
Note there are some issues and I suspect they are more related to the .STORE TLD than anything else:
https://dnsviz.net/d/1001h.store/dnssec/
https://dnssec-debugger.verisignlabs.com/1001h.store
This DANE validator reports issues for box.1001h.store:
https://check.sidnlabs.nl/dane/
You can try emailing again with the DS record set, but if you continue to receive the same message, your only options are likely to wait long enough and Google might possibly begin accepting email from the server or use a different TLD for the sending server domain. I recommend using a .COM, .NET, or .ORG and at least one of those is still available with your domain.
That said, it is notable that there are other TLDs that work without issue. The domain we are currently on right now uses .INFO for its sending server.
Do you think that the service provider has nothing to do with this problem?
The domain is old and I used it before without any problem
I asked my service provider to configure my SPF because I was having an Rdns problem and they fixed it
A whois query returns:
Creation Date: 2021-06-09T12:29:04.0Z
So not yet two months.
The message from Google states they have an issue with the sending domain.
okay I will try to change the domain
thank you sir
1 Like
Hi @kamdell Have you done anything drastic yet? If not, and if you’re willing I’d like to do a couple of experiments if you’ll be free.