December 25, 2011

L2.APEWS.ORG False Positive #10

Just over a week since the last one, found this which is the tenth in as many weeks, not bad. We know that the email sent by the server was solicited as it was a response to a web purchase, i.e. server generated receipt;

Sat 2011-12-24 06:53:43: [916:2344] Accepting SMTP connection from [83.223.106.9]
Sat 2011-12-24 06:53:43: [916:2344] Looking up PTR record for 83.223.106.9 (9.106.223.83.IN-ADDR.ARPA)
Sat 2011-12-24 06:53:44: [916:2344] D=9.106.223.83.IN-ADDR.ARPA TTL=(1440) PTR=[fusion.bpweb.net]
Sat 2011-12-24 06:53:44: [916:2344] Gathering A-records for PTR hosts
Sat 2011-12-24 06:53:44: [916:2344] D=fusion.bpweb.net TTL=(120) A=[83.223.106.9]
Sat 2011-12-24 06:53:44: [916:2344] --> 220 xxx.xxx.xxx ESMTP MDaemon 6.7.9; Sun, 25 Dec 2011 06:53:44 -0500
Sat 2011-12-24 06:53:44: [916:2344] <-- EHLO fusion.bpweb.net
Sat 2011-12-24 06:53:44: [916:2344] Performing reverse lookup on fusion.bpweb.net (looking for 83.223.106.9)
Sat 2011-12-24 06:53:44: [916:2344] D=fusion.bpweb.net TTL=(120) A=[83.223.106.9]
Sat 2011-12-24 06:53:44: [916:2344] --> 250-xxx.xxx.xxx Hello fusion.bpweb.net, pleased to meet you
Sat 2011-12-24 06:53:44: [916:2344] --> 250-ETRN
Sat 2011-12-24 06:53:44: [916:2344] --> 250-AUTH=LOGIN
Sat 2011-12-24 06:53:44: [916:2344] --> 250-AUTH LOGIN CRAM-MD5
Sat 2011-12-24 06:53:44: [916:2344] --> 250-8BITMIME
Sat 2011-12-24 06:53:44: [916:2344] --> 250 SIZE 0
Sat 2011-12-24 06:53:45: [916:2344] <-- MAIL From: SIZE=112236
Sat 2011-12-24 06:53:45: [916:2344] Performing reverse lookup on londonmagicstore.co.uk (looking for 83.223.106.9)
Sat 2011-12-24 06:53:45: [916:2344] D=londonmagicstore.co.uk TTL=(119) A=[87.117.239.236]
Sat 2011-12-24 06:53:46: [916:2344] P=050 D=londonmagicstore.co.uk TTL=(120) MX=[aspmx3.googlemail.com] {74.125.127.27}
Sat 2011-12-24 06:53:46: [916:2344] P=040 D=londonmagicstore.co.uk TTL=(120) MX=[aspmx2.googlemail.com] {74.125.43.27}
Sat 2011-12-24 06:53:46: [916:2344] P=030 D=londonmagicstore.co.uk TTL=(120) MX=[alt2.aspmx.l.google.com]
Sat 2011-12-24 06:53:46: [916:2344] P=020 D=londonmagicstore.co.uk TTL=(120) MX=[alt1.aspmx.l.google.com]
Sat 2011-12-24 06:53:46: [916:2344] P=010 D=londonmagicstore.co.uk TTL=(120) MX=[aspmx.l.google.com]
Sat 2011-12-24 06:53:46: [916:2344] D=alt2.aspmx.l.google.com TTL=(4) A=[74.125.65.26]
Sat 2011-12-24 06:53:46: [916:2344] D=alt1.aspmx.l.google.com TTL=(4) A=[209.85.225.26]
Sat 2011-12-24 06:53:46: [916:2344] D=aspmx.l.google.com TTL=(4) A=[74.125.127.26]
Sat 2011-12-24 06:53:46: [916:2344] Spam Blocker A-record resolution of [9.106.223.83.L2.APEWS.ORG] in progress (DNS Server: 192.168.1.2)...
Sat 2011-12-24 06:53:46: [916:2344] Spam Blocker D=9.106.223.83.L2.APEWS.ORG TTL=(35) A=[127.0.0.2]
Sat 2011-12-24 06:53:46: [916:2344] L2.APEWS.ORG LISTED
Sat 2011-12-24 06:53:46: [916:2344] Message will be accepted and X-RBL-Warning: header will be inserted.
Sat 2011-12-24 06:53:46: [916:2344] --> 250 , Sender ok
Sat 2011-12-24 06:53:46: [916:2344] <-- RCPT To:
Sat 2011-12-24 06:53:46: [916:2344] --> 250 , Recipient ok
Sat 2011-12-24 06:53:47: [916:2344] <-- DATA
Sat 2011-12-24 06:53:47: [916:2344] --> 354 Enter mail, end with .
Sat 2011-12-24 06:53:49: [916:2344] --> 250 Ok, message saved
Sat 2011-12-24 06:53:49: [916:2344] <-- QUIT
Sat 2011-12-24 06:53:49: [916:2344] --> 221 See ya in cyberspace
Sat 2011-12-24 06:53:49: [916:2344] SMTP session successful, 113812 bytes transferred.
Sat 2011-12-24 06:53:49: [916:2344] Shuffling message(s) into proper queue(s)
Sat 2011-12-24 06:53:49: [916:2344] Message received from fusion.bpweb.net [83.223.106.9] with SMTP for [Size 113801] {j:\localq\md0000000.msg}

