Another user reported a newsletter in the junk folder however on checking the IP address appears to have already been delisted, publishing this false positive for the record (full email header munged where appropriate);
Wed 2013-10-02 18.13:20: [1768:723] Accepting SMTP connection from [159.220.9.56]
Wed 2013-10-02 18.13:20: [1768:723] Looking up PTR record for 159.220.9.56 (56.9.220.159.IN-ADDR.ARPA)
Wed 2013-10-02 18.13:21: [1768:723] D=56.9.220.159.IN-ADDR.ARPA TTL=(0) PTR=[mailout2-trm.thomsonreuters.com]
Wed 2013-10-02 18.13:21: [1768:723] Gathering A-records for PTR hosts
Wed 2013-10-02 18.13:21: [1768:723] D=mailout2-trm.thomsonreuters.com TTL=(60) A=[159.220.9.56]
Wed 2013-10-02 18.13:21: [1768:723] --> 220 xxx.xxx.xxx ESMTP MDaemon 6.7.9; Wed, 02 Oct 2013 18.13:21 -0500
Wed 2013-10-02 18.13:21: [1768:723] <-- EHLO mailout2-trm.thomsonreuters.com
Wed 2013-10-02 18.13:21: [1768:723] Performing reverse lookup on mailout2-trm.thomsonreuters.com (looking for 159.220.9.56)
Wed 2013-10-02 18.13:21: [1768:723] D=mailout2-trm.thomsonreuters.com TTL=(59) A=[159.220.9.56]
Wed 2013-10-02 18.13:21: [1768:723] --> 250-xxx.xxx.xxx Hello mailout2-trm.thomsonreuters.com, pleased to meet you
Wed 2013-10-02 18.13:21: [1768:723] --> 250-ETRN
Wed 2013-10-02 18.13:21: [1768:723] --> 250-AUTH=LOGIN
Wed 2013-10-02 18.13:21: [1768:723] --> 250-AUTH LOGIN CRAM-MD5
Wed 2013-10-02 18.13:21: [1768:723] --> 250-8BITMIME
Wed 2013-10-02 18.13:21: [1768:723] --> 250 SIZE 0
Wed 2013-10-02 18.13:21: [1768:723] <-- MAIL From:<x@ thomsonreuters.com> SIZE=45939
Wed 2013-10-02 18.13:21: [1768:723] Performing reverse lookup on thomsonreuters.com (looking for 159.220.9.56)
Wed 2013-10-02 18.13:22: [1768:723] D=thomsonreuters.com TTL=(0) A=[163.231.4.79]
Wed 2013-10-02 18.13:22: [1768:723] P=020 D=thomsonreuters.com TTL=(0) MX=[mailin2-tr.thomsonreuters.com] {59.144.10.241}
Wed 2013-10-02 18.13:22: [1768:723] P=020 D=thomsonreuters.com TTL=(0) MX=[mailin1-tr.thomsonreuters.com] {199.224.149.51}
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin7-tr.thomsonreuters.com]
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin6-tr.thomsonreuters.com] {159.220.48.8}
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin5-tr.thomsonreuters.com]
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin4-tr.thomsonreuters.com]
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin3-tr.thomsonreuters.com]
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin2-trp.thomsonreuters.com] {163.231.6.25}
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin2-trm.thomsonreuters.com] {159.220.9.53}
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin1-trp.thomsonreuters.com] {163.231.6.5}
Wed 2013-10-02 18.13:22: [1768:723] P=010 D=thomsonreuters.com TTL=(0) MX=[mailin1-trm.thomsonreuters.com] {159.220.28.53}
Wed 2013-10-02 18.13:22: [1768:723] D=mailin7-tr.thomsonreuters.com TTL=(0) A=[159.220.48.10]
Wed 2013-10-02 18.13:22: [1768:723] D=mailin5-tr.thomsonreuters.com TTL=(0) A=[159.220.38.28]
Wed 2013-10-02 18.13:22: [1768:723] D=mailin4-tr.thomsonreuters.com TTL=(0) A=[159.220.20.196]
Wed 2013-10-02 18.13:22: [1768:723] D=mailin3-tr.thomsonreuters.com TTL=(0) A=[159.220.16.156]
Wed 2013-10-02 18.13:22: [1768:723] Spam Blocker A-record resolution of [56.9.220.159.L2.APEWS.ORG] in progress (DNS Server: 192.168.1.2)...
Wed 2013-10-02 18.13:22: [1768:723] Spam Blocker D=56.9.220.159.L2.APEWS.ORG TTL=(35) A=[127.0.0.2]
Wed 2013-10-02 18.13:22: [1768:723] L2.APEWS.ORG LISTED
Wed 2013-10-02 18.13:22: [1768:723] Message will be accepted and X-RBL-Warning: header will be inserted.
Wed 2013-10-02 18.13:22: [1768:723] --> 250 <x@ thomsonreuters.com>, Sender ok
Wed 2013-10-02 18.13:23: [1768:723] <-- RCPT To:<xxx@ xxx.xxx>
Wed 2013-10-02 18.13:23: [1768:723] --> 250 <xxx@ xxx.xxx>, Recipient ok
Wed 2013-10-02 18.13:23: [1768:723] <-- DATA
Wed 2013-10-02 18.13:23: [1768:723] --> 354 Enter mail, end with <CRLF>.<CRLF>
Wed 2013-10-02 18.13:24: [1768:723] --> 250 Ok, message saved <Message-ID: 11D276E588427@ ERFMMBX12.ERF.thomson.com>
Wed 2013-10-02 18.13:26: [1768:723] <-- QUIT
Wed 2013-10-02 18.13:26: [1768:723] --> 221 See ya in cyberspace
Wed 2013-10-02 18.13:26: [1768:723] SMTP session successful, 46875 bytes transferred.
Wed 2013-10-02 18.13:26: [1768:723] Shuffling message(s) into proper queue(s)
Wed 2013-10-02 18.13:26: [1768:723] Message received from mailout2-trm.thomsonreuters.com [159.220.9.56] <x@ thomsonreuters.com> with SMTP for <xxx@ xxx.xxx> [Size 4859] {i:\localq\000351496.msg}
Please remove my ip 186.251.184.0/22 block the spam list
ReplyDeletemy server is 186.251.184.11 IP ns1.vipnetsul.com.br AS263003, already solved the problem of spam with a User of our network thanks
Dear Sir,
ReplyDeleteAs the ip address 58.177.253.115 is normal now. Please remove it blacklist on l2.apews.org.
Thanks a lot.
Dear Sir,
ReplyDeleteAs the ip address 58.177.253.116 is normal now. Please remove it blacklist on l2.apews.org.
Thanks a lot.
Dear Sir,
ReplyDeleteAs the ip address 202.64.174.186 is normal now. Please remove it blacklist on l2.apews.org.
Thanks a lot.
Hello There,
ReplyDeleteI just got this IP newly(203.124.116.1) and found it's blacklisted in apews.org.
Could you kindly remove it as i'm not a spammer but may be some one who used it previously years ago!!
Thanks.
Dear Sir,
ReplyDeleteour ip ( 5.134.124.136 ) since 2012 wansn't used for spam. Please, remove from the list, and please also remove armada.it from ISP with a bad reputation; we fight every day against spammers and their lamer attacks, providing to clients a (hope this true) normal and spam-free service.
Best Regards
Claudio Cosenza - Armada.it
Hello would need to deslistaran the IP 80.36.136.149 that is a mail server that is ok
ReplyDeletethank you very much
80.36.136.149 It's a false positive
DeleteDear Sir,
ReplyDeleteAs the ip address 194.149.54.252 is normal now. Please remove it blacklist on apews.org.
Horváth Szilveszter
Please, Can you remove my ip ?
ReplyDeleteOooops 187.50.76.37 is currently listed in APEWS :-(
Entry matching your Query: E-413713
187.50.0.0/16
CASE: C-41
Spambots / zombies / spammers / scanners within CIDR
Good Morning to ... whomever ???
ReplyDeleteI was informed this morning that our IP Address of 50.79.156.221 was being blocked by your service. I quick check found that the entire CIDR of 50.64.0.0/11 is listed in your service.
I cant speak for the entire CIDR but can tell you it belongs to Comcast Business Services and is distibuted to their business customers and not home customers, so spam is highly unlikely on this CIDR.
As for us, we are an emergency services organization and use mailman to distribute daily status bulletins to our memebers (California State ACS) and regional members (City and County).
Our members only are the ones receiving the messages, and not the general public (as some messages contain confidential information.)
The specific MTA mail server is n1oes.org / 50.79.156.221.
If you could remove this IP Address from your blocking, 3 of our members would love to get their mail again.
You can contact me at webmaster@n1oes.org and/or webmster@acscalifornia.org
Thank you,
Wm Lewis / M.A.R. 4 ACS Officer.
Good Morning.
ReplyDeleteAs the ip address 87.204.75.176 is normal now (was too, but entire CIDR 87.204.64.0/18 is listed in your service). Please remove it blacklist on l2.apews.org.
Thank you,
Abriel
Good morning,
ReplyDeletecould you please check:
Oooops 31.193.164.111 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
Our part 31.193.160.0 - 31.193.167.255 of this CIDR is a very young net, I think you are using an old bogons list.
BR
Markus
please delist our ip-address "46.237.200.130"
ReplyDeletespam problems solved !!
Dear Sir,
ReplyDeleteAs the ip address 202.66.82.217 is normal now. Please remove it blacklist on l2.apews.org.
Thanks a lot.
Please DE-List our mail server, domain csif.bg inc/out: mail.csif.bg; IP 84.242.134.36.... Spam problem is solved!
ReplyDeleteSMTP error from remote mail server after end of data:
host gmail-smtp-in.l.google.com [173.194.70.27]:
550-5.7.1 [84.242.134.36 1] Our system has detected an unusual rate of
550-5.7.1 unsolicited mail originating from your IP address. To protect our
550-5.7.1 users from spam, mail sent from your IP address has been blocked.
common someone to help
DeleteHi,
ReplyDeletePlease de-list 71.190.247.12 from email blacklist. I have found the infected machine and removed it from the network.
Thank you,
71.190.247.12 is currently listed in APEWS :-(Entry matching your Query: E-220312 71.190.0.0/16CASE: C-130One or more bots in ASN / CIDR, unprofessional / negligent ownerSpecial Reason:Only the ASN/CIDR owner can solve this listing by actioning FAQ 42 apews.org SHUTDOWN BOTS, ZOMBIES, NET ABUSEHistory:Entry created 2007-06-29
DeleteGhwarchitects.com
Please remove
Hello There,
ReplyDeleteI just got this IP newly(5.147.123.139) and found it's blacklisted in apews.org.
Could you kindly remove it as i'm not a spammer but may be some one who used it previously years ago!!
Thanks.
APWS: 23.21.186.79
ReplyDeletethis IP isn't a spamer please keep out the list.
This account is blocked because of a problem in 2011... We have a server since the beginning of this year using that same IP, please unblock.
ReplyDeleteThanks!
Oooops 76.76.103.210 is currently listed in APEWS :-(
Entry matching your Query: E-455746
76.76.100.0/22CASE: C-79
Spambots, zombies, contaminated CIDR, bad reputation providerHistory:
Entry created 2011-02-03
Please remove my ip 197.246.6.120/29 block the spam list
ReplyDeletemy server is 197.246.6.123
Dear Sir,
ReplyDeleteIp address 210.242.27.95 & 210.242.27.91 is normal now. Please remove it blacklist on l2.apews.org. Thanks.
.
Dear Sir,
ReplyDeleteIp address 201.158.0.18 is normal now. Please remove it blacklist on apews.org. Thanks.
Dear Sir,
ReplyDeleteIp address 210.242.27.95 is normal now. Please remove it blacklist on l2.apews.org. Thanks.
Please delist -
ReplyDelete--
Entry matching your Query: E-457241
81.23.102.0/23
--
our ip is 81.23.102.130 and we never sent out any spam
Dear Sir,
ReplyDeleteWe just found our IP (220.128.217.32 & 219.130.113.114) were blacklisted in apews.org. from http://whatismyipaddress.com/blacklist-check.
Please remove our ip from block the spam list. We're PROTOP Int’I Inc from Taiwan as normal supplier . Thank you very much for great help!
Dear Sir,
ReplyDeleteWe just found our IP "182.57.129.54" were blacklisted in apews.org.
Please remove our IP from block the spam list. our company is Architect and Civil consulting company. Please
Dear APEWS,
ReplyDeleteOur mail server with IP address 178.18.135.8, had a bad configuration allowing it to be a relay. Since then, we have a new Admin in our company, he has fixed the problem. Currently the only site blacklisting our IP address/domain is APEWS(l2.apews.org).
Can our admin get in contact with you to explain the steps he took to fix the problem, so we can get delisted? Some of our customers use APEWS and we cannot have normal mail exchange, as we have to resort using gmail instead.
Thank you for your time and help
Kind Regards
Eduardo Brigham
Oooops 178.18.135.8 is currently listed in APEWS :-(
Entry matching your Query: E-450917
178.18.128.0/17
CASE: C-14
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2011-01-18
Please removed my ip address 108.170.56.51
ReplyDeleteI test my ip in differents webs to blacklist results and only in yours i have block. This is the report.
---------------------------
Oooops 108.170.56.51 is currently listed in APEWS :-(
Entry matching your Query: E-685820
108.170.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 2013-09-25
-------------------------------
Please help me!! This ip is actually for company and all mails we send if a us registered client all they accept us politics to send mails...
Thanks a lot!!
Dear APEWS,
ReplyDeleteWe kindly request you to remove us from the blacklist as we host a mail server from our office, we are having 60 people working in office and we constantly monitor our server from attackers.
Thanking you
Best Regards
RAM
Testresults
Oooops 195.189.29.222 is currently listed in APEWS :-(
Entry matching your Query: E-270999
195.189.29.0/24CASE: C-659
AS29348 IS, ISP permits abuse and/or ignores criminal activitySpecial Reason:
ISP permits abuse and/or ignores criminal activityHistory:
Entry created 2007-07-17
Dear Support,
ReplyDeleteAs the ip address 203.194.252.0/24 is normal now. Please remove it blacklist on l2.apews.org.
Thanks a lot.
Please remove our IP address from blacklist, our IP is 186.15.140.242. Here is the report, thanks
ReplyDeleteEntry matching your Query: E-403264
186.15.128.0/17
CASE: C-22
Dynamic IP space, generic DNS/rDNS, no PTR
Direct connections to MX not permitted, you
need to use your ISP servers or smarthost
Special Reason:
Dynamic IP, generic DNS, missing rDNS/PTR not permitted for direct email connection. You must use correctly configured [with registered working abuse contact] static IP / ISP mail servers / smarthost service
History:
Entry created 2010-07-21
Please remove our IP address from blacklist, our IP is 46.26.154.102. Here is the report, thanks
ReplyDeleteEntry matching your Query: E-521057
46.24.0.0/14
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-04-13 2013-08-22: Entry changed from 46.24.0.0/13 to 46.24.0.0/14
Hi;
ReplyDeletePlease remove my server ip 85.133.147.251 from l2.apews.org ,spammer has been blocked
Please remove my ip 164.77.245.115/a block the spam list
ReplyDeletemy server is 164.77.245.116 IP mail.dragpharma.cl already solved the problem of spam with a User of our network thanks
Please remove my IP from your L2.apnews.org 50.76.25.65. I am part of Comcast business and have spam guards in place.Entry matching your Query: E-496143
ReplyDelete50.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 It appears to be other than my IP
I don't know what can I do. My company IP was listed on APEWS because we had spambot on one PC. The problem was solved yesterday but now employees have problem with mail delivery to some recipients.
ReplyDeleteEntry matching your Query: E-763332
91.219.209.41
CASE: C-1425
Spammer, scanner, scammer, zombie PC, rooted PC, other
History:
Entry created 2013-10-29
Please remove my ip of APEWS 187.72.173.237 and 187.72.173.232. The problem was solved: Entry matching your Query: E-431062
ReplyDelete187.72.0.0/15
CASE: C-41
Spambots / zombies / spammers / scanners within CIDR
History:
Entry created 2010-11-02
Please can you remove 5.159.226.25 from APEWS as it's being blocked on a false positive basis. We don't send out any spam emails and we use a reputable provider (http://www.melbourne.co.uk/).
ReplyDeleteEntry matching your Query: E-179983
5.0.0.0/8
CASE: C-1404
IP allocations to providers with a bad reputation
Special Reason:
IP allocations to providers with a bad reputation
History:
Entry created 2007-05-28 2012-05-31: Reason changed from No traffic until allocated to IP allocations to providers with a bad reputation
Please remove my ip 211.25.236.5 from block the spam list
ReplyDeletemy server is zimbra.pns.com.my already solved the problem of spam with a User of our network thanks
Please remove my ip 188.219.207.35 and 188.219.207.36 of my two servers from block list
ReplyDeleteMy mail server is kerio connect. The problem is solved on pur network.
Thanks
Dear Sir,
ReplyDeleteAs the ip address 219.83.95.195 is normal now. Please remove it blacklist on l2.apews.org.
Thanks a lot.
Abuse IM2
ASn. 4795
Hello There,
ReplyDeleteI just got this IPs in January 2013 (89.238.204.90 /91 /92 /93) and found it's blacklisted in apews.org.
Could you kindly remove them as i'm not a spammer but may be some one who used it previously years ago!! (the registrations in your database are from 2007)
Thanks.
Since, according to the introductory text of this blog, Usenet is deprecated as a communication medium, could APEWS please remove any mention of Usenet newsgroups from their FAQ? Many people still make the mistake of posting removal requests to news.admin.net-abuse.email. This happens frequently enough that some are even trying to lobby blacklist lookup Web sites to get them to remove APEWS lookups from their results. There is also frequent derision of APEWS as a blocklist and advice to just ignore it. In particular, I would say that Usenet is not a useful medium for APEWS and it's best for them not to mention it in their FAQ since it is obvious that they disregard it.
ReplyDeleteAPEWS: Thank you for modifying the FAQ. It should greatly reduce confusion, especially among those for whom English is not their native language.
DeleteOne particular case is a recent one where a non-native English speaker posted and addressed a removal request to "Jamie and team". When challenged, he said that the FAQ told him to ask "Jamie" for removal. (By the way, "Jamie" has not been heard from in years. He is probably not on the Internet anymore since even his darkshado.ca domain is gone.)
Lets hope that the drive-by posts stop in Usenet, particularly nanae. We referenced deprecated due to the loss of .sightings and .blocklists, also the increased NR ratio.
DeleteInteresting to note that the Jamie reference has also bee removed from the FAQ, see what happens, worth a try and should cut down on the blame game against Apews.org.
Please remove 187.237.95.163 and 187.237.95.164 from your blacklist, these IPs belongs to gepp.com. We recently changed our ISP provider.
ReplyDeleteThanks a lot!
Please remove 41.160.51.34 ip address from your blacklist on l2.apews.org. We recently changed our ISP provider
ReplyDeleteThanks in advance
Please Remove 70.99.206.0/23 from your list. We were hacked previously, but that has been dealt with, and reinstalled the server software. Please, kindly take us of your list.
ReplyDeletePlease remove 187.157.45.9 ip address from your blacklist. We recently changed our ISP provider.
ReplyDeleteOooops 187.157.45.9 is currently listed in APEWS :-(
Entry matching your Query: E-413734
187.128.0.0/9
CASE: C-41
Spambots / zombies / spammers / scanners within CIDR
History:
Entry created 2010-09-19
Please remove 41.226.16.0/16 & 41.226.21.0/16 from your blacklist.
ReplyDeleteEntry matching your Query: E-539093
41.226.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-05-02
-----------------------
Entry matching your Query: E-539093
41.226.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-05-02
Thanks in advance
APEWS
ReplyDeleteE=451812 65.41.192.0/20 I'm the new admin for the site and I found a machine on the network with viruses. The machine was removed from network. Thanks in advance for reviewing.
Please remove 82.165.193.192 from your blacklist.
ReplyDeleteThanks, Oscar Serrano
Oooops 82.165.193.192 is currently listed in APEWS :-(
Entry matching your Query: E-438980
82.165.193.128/25
CASE: C-17
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2010-12-22 2013-08-08: Entry changed from 82.165.193.0/24 to 82.165.193.128/25
Please, delist our range: 200.198.51.130
ReplyDeleteEntry matching your Query: E-611314
200.198.48.0/22
Tank you
Please remove IP: 203.185.133.102 and 203.185.133.103 from your blacklist.
ReplyDeleteOooops 203.185.133.102 is currently listed in APEWS :-(
Entry matching your Query: E-587119
203.185.133.0/24
CASE: C-46
Spammer / Scammer / Scanner / Zombie / other within this CIDR
History:
Entry created 2012-06-28
Thanks,
Chanachai
I am the server administrator at Knowledgestart.com. Please delist 208.43.88.115. Our company does not send SPAM. Any newsletters sent out by our company uses opt-in only lists. For more information place call me at 610.650.0448 x 112. Thanks, Kevin
ReplyDeleteOooops 208.43.88.115 is currently listed in APEWS :-(
Entry matching your Query: E-472358
208.43.88.0/24
CASE: C-630
Spambots, zombies, contaminated CIDR, bad reputation provider
Spambots, zombied PC, spam relay, generic viagra spam
Multiple abusive systems within CIDR, not stopped for several days
History:
Entry created 2011-05-10
APEWS friends. I was unable to work for many months not finding this page to warn them. Will I have been customers. I want to start again. Please unlock my server ip 65.111.180.240 . We do nothing wrong
ReplyDeleteOooops 65.111.180.240 is currently listed in APEWS :-(
Entry matching your Query: E-1230177
65.111.180.240
CASE: C-1469
Spammer, scanner, scammer, zombie PC, rooted PC, bot, etc
History:
Entry created 2014-03-12
Hi,
ReplyDeletePlease remove
65.111.180.240
problem with mailbox is resolute
Thanks.
Please remove ip 89.153.37.159
ReplyDeleteheyy help me!!
ReplyDeleteOooops 177.19.174.235 is currently listed in APEWS :-(
Entry matching your Query: E-520110
177.19.128.0/18
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-04-10
thanks man!!!!
thx you my freind
ReplyDeletehttp://jeuxjeux99.blogspot.com/
العاب سيارات هنا سوف ستجدون تشكيلة مميزة من أروع و أفضل ما يوجد في العاب سيارات يمكنك اللعب مباشرة وبسهولة تامة بدون تحميل و مرحبا بالجميع في موقع العاب سيارات .
Our MTA IP 144.76.29.37 is listed since 2013-10-29!
ReplyDeleteEntry matching your Query: E-762065
144.76.29.37CASE: C-1425
Spammer, scanner, scammer, zombie PC, rooted PC, otherHistory:
Entry created 2013-10-29
Please remove it from your list.
ReplyDeletenode808February 19, 2015 at 9:11 PM
Remove 204.153.52.2
We are a State Gov. agency. Your records show that we were blacklisted in July 2014 while none of the real blacklist sites had us listed. I believe someone maliciously added us to your list...probably due to its obscurity. Remove our IP ASAP!
Please remove my ip 177.70.110.118 block the spam list
ReplyDeletethe problem of spam with a User of our network thanks
Hello .I am IT administrator at city hall Mediaș in Romania.
ReplyDeleteOur web site is www.primariamedias.ro
Please remove our ip adress 86.125.43.100 from black list. We do not send spam.
Thank you.
E-mail that was rejected is
"Subject: failure notice
Hi. This is the qmail-send program at www.primariamedias.ro.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
:
81.181.207.91 does not like recipient.
Remote host said: 450 4.7.1 Client host rejected: cannot find your hostname,
[5.2.238.14]
Giving up on 81.181.207.91.
I'm not going to try again; this message has been in the queue too long.
"
Please remove our ip adress 198.57.179.65 from black list. We do not send spam.
ReplyDeleteThank you.
Dearest,
ReplyDeleteI come to request removal from our IP: 196.32.199.198 the Blacklist please, that this to condition our work.
Thank you
Dearest,
ReplyDeleteI come to request removal from our IP: 196.32.199.198 the Blacklist please, that this to condition our work.
Thank you
Dear team,
ReplyDeleteI write in this forum to request removal from our IP: 200.71.162.216 of your Blacklist please, this is blocking our work.
Thank you and kind regards
David Lanz
IT Director
Protokol Grupo de Informática y Telecomunicaciones
Please remove our ip adress 189.113.140.27 from black list. We do not send spam.
ReplyDeleteThank you.