jeremy9365 wrote:
We have received some bounce messages when we ship to different addresses: the message is as follows:
554 your access to this mail system has been denied due to the bad reputation of the sending mta. If you believe this failure is due to an error, please contact the intended recipient via alternative means.
We’ve also seen this:
554 connections from this sending hostname companyname.com ip: :ipaddress address are being rejected due to low sender base reputation score (less than -2)
We had an issue where an account was sending emails and that has been fixed. we contacted our mail provider who has not responded so far. the mail server is not on any blacklist; however, the sending base rating is low due to the volume of spam that was sent.
Has anyone had a problem like this? I’ve been all over the web and have all sorts of things to look at, but nothing concrete on how to get out of the referrer base or low mta ratings.
chad.w wrote:
Sometimes when you get on one of these lists, they will keep you on them even after the initial “garbage storm” resolves. What this means is that you may want to take a moment and make sure all of your email best practices are in place before reaching out and begging to be manually removed from some list. they usually delete it when everything is 100% in order, so that’s probably not the case with your mail organization.
- do you have your reverse dns entry in your internet provider and is it correct?
- do you have spf records in your public dns? are they accurate
- are you backscattering spam?
Is your internet provider’s reverse dns entry in place and correct? senderbase says matching fwd.reverse dns is a no. we switched our website to a different provider a few months ago. the a record points to the new ip for the website, there is a ptr record that has the mail server ip pointing to the domain name.
checking the reverse lookup in mxtoolbox I get the following
if I check the ip of the mail server, say 11.12.13.14, it resolves to the domain name
if I reverse lookup a registry address (or ping domainname.com, say 16.17.18.19, it says no registry exists
do you have spf records in your public dns? are accurate
lookup and validation of spf records for: domainname.com spf records are primarily published to dns as txt records.
txt records found for your domain are: v=spf1 a mx:domainname.com ip4:11.12.13.14 -all
spf records must also be published to dns as records of type spf. no spf type records found.
checking if there is a valid spf record.
found v=spf1 record for domainname.com: v=spf1 a mx:domainname.com ip4:11.12.13.14 -all
evaluating… spf record passed validation test with pyspf (python spf library)!
not sure why there were two, but it seems to be valid: mxtoolbox says no valid spf record found
I have an spf record configured in the dns for @(none), mail.domainname.com and www.domainname.com, they are all the same
v=spf1 to mx:domainname.com ip4:11.12.13.14 -all
are you generating backscatter spam?
I’ll have to investigate