August 30, 2013

SPEWS Memorial Day

Every August 30th the APEWS.org website changes it's home page to show the following;

 **************************************

Today our website and our mail-servers are not available, because it is 30 August - SPEWS MEMORIAL DAY

Our beloved SPEWS operator got hit by a truck and died 30 August 2006. One of his dreams was to make the world a spam free place.
As long as spam exists we therefore recommend all of you to shutdown all mail-servers at every 30. August for 24 hours.
Be creative to make today a black day for all spammers and spam supporters and a day without mail and spam.
It is just one day in the year so it will not hurt you nor your company, but it will set a widely visible sign if enough people do so.
Our blacklists are online, but we will not display reasons for listings nor do any removals by today.
We will be back by tomorrow. APEWS - Anonymous Postmasters Early Warning System.

 **************************************

The man behind the former blacklist known as SPEWS was visionary in that he recognized that playing with dynamic listings was mot a solution, just prolonging the problem and in fact permitting both spammers and anti-spammers to continue to profit from the problem at the expenses of the general public internet users.

Instead he designed a fixed listing system that prevented the internet service providers (ISP) from recycling their IP space for profit, listing them as having a bad reputation. The SPEWS blacklist database was known to be fairly aggressive with the ISPs that ignored the spam problem whilst making money from it.

From what we know, the founder of SPEWS was not only an experienced driver but had additional training possibly as a driving instructor. He also liked to drive one of the safest cars manufactured yet, despite this, whilst driving his usual cross-country route between home and office, a truck appeared and there was a crash that left the SPEWS founder dead. That was August 30th 2006. Was there foul play?

We think that if the SPEWS founder was still alive today, he would be pleased with the progress that APEWS.org has made using his ideology and advancing it further to cover all ISPs and IPv4 space.

