This has taken a while since there is a lot of it! By comparing our own records with listings that exist in the Apews dataset we have been able to conclude the following;
Single IP addresses that have made a direct connection to our servers in order to send spam email have also been found in C-1, C-2, C-12, C-35C-52, C-53, C-66, C-67, C-73 and C-630.
Mostly /24 listings can mostly be found in C-3, C-11, C-13, C-21, C-36, C-41, C-130, C-1375 and C-1402. These /24 generally include the above single IP addresses suggesting that they are maybe escalations.
Single IP addresses that have done port scanning, SSH probes, attempted PHP or SQL injection, password guessing, hosting landing pages that contain virus, trojan etc have only been found in C-16 and C-86.
CIDR that contain residential customers, typically have no reverse DNS and generic host names (as noted in some records by Apews) have been found in C-22, C-1010 and C-1403. These are often referred to as dynamic since they can be large DHCP pools too. These CIDR would not be RFC compliant for the sending of emails.
Other CIDR, usually larger than /24, can be found in C-14, C-15, C-17, C-18, C-20, C-79, C-258 and C-813.
apews.org does a disservice by blocking ip addresses without a way for honest companies to get themselves de-listed. We were added to the list on Dec 2010 and have no way of being removed. We had a server that was open to transfers for a period but fixed the problem as soon as we found out. Seems the only way to get off the list is to move to another IP. Our IP is not listed on other blacklists
ReplyDeleteYou are confused, APEWS does not block any emails, it is just a list like a reputation index for ipv4. Mail server administrators are free to use whatever lists and filters they want to, and here we are using l2.apews.org with good results. By your own admission you had a server incorrectly configured but connected to the internet. If you do not know how to correctly configure a server, you owe it to the internet community to contract someone that does. In this case your server's IP address was correctly listed by Apews and possibly others since it was a source of abuse. You say that your server caused abuse for "a period" which means that there is no supervision of the IP traffic. In assessing the risk of future abuse from that group of IP addresses, what has changed? As an honest company, are you offering to compensate the victims of your abuse?
DeletePlease remove Entry matching your Query: E-401773
Delete212.150.158.0/24CASE: C-13
Spambot/zombie PC and/or port scanner and/or harvester bot in CIDR.
It was listed in July 2010 and has been fixed since then.
Please remove the IP 187.4.69.218 and Entry matching your Query: E-433317
ReplyDelete187.4.64.0/20
thank you
Good day ! Please remove the IP 85.132.122.10 from your spamlist.
ReplyDeleteTestresults
Oooops 85.132.122.10 is currently listed in APEWS :-(
Entry matching your Query: E-521337
85.132.122.0/24CASE: C-15
Spambots, zombies, contaminated CIDR, bad reputation providerHistory:
Entry created 2012-04-14
Whe are the government organization !
Thank You!
Please, remover the IP 201.0.207.18 from your Blacklist.
DeleteWe change your ISP recently and get this new IP number (But is Fixed IP with registered reverse DNS).
APEWS Test Results:
Oooops 201.0.207.18 is currently listed in APEWS :-(
Entry matching your Query: E-412814
201.0.207.0/24
CASE: C-149
AS27699, ISP permits abuse and/or ignores criminal activity
History:
Entry created 2010-09-15
Thanks,
Please, remover the IP 201.0.207.18 from your Blacklist.
ReplyDeleteWe change your ISP recently and get this new IP number (But is Fixed IP with registered reverse DNS).
APEWS Test Results:
Oooops 201.0.207.18 is currently listed in APEWS :-(
Entry matching your Query: E-412814
201.0.207.0/24
CASE: C-149
AS27699, ISP permits abuse and/or ignores criminal activity
History:
Entry created 2010-09-15
Thanks,
Please, remove the below IP
ReplyDeleteEntry matching your Query: E-449889
196.38.192.0/19
CASE: C-715
Please remove the below CIDR, it is an entry since 2010:
ReplyDeleteOooops 212.150.158.90 is currently listed in APEWS :-(
Entry matching your Query: E-401773
212.150.158.0/24CASE: C-13
Spambot/zombie PC and/or port scanner and/or harvester bot in CIDRSpecial Reason:
CIDR contains at least one spammer and/or port scanner. ASN/CIDR owner can solve listing by: block TCP25 out, use TCP587 or TCP465 for client email via ISP servers, terminate accounts of abusive clientsHistory:
Entry created 2010-07-12
Please remove the below IP
ReplyDeleteEntry matching your Query: E-519884
107.20.240.0/20CASE: 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 tableHistory:
Entry created 2012-04-09
Dear APEWS!
ReplyDeleteRemove the black list the IP address of the following:
Domain : onaysan.com.tr
IP Address: 82.222.51.27
Please Help Me!!!
Thanks...
178.18.199.42 please remove from black list THANKS
ReplyDeleteHi!
ReplyDeletei just found out that 2 my IP's are listed in your spam list but i guess it's some kind of mistake. i have a lot of clients so i have to send to them all information about prices and so on. but all my emails contain the phrase "if you don’t like to receive newsletters from our company, you can unsubscribe at any time". Hope we can clear up this misunderstanding. Please remove from the blacklist the following IP:
IP 213.160.132.43
IP 178.216.8.110
Sincerely,
Natalie
I agree with person above who says you're doing a disservice. Blocking an entire /24 is reckless when there are IPs within that block that are causing no harm. All you are doing is punishing innocent and legitimate people running servers.
ReplyDeleteIf your intent is to punish a hosting service, you are still punishing me as a user of that hosting service. It is very costly and time consuming to change hosting companies. In defense of the hosting company, they can't know ahead of time whether a new user is going to be bad net citizen. Once they are found out, they are kicked off. But your database retains that info for too long. Really? Over two years?
I've checked two of my IPs and they were BL in your stupid /24 block back in Oct 2010. This is ridiculous. It was two years ago. And whoever was causing the problem is probably long gone. In any case, my individual IPs were not causing any problems because I've had them for over 5 years.
You say that you have no control over who uses your blacklist. You seem to think that releases you from any responsibility of accuracy of your BL. It doesn't. I am still caught in the middle because I have no control over which mail servers are using your BL. All this does force independent server operators to utilize big corporate hosting services who won't rely on your BL. That's all we need is an even more corporate internet.
I'm not even going to bother to ask you to remove my IPs from your BL because it will just legitimize it further. All you need to do is stop blocking large blocks of IPs and to shorten the time on the BL if no other offenses occur.
Obviously you've got an inaccurate BL when you're the only one out of 64 BLs listing my IP.
It seems that you are a bad judge of service provider, they obviously don't respect you if they allow spam to come out of an IP address so close to yours. Why don't you rent an IP from a better provider? Don't blame the list admins for your negligence or inexperience, wise up. Your IP address is being used as a human shield. The statistics from using the apews data do not support your theory. Get whitelisted with your recipients, you do have their permission don't you?
DeleteDear APEWS!
ReplyDeleteRemove the black list the IP address of the following:
Domain : dcss.ru
IP Address: 95.167.218.233 and 95.167.218.234
Testresults
Oooops 95.167.218.233 is currently listed in APEWS :-(
Entry matching your Query: E-405502
95.167.0.0/16
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-08-04
Oooops 95.167.218.234 is currently listed in APEWS :-(
Entry matching your Query: E-405502
95.167.0.0/16
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-08-04
Thanks...
How can any blacklist publish a /8? We own 103.23.188.0/22 within this range.
ReplyDeleteI'm sure someone in that /8 has a bad reputation - but that spans most of Asia Pacific region.
Oooops 103.1.1.1 is currently listed in APEWS :-(
--------------------------------------------------------------------------------
Entry matching your Query: E-180000
103.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-06-19: Reason changed from No traffic until allocated to IP allocations to providers with a bad reputation
Please remove 64.173.128.0/17. (The case information is not correct. All mail servers are static, have rDNS/PTR & allow connections.)
ReplyDeleteEntry matching your Query: E-357862
64.173.128.0/17
CASE: C-1010
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
serviceHistory:
Entry created 2008-06-20
"Static, have rDNS/PTR & allow connections" is not enough, those dns entries must not be generic. That /17 is more than 30,000+ IP addresses, every one of those will need a domain name and PTR records matching the A host records of the email servers. Only then might that CIDR get delisted. Why not change the whois and announce a dynamic block with a smaller email sending block, guarantee the working of the dns, PTR, EHLO etc of the email servers in that smaller block say a /24 to start with. That's 250 email servers to configure first, then come back here and notify everyone so that folks can check your whois and dns server configs.
DeleteOooops 196.213.152.6 is currently listed in APEWS :-(
ReplyDeleteEntry matching your Query: E-414137
196.212.0.0/14
CASE: C-715
AS3741 ZA, ISP permits abuse and/or ignores criminal activity
History:
Entry created 2010-09-20
Please delist this IP, it is to be used for a secure privately managed mail server.
Please remove from your list: 68.67.88.174
ReplyDeleteOooops 68.67.88.174 is currently listed in APEWS :-(
-----------------------------------------------------------------
Entry matching your Query: E-436320
68.67.80.0/20
-----------------------------------------------------------------
CASE: C-21
Spammer / Scammer / Scanner / Zombie / other within this CIDR
-----------------------------------------------------------------Special Reason:
CIDR contains at least one spammer and/or port scanner. ASN/CIDR owner can solve listing by: block TCP25 out, use TCP587 or TCP465 for client email via ISP servers, terminate accounts of abusive clients
-----------------------------------------------------------------
History:
Entry created 2010-12-13
These results say this entry was created in 2010. How can our IP address be on your list? We have only had it for about a month and this is September 2012. Please remove our IP from your list.
Thank you
You are currently listing 63.252.64.0/19, we have 63.252.93.0/24 within this range and have no affiliation with nor control over the other addresses within this range.
ReplyDeleteEntry matching your Query: E-330934
63.252.64.0/19
CASE: C-1402
Spambots in CIDR, little or no action by NOC
Special Reason:
Only the ASN/CIDR owner can solve this listing by actioning FAQ 42 apews.org SHUTDOWN BOTS, ZOMBIES, NET ABUSE
History:
Entry created 2008-04-29
APEWS, We have been on your black list since April and have requested 3 times to be removed. We are on no other black lists and have a server management company making sure we send out no spam. Please remove the following entry:
ReplyDeleteEntry matching your Query: E-520202
184.172.0.0/16
----------------------
CASE: C-13
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 tableHistory:
Entry created 2012-04-10
The planet has thousands of IP addresses that are not all listed, CIDRs that don't all have a good rep. Best would be to cleanup those, admittedly not as bad as a few years back. Why lease blocks to Softlayer? If you rent out IPs to bad rep guys, expect to remain listed. Taking spammer money for your profits does not entitle you to push the problem onto the rest of the internet community, those days are gone.
DeleteI am trying to delist 50.192.0.0/10, which belonged to DoD before ARIN got it back. ARIN then allocated this to Comcast.
ReplyDeleteAccording to the listing, 50.192.0.0/10 was added 1/10/2012. We did not even start using this for commercial customers until March, 2012. This /10 is used for Cable Modems, DOCSIS-based commercial customers running RIP, and MetroE customers.
We have no way of delisting this, and customers are starting to complain.
jim_romary@cable.comcast.com
abuse@comcast.net
Entry matching your Query: E-505366
Delete50.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
I would say you're in the bad rep category, we still get spam coming out of Comcast IP space both residential and "static" that generic dns. Whilst you've got that going on and the bad rep from before, in our opinion permitting further unlisted IP address space would be negligent. The days of getting virgin CIDRs and surprising the world are over, clean up what you've got first. For that 50.192/10 IP address space, why not run the outgoing emails through your existing comcast servers if you trust the clients so much.
DeleteOooops 27.254.34.148 is currently listed in APEWS :-(
ReplyDeleteEntry matching your Query: E-414071
27.128.0.0/9CASE: C-41
Spambots / zombies / spammers / scanners within CIDRHistory:
Entry created 2010-09-20
Dear team.
My IP address is blacklisted on the basis of the hosting contract beg you to remove this ip 27.254.34.148
Oooops 184.172.195.43 is currently listed in APEWS
ReplyDeletePlease Remove 184.172.195.43
please remove my ip address it is listed in APEWS
ReplyDeleteTestresults
Oooops 110.34.4.250 is currently listed in APEWS :-(
Entry matching your Query: E-411987
110.32.0.0/11CASE: C-1375
Spambots/zombies within CIDRHistory:
Entry created 2010-09-08
Please remove 217.33.166.162 it hasn't been spamming.
ReplyDeleteSome spammer set the reply address to spam@direct-golf.co.uk, so we get all the bounce backs, but we haven't sent the spam.
Entry matching your Query: E-442473
217.33.164.0/22
Please remove 188.165.200.70
ReplyDeleteEntry matching your Query: E-439149
188.165.200.0/21CASE: C-17
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2010-12-23
Please remove the below CIDR, it is an entry since 2011:
ReplyDeleteOooops 216.241.9.99 is currently listed in APEWS :-(
Entry matching your Query: E-442329
216.241.8.0/22
CASE: C-15
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2011-01-01
Please do not remove any CIDR so soon you APEWS site will be considered as the biggest spammer in the world.
ReplyDeleteA different kind of spam: Catalog as spammers IPs that are not and never have been spammers.
Please remove 184.11.127.158 the problem was fixed. We are local government
ReplyDeleteEntry matching your Query: E-480388
184.0.0.0/10
--------------------------------------------------------------------------------
CASE: C-1404
IP allocations to providers with a bad reputation
--------------------------------------------------------------------------------
History:
Entry created 2011-07-21
Please remove 77.79.110.68
ReplyDeleteOooops 77.79.110.68 is currently listed in APEWS :-(
Entry matching your Query: E-598773
77.79.96.0/20
CASE: C-258
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2012-08-21
Please remove 62.99.66.170
ReplyDeleteOooops 62.99.66.170 is currently listed in APEWS :-(
--------------------------------------------------------------------------------
Entry matching your Query: E-286508
62.99.0.0/17
Thanks
Please remove 2.139.218.202
ReplyDeleteOooops 2.139.218.202 is currently listed in APEWS :-(
Thanks
He, can you please clear the IP 96.30.49.164. It is currently listed in APEWS Database.
ReplyDeleteThanks
Hello, can you please remove the IP: 96.9.170.139, is currently listed in APEWS Database with CASE: C-18 Spambots, zombies, contaminated CIDR, bad reputation provider
ReplyDeleteEntry matching your Query: E-463673
96.9.160.0/20
Please remove the IP 190.11.195.132 which was solved mass sending emails.
ReplyDeleteCASE: C-176
AS6140 AR, ISP permits abuse and/or ignores criminal activity
Can you lease remove the IP 202.89.55.218 from the list?
ReplyDeleteEntry matching your Query: E-461033
202.89.48.0/21
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
Can you lease remove the IP 117.102.9.0/24
ReplyDeleteEntry matching your Query: E-327566
CASE: C-1375
Spambots/zombies within CIDR
Good day.
ReplyDeletePlease remove the IP 37.228.68.157 from the list.
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-03-10
Hello. Please remove th ip 37.228.68.157.
ReplyDeleteEntry matching your Query: E-513212
37.128.0.0/9
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-03-10
Thanks.
Please remove the IP 187.9.127.60
ReplyDelete187.9.127.60 is currently listed in APEWS
Entry matching your Query: E-413667
187.8.0.0/15
CASE: C-41
Spambots / zombies / spammers / scanners within CIDR
History:
Entry created 2010-09-19
Please Remove: 187.213.111.248
ReplyDeleteEntry matching your Query: E-413734
187.128.0.0/9
CASE: C-41
Spambots / zombies / spammers / scanners within CIDR
Please remove 216.165.241.78
ReplyDeleteWe recently were assigned this ip address. It is only for browsing, our email address is 63.149.241.133
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
Please Remove the IP: 92.253.101.45
ReplyDeleteEntry matching your Query: E-320874
92.253.0.0/17
CASE: C-1403
this is used in a hospital
hi, how can i know if my IP address has been removed or not? it's 92.253.101.45
ReplyDeletethanks
Please remove the ip 190.14.48.170
ReplyDeleteEntry matching your Query: E-625516
190.14.48.0/24
CASE: C-34
please remove th e ip 185.2.100.49
ReplyDeleteEntry matching your Query: E-180028
185.0.0.0/8
CASE: C-1404
IP allocations to providers with a bad reputation
Special Reason:
No traffic until allocated
History:
Entry created 2007-05-28
Please remove the IP 203.127.95.242 and 1.9.130.18 from your blacklist
ReplyDeleteTestresults
Oooops 203.127.95.242 is currently listed in APEWS :-(
Entry matching your Query: E-440771
203.127.64.0/18
CASE: C-15
Spambots, zombies, contaminated CIDR, bad reputation provider
Testresults
Oooops 1.9.130.18 is currently listed in APEWS :-(
Entry matching your Query: E-406345
1.0.0.0/8
CASE: C-1404
IP allocations to providers with a bad reputation
Thanks
Please remove IP address 96.254.71.145
ReplyDeleteWe got a virus (BOT) from a DnB spam email. All PCs and our server have been disinfected and we have been remove from all black lists except APEWS.
Thanks and happy 2014
Oooops 96.254.71.145 is currently listed in APEWS :-(
Entry matching your Query: E-439504
96.254.64.0/19CASE: C-17
Spambots, zombies, contaminated CIDR, bad reputation providerHistory:
Entry created 2010-12-24
Please remove the IP 195.112.120.157 and Entry matching your Query: E-303627
ReplyDelete195.112.96.0/19
thank you
kindly remove this because this is email server 125.209.123.180
ReplyDeletePlease remove the IP 203.150.231.110 and Entry matching your Query: E-493460
ReplyDelete203.150.0.0/16
thank you
Please remove IP 178.63.64.197
ReplyDeleteEntry matching your Query: E-431412 178.63.64.0/24
Thanks!
Buenas tardes. No tenemos ni idea de porque estamos aquí, ya que no enviamos correos publicitarios ni envíos masivos, tan solo en navidad enviamos una felicitación a nuestros clientes y lo hacemos con una empresa que se dedica a esto y nos asegura que no supone ningún riesgo.
ReplyDeleteContratamos en Diciembre de 2013 una IP fija y ahora nos vemos que no podemos conectar con nuestro servidor de correo y parece ser por esto.
Puede alguien ayudarnos y decirnos como tenemos que eliminar:
CASE: C-1375
Spambots/zombies within CIDR
History:Entry created 2010-08-26
Muchas gracias anticipadas.
Un saludo.
Jorge.
Veo que esto ha escrito lo que ha querido.
DeletePedimos ayuda para eliminar lo que parece ser un virus:
CASE: C-1375
Spambots/zombies within CIDR
History: Entry created 2010-08-26
Agradecidos de antemano.
Saludos.
Jorge.
Buenas tardes. No tenemos ni idea de por que estamos aqui, ya que No enviamos correos publicitarios ni envíos Masivos, solo en navidad enviamos una felicitación a nuestros clientes y lo hacemos con una empresa que se dedica a esto y nos Asegura que no supone ningún riesgo.
ReplyDeleteContratamos en Diciembre de 2013 una IP fija y Ahora nos vemos que no podemos conectar nuestro con nuestro servidor de correo.
Por favor podría alguien ayudarnos y decirnos como tenemos que eliminar:
CASO: C-1375
/ spam zombies dentro CIDR
Historia: el registro Creado 2010-08-26
Muchas gracias Anticipadas.
Un saludo.
Jorge.
Please remove
ReplyDeleteOooops 212.219.197.129 is currently listed in APEWS :-(
Entry matching your Query: E-441734
212.219.192.0/19
CASE: C-15
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2010-12-30
Please unblock 212.219.197.129 is currently listed in APEWS :-(
ReplyDeleteEntry matching your Query: E-441734
212.219.192.0/19
CASE: C-15
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2010-12-30
Please can you confirm when 212.219.197.129 is removed.
ReplyDeleteThank you.
This comment has been removed by the author.
ReplyDeletePlease unblock 5.56.63.140 is currently listed in APEWS
ReplyDeleteEntry matching your Query: E-1151484
5.32.0.0/11CASE: 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 tableHistory:
Entry created 2014-02-18
Please can you confirm when is removed
Please unblock 202.10.95.58 which is currently listed in APEWS.
ReplyDeleteEntry matching your Query: E-380046
202.10.80.0/20
CASE: C-1010
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 2009-02-18
Hi Please de list us
ReplyDeleteOooops 123.231.72.150 is currently listed in APEWS :-(
Entry matching your Query: E-614279
123.231.64.0/18
CASE: C-15
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2012-11-28
We are a government funded project.
Not spammers!
Thanks
Hi Guys,
ReplyDeleteCan you please remove this ip address : 202.10.86.51 from your list.
We have just brought up a server on it and I can assure that no other email server has been used on this ip address within last 3 years.
YOur help is appreciated,.
The arrogance of admin, and the fruitless requests of those of us honest mail admins being held captive is nothing less than comical. I've spent the greater part of a day trying to figure out how to get delisted from a listing that was created on apews in 2010, a full 4 years ago. Interesting that only 1 of 65+ blacklists would have us listed. Apparently the other 64 or so actually will delist servers after a period of time has past with no activity, or any further activity. Since I am not having any issues sending or receiving email I am not even going to ask for you to remove my ip's. seeing as though the apews service is irrelevant in the first place.
ReplyDeleteHello Dear,
ReplyDeletePlease delist or remove my IP address from your blacklist or tell me the process how I can remove my IP address from l2.apews.org
Entry matching your Query: E-413469
117.192.0.0/11
CASE: C-41
Spambots / zombies / spammers / scanners within CIDR
thx you my friends
ReplyDeletehttp://jeuxjeux99.blogspot.com/
العاب سيارات هنا سوف ستجدون تشكيلة مميزة من أروع و أفضل ما يوجد في العاب سيارات يمكنك اللعب مباشرة وبسهولة تامة بدون تحميل و مرحبا بالجميع في موقع العاب سيارات .
Kindly remove/delist us from your list. Reason: APEWS FAQ: Q42
ReplyDeleteTemporary move from primary to secondary IP address due to ISP downtime of primary line.
Entry matching your Query: E-437858
78.*.*.*/19
CASE: C-17
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2010-12-20
Hi Please de list us
ReplyDeleteOooops 212.175.223.135 is currently listed in APEWS :-(
Entry matching your Query: E-448884
212.175.220.0/22
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
Hi Please de list out IP
ReplyDeleteOooops 82.141.163.114 is currently listed in APEWS :-(
Entry matching your Query: E-457892
82.141.160.0/22
CASE: C-20
Spambots, zombies, contaminated CIDR, bad reputation provider
History:
Entry created 2011-02-08
Thanks for your help!
Hi Please delist our IP
ReplyDeleteOooops 135.196.135.101 is currently listed in APEWS :-(
Entry matching your Query: E-349688
135.196.128.0/17CASE: C-1403
Dynamic IP space, generic DNS/rDNS, no PTR
Direct connections to MX not permitted, you
need to use your ISP servers or smarthostSpecial 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 serviceHistory:
Entry created 2008-05-20
I am with a Service Provider who was granted a block of 8 class C's in December of 2014. I have 1 customer who's Ip address appears to be on your site. Since we did not have this address at the time of the incident below please remove this address 104.244.150.56 from your blacklist. Thanks
ReplyDeleteOooops 104.244.150.46 is currently listed in APEWS :-(
Entry matching your Query: E-180001
104.0.0.0/8
CASE: C-1404
IP allocations to providers with a bad reputation
Special Reason:
No traffic until allocated
History:
Entry created 2007-05-28
por favor pueden borra de su lista el IP 190.129.85.174, gracias
ReplyDeletePlease delist
ReplyDeleteOooops 187.191.27.143 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