This is a blacklist of any source IP that connected to our network to deliver spam or attempt a relay of mail to another network through our server(s). Spam is any commercial email that hits our spam traps and are initiated by a company that send newsletters, e-mail campaigns or customer related communication in an automated way to such typ of e-mail address. Our spam traps are all typo-traps. Typo traps are addresses that looks like a common address from one of the know ISPs. Companys who send e-mails to such typ of addresses does not reach their customers instead they send personal information to third parties like our traps. These companys need improve their address quality, implement processes to protect customer's data (e.g. e-mail confirmations, syntax checks or other e-mail verification methodes). It is obviously a form unsolicited bulk or commercial e-mail), deceptively malformed (wrong recipients). Mail sent to any of my spam traps and threatens the protection of personal data of the actual recipient / customer.
Basically, we believe in preserving the standards of the open internet, so we will not punish any mail delivery system (MTA) for permitting relaying if that host has no record of spam. We find it hard to tell the difference between mail emerging from an open proxy and mail emerging from dialups (direct-to-MX) spammers (except for whois data which is sometimes inaccurate anyway), so we'll just list them both regardless; anyway, open proxies aren't regularly used for legit purposes where mail is concerned, and provide inappropriate anonymity for the spammer not normally provided by an open relay, so we felt we should draw the line there. For other open-proxy-like entities like Webmail/formmail/other CGI scripts/programs, the output host is the only one that gets it - either the relay passed the message from the host running the CGI, else the badly-insecure webserver - probably not both.
You'll get listed only if your host sends us spam, as defined above or relay probes us, NEVER otherwise. We will not foretell, in any way, any host or netblock, for we may punish the innocent. Instead, as a not unreasonable compromise, we will kindly request of the ISP to let us know when it has dealt with the customer or fixed their proxy or whatever. If the ISP should have bad WhoIs data, the upstream provider is always contacted instead. The WhoIs data must have an abuse contact explicitly (this may be present in a Remarks field) in order that we consider the WhoIs data useful. Otherwise, should the reporting of persistent spammers from a single network prove ineffective, we will simply take the situation to their upstream provider; we will still not take drastic actions by including entire netblocks, and our own judgement is used to determine when this report to the upstream provider will be made based on how much spam we've had from them and how many sincere requests we've already made to them without effect. The IP will remain blacklisted until the ISP acknowledges (the acknowledgement will be carefully inspected) either robotically or from a human that the problem is cleared up. Then, hopefully, the whole issue of dynamic ranges and who gets what IP should go away - it's the ISP's responsibility to tell us they chucked the customer. We would not rather just list dialup ranges, because many customers have good reasons to run their own MTAs and not to depend upon their ISP's. The exception to this rule is if an anti-spam group or blacklist owner can provide substantial evidence (for no charge) that netblocks have had a reputation for serious spamming or spammer-neutrality, in which case I might consider a netblock be listed.
The list is more of an warning for company's to protect their customer's data than many other larger blacklists for the more usual dialup spamrunners, and we hope this will greatly help. We get the spam and find its source so you can enjoy a more data proteced mailbox, and know that the criminal must be dealt with before the ISP gets its next rest. Unless the third party providing the DNS Service starts noticing very strong interest in the zone, I offer it to you at no fee. It is certainly not a replacement for other blacklists which suit your various political requirements better.
No zone transfers are allowed for this zone.
So, in summary, don't send commercial e-mail to typo domains and ye shall not be marked. I am liberal and forgiving, but I refuse to find more and more ingenious ways of catching spammers by restricting even more of our already tightly restricted internet and email. I am totally blind, and email is very important to me - it seems right to protect it with fair justice.
Query an IP4R blacklist at spamsources.yamta.org (EG to find if spam with IP a.b.c.d exists, look up d.c.b.a.spamsources.yamta.org). The zone returns 127.0.0.2 if the IP is a spam source.
In the event that an IP becomes both a spam source, it will be listed as a spam source.
To observe a hit from this list, query for either 127.0.0.2. You will get the IP you queried for - IE 127.0.0.2 is a hypothetical spam source.
If they get large volumes of queries, users will need to bare with me while I make arrangements with them. Meantime, they assisted me with getting things set up, and I thank them for that.
Various other people from various anti-spam groups have contacted me, and I thank them all for their interest in everything spam and blindness and how they come together.
Most importantly, of course, I'd like to thank all of the companies for filling my mailbox with unsolicited bulk.
Please do get in touch. In order to reach me, please write to postmaster at this domain.