[REQUEST] REMOVE Query: C-664 from APEWS

damian.k...@gmail.com

unread,

Jan 3, 2013, 10:30:44 AM1/3/13

to

We are an ISP who care about our users and we do not ignore criminal activity.
So we think that it is false positive entry.
We started using this network from 2009 and the entry is from 2007.

Our AS is 13110 and network is 77.65.0.0/17
Please doublecheck if this is not a mistake.

CASE: C-664
AS13110 PL, ISP permits abuse and/or ignores criminal activitySpecial Reason:
ISP permits abuse and/or ignores criminal activityHistory:
Entry created 2007-07-17

Rob Kelk

unread,

Jan 3, 2013, 11:14:01 AM1/3/13

to

You want news.admin.net-abuse.email - this is
news.admin.net-abuse.policy.

--
Rob Kelk, co-moderator, rec.arts.anime.info
Personal address, in ROT-13: eboxryx -ng- tznvy -qbg- pbz

Taki Kogoma

unread,

Jan 3, 2013, 11:37:40 AM1/3/13

to

On 2013-01-03, Rob Kelk <rob...@deadspam.com>
allegedly proclaimed to news.admin.net-abuse.policy:

> You want news.admin.net-abuse.email - this is
> news.admin.net-abuse.policy.

news.admin.net-abuse.email isn't the proper venue for DNSBL removal
requests either.

--
Capt. Gym Z. Quirk (Known to some as Taki Kogoma) quirk @ swcp.com
Just an article detector on the Information Supercollider.

Rob Kelk

unread,

Jan 3, 2013, 6:16:46 PM1/3/13

to

On Thu, 03 Jan 2013 11:37:40 -0500, Taki Kogoma <qu...@tenma.swcp.com>
wrote:

>On 2013-01-03, Rob Kelk <rob...@deadspam.com>
>allegedly proclaimed to news.admin.net-abuse.policy:
>> You want news.admin.net-abuse.email - this is
>> news.admin.net-abuse.policy.
>
>news.admin.net-abuse.email isn't the proper venue for DNSBL removal
>requests either.

True, but I understand that it's the newsgroup listed in the APEWS FAQ.

David Ritz

unread,

Jan 3, 2013, 11:29:52 PM1/3/13

to

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday, 03 January 2013 18:16 -0500,
in article <50e6111...@news.individual.net>,

Rob Kelk <rob...@deadspam.com> wrote:

> On Thu, 03 Jan 2013 11:37:40 -0500, Taki Kogoma <qu...@tenma.swcp.com>
> wrote:

> >On 2013-01-03, Rob Kelk <rob...@deadspam.com>
> >allegedly proclaimed to news.admin.net-abuse.policy:

>>> You want news.admin.net-abuse.email - this is
>>> news.admin.net-abuse.policy.

>> news.admin.net-abuse.email isn't the proper venue for DNSBL removal
>> requests either.

> True, but I understand that it's the newsgroup listed in the APEWS FAQ.

Have you read the APEWS FAQ? If you have, it's been too long and your
memory is faulty.

It begins:

<http://www.apews.org/?page=faq>
<quote>
Frequently Asked Questions, Comments and Answers.

Do not write requests in Usenet newsgroups, it will be better to
publish your error report complete with relevant email headers
including your IP address so that an Administrator can find it.
If your IP address is in a bad neighborhood (CIDR), inform your
Internet Service Provider (ISP). There are positive results for
some who published [12]here.
[...]
12. http://apews-user.blogspot.com/
</quote>

There is a further mentions of n.a.n-a.blocklising(RIP] and
n.an-a.email, as resonable possibilities for discussion, but notes:

<quote>
A47: [...]
Please note that these newsgroups are not our removal queues.
</quote>

As there is nowhere on Usenet, where DNSbl removal requests are
appropriate, I often point to 12., above, and Al Iverson's comments
<http://www.dnsbl.com/2007/08/what-to-do-if-you-are-listed-on-apews.html>.

Please, please, oh please, do not direct any type of DNSBL removal
requests to an Usenet discussion group, regardless of topic.
news.admin.net-abuse.email is not now, nor ever was, a DNSBL removal
queue.

Please also note, virtually all APEWS removal requests are generated
by the unwashed masses pasting their IP address into a multi-DNSbl
lookup tool, and finding that their /32 is part of a /15 APEWS
listing. In many cases, users have found the APEWS listing, because
they misconfigured their SMTP server, and reach the erronious
conclusion that their inability to _send_ email must be due to the
listing. Such lusers are invariably in over their head.

In this case, it may not be the issue at hand. Still, there is
absolutely no way anyone reading n.a.n-a.email can do anything about
it.

- --
David Ritz <dr...@mindspring.com>
Be kind to animals; kiss a shark.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (Darwin)
Comment: Public Keys: <http://dritz.home.mindspring.com/keys.txt>

iEYEARECAAYFAlDmWrQACgkQUrwpmRoS3uv5wgCgh/nnf+AHf0wsChG/xDsDMqNW
fhoAoPAsc5H1zTmowtsXQIQVdZkyMX9R
=zwnP
-----END PGP SIGNATURE-----

Rob Kelk

unread,

Jan 4, 2013, 12:51:10 PM1/4/13

to

On Thu, 03 Jan 2013 23:29:52 -0500, David Ritz <dr...@mindspring.com>
wrote:

>On Thursday, 03 January 2013 18:16 -0500,
> in article <50e6111...@news.individual.net>,
> Rob Kelk <rob...@deadspam.com> wrote:

<snip>

>> True, but I understand that it's the newsgroup listed in the APEWS FAQ.
>
>Have you read the APEWS FAQ? If you have, it's been too long and your
>memory is faulty.
>
>It begins:
>
><http://www.apews.org/?page=faq>
><quote>
> Frequently Asked Questions, Comments and Answers.
>
> Do not write requests in Usenet newsgroups, it will be better to
> publish your error report complete with relevant email headers
> including your IP address so that an Administrator can find it.
> If your IP address is in a bad neighborhood (CIDR), inform your
> Internet Service Provider (ISP). There are positive results for
> some who published [12]here.
>[...]
> 12. http://apews-user.blogspot.com/
></quote>

They've finally updated it, then. Good.

<snip>

axlq

unread,

Jan 9, 2013, 1:56:17 PM1/9/13

to

In article <alpine.OSX.2.00.1...@mako.ath.cx>,

David Ritz <dr...@mindspring.com> wrote:
>Have you read the APEWS FAQ? If you have, it's been too long and your
>memory is faulty.

>[...]

>There is a further mentions of n.a.n-a.blocklising(RIP] and

Just want to emphasize: Note that n.a.n-a.blocklisting no longer
exists. RIP indeed; it was a good newsgroup while it lasted.

-A