I noticed this too Sergio, so I signed up for an account with Validity just to see how to get rid of the notices.
Once signed up, they tried to funnel me through a sales channel that felt counter productive to reducing spam. I have since deleted my account with them as the whole scheme felt nefarious, happy to be proven wrong though.
This is nothing to do with MailScanner Front-End. It is related to a SpamAssassin test. The link in the error gives further information. If you do not want to create an account with Validity you can disable the validity rules by following the steps in this article:
chrismclennan wrote: ↑31 Dec 2024, 00:31
I noticed this too Sergio, so I signed up for an account with Validity just to see how to get rid of the notices.
Once signed up, they tried to funnel me through a sales channel that felt counter productive to reducing spam. I have since deleted my account with them as the whole scheme felt nefarious, happy to be proven wrong though.
I have also signed out from validity and follow Sarah directions to take out validity.
Happy New Year 2025 to everyone in ConfigServer Forum, specially to Sarah and Jonathan.
I’ve noticed that this issue is becoming more common, and it seems that there still isn’t an effective solution. According to the official documentation, a non-forwarding DNS is required, and a DNS server needs to perform recursive queries to ultimately find the corresponding authoritative server for resolution. Based on this idea, we can use manual commands or online tools that others have already developed to query 1.0.0.127.bl.score.senderscore.com and find that the authoritative DNS server is nsb00.rpdns.net. Therefore, we can conditionally forward the bl.score.senderscore.com domain to the IP address of the authoritative server, nsb00.rpdns.net, on our DNS server.
bl.score.senderscore.com should query results from nsb00.rpdns.net.
sa-accredit.habeas.com and sa-trusted.bondedsender.org should query results from nsw00.rpdns.net.