As before, we will report back if this gets de-listed.

34 comments:

  1. Hello, I have an IP 93.114.46.58, that is blacklisted in your sistem:

    ------------------------------
    Oooops 93.114.46.58 is currently listed in APEWS :-(
    Entry matching your Query: E-411295
    93.114.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
    History:
    Entry created 2010-09-05
    -------------------------

    I check my ip on http://www.emailtalk.org/PTR.aspx and the result was :

    ----------------------------------------
    93.114.46.58 PTR points to eu-solution.ro.
    ----------------------------------------

    In this context I think that my IP in your sistem ar old. What can I do to resove this problem.


    I have same problem with my second IP 93.114.41.24.
    Thank you,
    Silviu

    silviuv2003@gmail.com
    silviu@eu-solution.com

    ReplyDelete
    Replies
    1. Firstly, this is just a blog to publish APEWS errors and shame them into correcting their data, better for everyone except spammers.
      The 93.114/16 seems to be registered via jump.ro and they have a bad reputation so it is not surprising to see the whole CIDR listed. You have mentioned 2 IP addresses which have the correct PTR records but the APEWS listing is for all of the 65,000+ IP addresses as a group.

      Checking for another opinion on www.senderbase.org and we can see that there are over 1,000 IP addresses currently or recently sending emails, the majority of which have either a bad reputation or no PTR record or both.

      From Whois we can see that the 2 IP addresses you refer to are allocated to Voxility SRL in 93.114.40.0/21, perhaps APEWS will update their records in some way. You can see on the www.senderbase.org website that there are bad reputation email senders from IP addresses even inside the same /24 as your 93.114.41.24 IP address. Many Administrators of private networks block 256 IP addresses, a /24, when they find abuse from a single IP address, a /32. The fact that you have your email servers in a bad neighborhood does not help your case. IP addresses like that should be very cheap to rent but if sending emails is important to you, perhaps you should consider spending more on IP addresses that are inside a good reputation CIDR? You could always smart host at least your outbound emails to have a better chance of delivery.

      Delete
    2. It looks like the good reputation IP addresses have been delisted, not the whole CIDR but at least the trusted senders, less FP then.

      Delete
  2. Hi,

    We are a fairly new ISP and have just been informed by one of our end customers that our assigned block is listed on APEWS.

    Oooops 31.22.72.0 is currently listed in APEWS :-(
    Entry matching your Query: E-504057
    31.16.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

    Can someone please remove 31.22.72.0/21, as this is a new range that has never been allocated by RIPE before.

    Thanks

    hostmaster@actimax.co.uk

    ReplyDelete
    Replies
    1. Checking this today shows that indeed the whole /21 has been delisted. Nice to see someone else get results too, thanks for posting here with the details.

      Delete
  3. Hello, im the owner of ELLOY.NET and the ip adress of it is 184.154.104.226 and since a week ago my antivirus detect that my website is blacklisted ? im not a spammer and i dont event know anything about spamm ?? all i know that im using joomla and iv got hacked 2 times twice and backed up my website but i dont know how to spamm or anything


    Now all i need is to know how to get my website back ? i mean to make it clean and remove it from the blacklist


    Thank you

    ReplyDelete
    Replies
    1. It does not help your case to post more than once. It sounds like you are operating an insecure server that has abused other internet users. If you do not have enough knowledge to secure your server you owe it to the internet community to pay a professional and get the server secured promptly.

      Delete
  4. Hi, this is owner of altayawines.com based in Hong Kong. We are legimiate company and do not spam. We are in two IP range 125.214.192.0/18 and 202.177.25.0/24, both are blacklisted according to APEWS. Would you please remove us from the block list? Thank you!

    Oooops 125.214.209.41 is currently listed in APEWS :-(
    Entry matching your Query: E-260504
    125.214.192.0/18
    CASE: C-447
    AS4515 HK, ISP permits abuse and/or ignores criminal activity
    Special Reason:
    ISP permits abuse and/or ignores criminal activity

    Oooops 202.177.25.28 is currently listed in APEWS :-(
    Entry matching your Query: E-300810
    202.177.25.0/24
    CASE: C-1342
    AS7479 HK, ISP permits abuse and/or ignores criminal activity
    Special Reason:
    ISP permits abuse and/or ignores criminal activity

    ReplyDelete
    Replies
    1. The first IP address has been delisted but strangely your other one is still listed as within the /24.

      Delete
    2. Some days ago the second IP address was also delisted

      Delete
  5. Oooops 184.11.127.158 is currently listed in APEWS :-(


    --------------------------------------------------------------------------------
    Entry matching your Query: E-620628
    184.8.0.0/13
    --------------------------------------------------------------------------------
    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-01-31
    Not sure what this is or what this is but we are local goverment. Can you please delist my address.

    ReplyDelete
  6. Testresults

    Oooops 50.196.237.9 is currently listed in APEWS :-(
    Entry matching your Query: E-505366
    50.192.0.0/10
    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,

    What's going here? Please remove.

    ReplyDelete
  7. Another listing that shouldn't be there. Hopefully this will be delisted. We're a small company whose most "bulk" email is to 200 of our associates. I guess it must be a bad neighbourhood.

    Oooops 188.39.108.130 is currently listed in APEWS :-(
    Entry matching your Query: E-635526
    188.39.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-07-12

    ReplyDelete
  8. Please remove. We DO NOT SPAM

    Oooops 46.31.82.138 is currently listed in APEWS :-(
    Entry matching your Query: E-521057
    46.24.0.0/13
    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

    ReplyDelete
  9. Hi,

    We recently moved to a new ISP, and since then our mail is being recognized as spam.
    All of our clients have the same issue: important emails go straight to the spam folder of the gmail receipent.
    Other mail providers just let it through.

    Oooops 164.138.31.65 is currently listed in APEWS :-(
    Entry matching your Query: E-469152
    164.138.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
    History:
    Entry created 2011-04-16

    ReplyDelete
  10. Hi,

    We have purchase new IP range from APNUC and we noticed that our IP has been blacklisted by APEWS. Can you please whitelist 103.26.40.0/22?


    ##########
    Oooops 103.26.42.47 is currently listed in APEWS :-(
    Entry matching your Query: E-629717
    103.26.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
    ##########

    Please contact me at support@signetique.com if you need further information.

    Thank you!

    ReplyDelete
  11. Hello,

    I recently have noticed that my IP ranges fall into ranges that are currently blacklisted. My server uses 2 different ISPs. Can you please remove the IP ranges 50.198.16.190/8 and 107.209.5.80/8?

    Oooops 50.198.16.193 is currently listed in APEWS :-(
    Entry matching your Query: E-505366
    50.192.0.0/10
    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

    Oooops 107.209.5.81 is currently listed in APEWS :-(
    Entry matching your Query: E-505390
    107.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

    Feel free to contact me at webmaster@allprowebservices.com for more information.

    Thanks!

    ReplyDelete
  12. Oooops 80.227.145.74 is currently listed in APEWS :-(
    --------------------------------------------------------------------------------
    Entry matching your Query: E-457209
    80.227.128.0/17
    --------------------------------------------------------------------------------
    CASE: C-226
    AS15802 AE, ISP permits abuse and/or ignores criminal activity
    --------------------------------------------------------------------------------
    History:
    Entry created 2011-02-06, kindly help we are small company even not sending many emails

    ReplyDelete
  13. still waiting for reply

    ReplyDelete
  14. Hello,
    IP 5.44.233.128 is currently listed in APEWS:

    Entry matching your Query: E-1151484
    5.32.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

    Our company got this new IP from our ISP, maybe old customer used it in a bad way. We're a small company, no spam activities. Can you delist it, please?

    ReplyDelete
  15. Oooops 23.226.143.99 is currently listed in APEWS :-(

    Entry matching your Query: E-1631846
    23.224.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

    I have just gottent this IP address as part of my vps subscription. I dont think this has been used for spamming in recent history. I hope it will be delisted soon.

    ReplyDelete
  16. Greetings:

    TestResults
    Oooops 187.141.13.131 currently in APEWS :-(
    Check matching your query: E-567133
    187.141.0.0/16CASE: C-131
    CIDR unassigned, assigned to traffic,
    or intended disreputable supplier
    or allocated but dynamic / generically called IPs,
    or bogons, see www.cidr-report.org,
    orphans or IP / CIDR routing in tableHistory:
    Entry created 2012-05-30

    a favor to remove my ip from their lists for my email correctly fucione

    Thank you.

    ReplyDelete
  17. Hi,

    Oooops 5.39.65.186 is currently listed in APEWS :-(
    Entry 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

    This is ip address only for our dedicaded server and service that we are providing. We definetely do not sending spam.

    ReplyDelete
  18. This comment has been removed by the author.

    ReplyDelete
  19. Hi, i've found this :

    Oooops 5.8.109.189 is currently listed in APEWS :-(
    Entry matching your Query: E-1151472
    5.8.0.0/15
    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 2014-02-18

    We have changed location so changed ip at the end of july
    , we use email to contact customer and friends

    thanks

    ReplyDelete
  20. And we are listed too:

    Oooops 176.98.166.251 is currently listed in APEWS :-(
    ________________________________________
    Entry matching your Query: E-1185642
    176.98.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 2014-03-04

    --

    Does anyone know how to get delisted?

    ReplyDelete
  21. Does anyone know how to get delisted, We purchase a new IP range from ISP

    Oooops 201.226.78.10 is currently listed in APEWS :-(
    Entry matching your Query: E-613011
    201.226.64.0/19
    CASE: C-194
    AS11556 PA, ISP permits abuse and/or ignores criminal activity
    History:
    Entry created 2012-11-19

    ReplyDelete
  22. The anti-spam service Mollom servers are on the list. Ironic.

    173.193.242.188, 174.37.205.126, 173.192.235.119, 173.192.235.120

    ReplyDelete
  23. This is the mail system at host mail.distar.com.ua.

    I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.

    For further assistance, please send mail to postmaster.

    If you do so, please include this problem report. You can delete your own text from the attached returned message.

    The mail system

    : host mxlb.ispgateway.de[80.67.18.126] said: 550 MFE:
    Message detected as spam (in reply to end of DATA command)

    Di-Star Lts ia a manufacturing company. 77.121.11.250
    On November 21st, 2014 the mail server of our company was hacked.
    Now the problem is solved.
    Please exclude us from the "bad reputation" list.
    We apologize for any inconvenience.

    ReplyDelete
  24. Hi there,

    Any idea how to proceed to remove our IPs from the blacklist? Some years ago ee purchased a range of IP from 31.193.192.0/18 but never got this problem.

    By the way, it looks pretty much to block /18. We just check the IPs reputation on senderbase a only 10 IPs from that range have bad reputation.

    Thank you in advance


    Oooops 31.193.226.119 is currently listed in APEWS :-(
    Entry matching your Query: E-1165784
    31.193.192.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

    ReplyDelete
  25. Estimated APEWS administrator , please request to remove the following IP blacklist , 201.222.83.193 , we are not spam.
    it is urgent to fail our mail some domains , thanks

    Oooops 201.222.83.193 is currently listed in APEWS :-(
    Entry matching your Query: E-613004
    201.222.80.0/21CASE: C-1028
    AS25620 BO, ISP permits abuse and/or ignores criminal activityHistory:
    Entry created 2012-11-19

    ReplyDelete




  26. Dear Administrator of APEWS
    Please kindly remove this already blacklisted IP; as it belongs to a block of IPs from our domain as an ISP

    Thank you in anticipation

    Oooops 212.100.72.153 is currently listed in APEWS :-(
    Entry matching your Query: E-325487
    212.100.72.0/24
    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-02-24

    ReplyDelete

  27. Dear Administrator of APEWS
    Please kindly remove this already blacklisted IP; as it belongs to a block of IPs from our domain as an ISP

    Thank you in anticipation


    Oooops 212.100.72.154 is currently listed in APEWS :-(
    Entry matching your Query: E-325487
    212.100.72.0/24
    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-02-24

    ReplyDelete
  28. Hello Apews Administrators,

    Since I have not gotten a fit back from you guys, I just simply want use this as a gentle reminder

    I hope you guys have a wonderful weekend

    ReplyDelete