35 comments:

  1. I'm sure our customers that send over orders and expect a quick reply would totally understand if we turned off our email for a day!

    I think it's pretty silly that a group that doesn't seem to understand the importance of email provides blacklist services for spam filters.

    ReplyDelete
    Replies
    1. Por favor, retire meu bloco ip 189.114.0.0/16 da lista de spam
      meu servidor é 189.114.223.23 IP link01.farbe.com.br, já resolvei o problema de spam com um usuário de nossa rede.

      Delete
    2. I agree with you Anon. Its like giving a bunch of kids guns over squirt guns. And expecting them to be sensible about the usage. I agree with the ideology behind spam blocking, though disagree with the methods. There's a reason why they have many false positives. They assume an aspect of "power" and run away with it, even if they do not understand which direction to run. It isn't to insult their ideology that's the great one. And wish more were open like that. But their execution is horrid. If the government acted like this toward its people. Over APEWS with spam. Everyone would be locked outside their doors in time.

      Delete
  2. Please delist my IP: 2.228.244.243

    Thanks

    ReplyDelete
  3. Please Admin, remove this IP :

    Oooops 2.228.121.198 is currently listed in APEWS :-(


    --------------------------------------------------------------------------------
    Entry matching your Query: E-575977
    2.228.0.0/16
    --------------------------------------------------------------------------------
    CASE: C-131
    Unallocated CIDR, no traffic until allocated,
    or allocated to bad reputation provider
    or allocated but dynamic / generically named IPs,
    or bogons, see www.cidr-report.org,
    or orphaned IP / CIDR in routing table
    --------------------------------------------------------------------------------
    History:
    Entry created 2012-06-19

    ReplyDelete
  4. Hi! Please remove us (ip 195.239.80.174) from the BLACKLIST. We do not spam! we company from Russia! Thanks in advance!
    JV ARKAIM

    ReplyDelete
  5. Please remove 50.127.151.98. We are a local county government.

    ReplyDelete
  6. Hopefully, an admin from Apews will take a look at the following ranges.

    50.117.11.0/24 (50.112.0.0/12 is listed)
    23.230.0.0/16 (23.128.0.0/9 is listed)



    ReplyDelete
  7. please remove 124.199.125.0/24 and 124.199.126.0/24

    ReplyDelete
  8. Hello,

    please check the following entry:

    Oooops 31.204.122.107 is currently listed in APEWS :-(

    ----------------------------------------------------------
    Entry matching your Query: E-510709
    31.192.0.0/12
    ----------------------------------------------------------
    CASE: C-131
    Unallocated CIDR, no traffic until allocated,
    or allocated to bad reputation provider
    or allocated but dynamic / generically named IPs,
    or bogons, see www.cidr-report.org,
    or orphaned IP / CIDR in routing table
    ----------------------------------------------------------
    History:
    Entry created 2012-02-24

    As you can see the whole network 31.192.0.0/12 (RIPE NCC allocation block) is blacklisted, we are using 31.204.112.0/20. At least our /20 is regulary allocated PA space with no orphaned or dynamic addresses and regular traffic flowing.

    Thanks in advance!

    ReplyDelete
  9. PLease Remove our IP from your blacklist. 208.27.160.41
    we are currently in the process of changing host providers and this has been a result of that process.

    ReplyDelete
  10. I have another error to report. I own a block of 5 addresses I purchase from Comcast Business. The addresses are STATIC IP address and I have a valid PTR. My rDSN works fine yet you report it with a generic "dynamic IP range / no MX allowed" message which is incorrect.

    IP: 173.12.179.129 through 173.12.179.135

    ReplyDelete
  11. Please delist our IPs:
    Entry matching your Query: E-618995
    109.239.48.0/22

    There are no spambots on our network. Thank you.

    ReplyDelete
  12. Please Remove our IP from your blacklist. 187.163.97.86

    We need work!!! Please

    ReplyDelete
  13. Dear Sir,

    As the ip address 202.66.82.217 is normal now. Please remove it blacklist on l2.apews.org.

    Thanks a lot

    ReplyDelete
  14. Dear Sir,

    As the ip address 58.177.253.115 is normal now. Please remove it blacklist on l2.apews.org.

    Thanks a lot

    ReplyDelete
  15. Dear Sir,

    As the ip address 58.177.253.116 is normal now. Please remove it blacklist on l2.apews.org.

    Thanks a lot

    ReplyDelete
  16. Dear Sir,

    As the ip address 58.177.253.98 is normal now. Please remove it blacklist on l2.apews.org.

    Thanks a lot

    ReplyDelete
  17. Dear Sir,

    As the ip address 202.64.174.186 is normal now. Please remove it blacklist on l2.apews.org.

    Thanks a lot

    ReplyDelete
  18. Hello,

    I am the 82.223.148.232 server administrator.
    The SMTP service is configured properly and does not allow the sending spam.
    I wish our IP eliminated from your list, Thanks.

    --------------------------

    Oooops 82.223.148.232 is currently listed in APEWS :-(

    --------------------------------------------------------------------------------
    Entry matching your Query: E-567431
    82.223.148.0/24
    --------------------------------------------------------------------------------
    CASE: C-36
    Spammer / Scammer / Scanner / Zombie / other within this CIDR
    --------------------------------------------------------------------------------
    History:
    Entry created 2012-06-02

    ------

    Eduardo Juan
    SMJ S.L.U

    ReplyDelete
  19. Hi,

    coud you please unlist this IP please?

    Oooops 174.36.63.88 is currently listed in APEWS :-(
    Entry matching your Query: E-471265
    174.36.56.0/21
    CASE: C-258
    Spambots, zombies, contaminated CIDR, bad reputation provider
    History:
    Entry created 2011-05-02

    Regards!!

    Hugo Sanchez G.
    Asierto S.A. de C.V.

    ReplyDelete
  20. False Positive for Unallocated or dynamic IP space on range 50.64.0.0/11:

    Entry matching your Query: E-496143
    50.64.0.0/11
    CASE: C-131
    Unallocated CIDR, no traffic until allocated,
    or allocated to bad reputation provider
    or allocated but dynamic / generically named IPs,
    or bogons, see www.cidr-report.org,
    or orphaned IP / CIDR in routing table
    History:
    Entry created 2011-10-23 2012-08-26: Entry changed from 50.64.0.0/10 to 50.64.0.0/11

    This is inaccurate. The following ranges are currently in use by Comcast Business Communications as static IP space and should not be listed as unallocated.

    50.73.0.0/16
    Network
    NetRange 50.73.0.0 - 50.73.255.255
    CIDR 50.73.0.0/16
    Name CBC-ALLOC-4
    Handle NET-50-73-0-0-1
    Parent NET50 (NET-50-0-0-0-0)
    Net Type Direct Allocation
    Origin AS
    Organization Comcast Business Communications, LLC (CBCI)
    Registration Date 2011-01-06
    Last Updated 2012-03-02
    Comments
    RESTful Link http://whois.arin.net/rest/net/NET-50-73-0-0-1
    See Also Related POC records.
    See Also Related organization's POC records.
    See Also Related delegations.

    50.76.0.0/14
    Network
    NetRange 50.76.0.0 - 50.79.255.255
    CIDR 50.76.0.0/14
    Name CBC-ALLOC-4
    Handle NET-50-76-0-0-1
    Parent NET50 (NET-50-0-0-0-0)
    Net Type Direct Allocation
    Origin AS
    Organization Comcast Business Communications, LLC (CBCI)
    Registration Date 2011-01-06
    Last Updated 2012-03-02
    Comments
    RESTful Link http://whois.arin.net/rest/net/NET-50-76-0-0-1
    See Also Related POC records.
    See Also Related organization's POC records.
    See Also Related delegations.

    Please assist.
    -Ken
    CSA Tech113
    Lead Technician
    Comcast Customer Security Assurance
    csatech113@comcast.net
    csatech113@gmail.com

    ReplyDelete
  21. Dear Sir,

    Please remove the record of 113.28.51.220, the record was 2 years ago and is already back to normal. Thanks a lot.

    Best regards,
    Postmaster of 113.28.51.220

    =======================
    Oooops 113.28.51.220 is currently listed in APEWS :-(


    --------------------------------------------------------------------------------
    Entry matching your Query: E-464829
    113.28.0.0/16
    --------------------------------------------------------------------------------
    CASE: C-18
    Spambots, zombies, contaminated CIDR, bad reputation provider
    --------------------------------------------------------------------------------
    History:
    Entry created 2011-03-16

    ReplyDelete
  22. please delist 88.119.96.199 , entry from 2011 year !!!

    ReplyDelete
  23. hello. please remove 95.140.197.228 ip address for your database, it is a mail server the ministry of health of Armenia

    ReplyDelete
  24. Dear Sir,

    As the ip address 58.177.253.115 is normal . Please remove it blacklist on l2.apews.org.

    Thanks a lot

    ReplyDelete
  25. Dear Sir,

    As the ip address 58.177.253.115 is normal . Please remove it blacklist on l2.apews.org.

    Thanks a lot

    ReplyDelete
  26. Please delist our IPs:
    Entry matching your Query: E-394274
    88.49.249.0/24

    There are no spambots on our network. Thank you.

    ReplyDelete
  27. Please delist our IPs:
    Entry matching your Query: E-394274
    88.49.249.0/24

    There are no spambots on our network. Thank you.

    ReplyDelete
  28. Please delist our IPs:
    Entry matching your Query: E-394274
    88.49.249.0/24

    There are no spambots on our network. Thank you.

    ReplyDelete
  29. Please delist our IP range, this dates back to 2011

    Entry matching your Query: E-457214
    80.231.171.0/24

    ReplyDelete
  30. Dear Sir,

    As the ip address 5.56.61.163 is normal . Please remove it blacklist on l2.apews.org. We're no spammers, and we fix an initial problem on the server. Right now, all works fine.

    Thanks a lot

    ReplyDelete
  31. Please unblock this range.

    Entry matching your Query: E-505366
    50.192.0.0/10CASE: C-131
    Unallocated CIDR, no traffic until allocated,
    or allocated to bad reputation provider
    or allocated but dynamic / generically named IPs,
    or bogons, see www.cidr-report.org,
    or orphaned IP / CIDR in routing table

    Comcast Business issues static IP addresses from this block.

    ReplyDelete
  32. Please, delist our range: 200.198.51.130

    Entry matching your Query: E-611314
    200.198.48.0/22

    Tank You

    ReplyDelete