All records older than Sunday, August 28, 2016 3:59:25 PM have been purged. The reason for this is simply the number of records causing issues with the outsourced DNS distribution.
ScientificSpam DNSBL has always considered itself a blocklist.
We get delisting requests from hosting providers for whose networks we have escalation listings. Sometimes they are asking for the escalation to be removed in favour of targeted listings for the spammer, implying that they’re okay hosting the spammer even though they understand why we listed them.
We get email that starts with
<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
and all we can say is please adjust your email program so we can read what you wanted to say. That is, if you want us to read it and react to it.
We have already once commented in public on this website (see earlier article) about the difficulty of communicating with you when you write in from a ticket system. This is just a heads-up; we have responded to you. If you don’t see our response, it’s not our fault. If you expect us to respond in your ticket system rather than in e-mail, don’t hold your breath.
Mar 5 11:31:39 x postfix/smtp: 89B9413E055: to=[email protected], relay=aspmx2.spamshooter.com[126.96.36.199]:25, delay=203, delays=0.05/0.04/200/3.1, dsn=2.0.0, status=sent (250 OK id=1j9oj3-0000Gh-CZ)
And as for the issue itself:
- Our services are not used by Yahoo, Hotmail and Gmail.
- Your RFC 5322 noncompliance issues are not related to Scientific Spam DNSBL listings and cannot be fixed by Scientific Spam.
- Get rid of OMICS.
It is already six years and a day since we started operations.
Usage has gone ~25% down on the IP list, with 1.7 billion queries recorded in 2019 (over 2.3 in 2018). The decline is even more marked on the right-hand side list, with 1.4B in 2019 compared to over 3B in 2018.
As always, thank you to everybody who is querying the data. If you have any suggestions, the usual email address is listening.
We replied to you on October 24, 2019, and again on Nov 5 (if only to indicate that we had already replied). You keep sending in new messages that don’t indicate you’ve seen any reply from us. We keep deleting the new messages. If you want to have a conversation, you need to have a conversation, and that means reading our replies and responding to them.
We keep deleting your new messages that contain no new information.
Message-ID: <20190826103442.GF18782 at crick.scientificspam.net> if you want a response.
You write to us from a ticket system, we respond to you, and then you never respond back to us, eventually closing the ticket as nothing further has been heard from “us” on “our issue”.
Hey, that’s okay. We don’t mind your issue with us staying unresolved. But as far as we remember, you started the conversation…
Back in January, a representative of the ESP Marketo attempted to start a delisting discussion by leaving a comment on one of the posts on this website. We declined to discuss the matter in public as we always do.
So, knowing that Marketo is a serious ESP and is generally able to carry out a conversation related to abuse, we sent an email to abuse @ marketo . com quoting the content of the website comment we declined to publish and responding to the points in it, asking for a response.
Nothing until today – when their ticket tracking system was kind enough to inform us of the fact that Marketo Delivery Case #01266633 had been closed.
Five months of nothing and then an auto-ack. Good work.