Don’t resend until you check your subscription practices and lists to make sure emails are only sent to recipients that have requested them.
If you’re an administrator for message content or mailing policy and you’ve made significant changes, or you’ve received this error for more than 48 hours, we ask that you review your outgoing emails for objectionable content or practices. Review our best practices for senders to learn how you can help your emails reach Yahoo Mail.
If you’re not the administrator of the mail server in question , we suggest you contact the administrator.
basically they want you to quit spamming … are you sending bulk email? If so have you checked all the things on the recommended list, and signed up for their Complaint Feedback Loop Program? PM me your box hostname if you’d like me to look at what may be the cause.
Ok, part of your problem is that you have not set things such as DKIM in your DNS at NameCheap. You need to enter the entries on the External DNS page. That or allow MiaB to host DNS for your domain.
I created a glue record for [ns1.box.firstsightmedia.com] not an A Record, per Namecheap instructions. Yes I created 8 text records for DKIM, DMARC, SPF, etc?
Ok, well then there is some confusion. WHOIS shows that the NameCheap servers are providing DNS for your domain. You even said that you wanted to use NameCheap’s DNS. So if you want to use the MiaB for the DNS, then you need to change the name servers at NameCheap to ns1.box.firstsightmedia.com and ns2.box.firstsightmedia.com. And add the glue for ns2 if you have not.
Now I see that your DNS has a second MX record which needs to be removed. The MX record for your domain is box.firstsightmedia.com so the MX record for firstsightmedia.com needs to be removed.
There is still no sign of any other records in DNS relating to email. I have dealt with NameCheap’s DNS in the past and from my experience it is horrible. I have never been able to set a record correctly in their DNS as they have specific ways that they want them entered which is not generally overly intuitive. I have always asked them to set the records. Perhaps it is time to contact support for some help setting these records.
I see that you are now publishing DKIM and SPF records in DNS … I presume that the call to NameCheap resolved the issue. Will you please share what the issue was to potentially help others in the future.
Also, now that you are publishing DKIM and SPF (and I assume DMARC records) has your deliverability situation improved yet?
Namecheap appends the naked domain to txt entries. So in the provided DNS admin, when you create the host name DO NOT add the naked domain to the HOST form entry, like in my example .ie firstsightmedia.com
Thanks for sharing as it may help someone down the road who uses NameCheap for DNS. Their documentation is not overly clear and this is an example of that.