Discussion:
[Usenet] RFD - Newshosting - Highwinds-Media.com
(too old to reply)
Richard Leslie
2008-12-25 03:50:12 UTC
Permalink
Dear Admins,

Request for Discussion - Newshosting.com - Highwinds-Media.com

Since 11-16-2008 complaints to Newshosting and/or Highwinds-Media
concerning the abuse posted through simonconsulting.at of usenet
groups have gone ignored. Both Newshosting and Highwinds seem
unwilling to
address this ongoing abuse.

Simonconsulting.at had never responded to any complaints.
Newshosting and Highwinds-Media were contacted as the upstream
provider because of this issue.

Note:
Simonconsulting.at is both the usent provider and web hosting ISP for
the posting site in question. (fets.com)

Responses from Highwinds and Newshosting:

[Ticket #664879] [11-17-08]
Thank you for contacting Highwinds Abuse. The post in question was
not posted by one of our customers. You will need to contact the
Usenet provider of the poster indicated in the "X-Complaints-To"
section of the header. Please refrain from sending us complaints
that do not concern one of our customers.

Thank you,
Highwinds Abuse Department

[Ticket #669988] [11-24-08]
Thank you for contacting Newshosting Support. The posts in question
did not originate from one of our customers. You will need to
contact the Usenet provider of the poster. This information can be
found in the 'X-Complaints-To' portion of the headers you have sent.

Thank you,
Newshosting Abuse Department

[Ticket #669991] [11-24-08]
Thank you for contacting Highwinds Abuse. The posts in question were
not posted by a customer of ours. You will need to contact the
Usenet provider of the poster. This information can be found in the
'X-Complaints-To' section of the header.

Thank you,
Highwinds Abuse Department

[Ticket #672493] [11-25-08]
Again, the post in question did not originate from any of our
customers. You need to contact the provider of the poster, which
again, WE ARE NOT. If you continue to Spam us with false complaints
all further emails from you will be rejected.

Thank you,
Highwinds Abuse Department

[Ticket #672493] [11-25-08]
Out of curiosity, what correspondences have you received from Simon
Consulting when trying to contact their abuse department? We can not
take individual complaints concerning another company's customers.
However, if Simon Consulting is not responding and taking the
appropriate action they should be, we can consult with them
concerning their lack of handling abuse issues properly. Please
provide us with any correspondences you have had with Simon
Consulting so that we can investigate the matter. Please include any
tickets numbers.

Thank you,
Highwinds Abuse Department

Response to this ticket was that simonconsulting had never responded.

On 11-28-08 Otto J Simon responded to a report sent in:

Dear Richard Leslie,

After reviewing FETS' postings, we consider them as fully legit and
don't think they are spam. That means we will not take any further
action. We are also asking you to stop reporting to us this kind of
Usenet content.

Kind regards,

Otto J. Simon

I then received the following from Brad through Highwinds-Media:

[Ticket #672493] [12-01-08]
Hello. We spoke with Simon Consulting as they are the ones in which
you need to send your complaints. They said that the content is
legit. If you need any further information, you will need to contact
them directly. This will be our last correspondence regarding your
complaints.

Thanks,
Brad

As of 12-07-08 I am no longer receiving auto-akn from either
Newshosting / Highwinds, it would appear that I'm being routed to
dev/nul for any correspondence to them.

I have submitted reports for other abuses not related to this issue
with the same negative response.

I believe that nothing will be done unless pressure is applied from
several sources in the internet community.

Respectfully submitted,

Richard Leslie
yourfriend
2008-12-25 21:30:39 UTC
Permalink
{big snip}
Post by Richard Leslie
Respectfully submitted,
Richard Leslie
suggestion: provide a list msg-id's showing the (alleged) abuse in a follow up
Richard Leslie
2008-12-26 04:34:54 UTC
Permalink
On Thu, 25 Dec 2008 13:30:39 -0800, yourfriend
Post by yourfriend
{big snip}
Post by Richard Leslie
Respectfully submitted,
Richard Leslie
suggestion: provide a list msg-id's showing the (alleged) abuse in a follow up
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My apologies.

The original posting originated from Cogeco Cable on Nov 10 & 12,
2008.

Message-ID: <***@216.221.81.119>
Message-ID: <***@216.221.81.119>
Message-ID: <***@216.221.81.119>
Message-ID: <***@216.221.81.119>

The postings were in the 100's on each day, and produced a BI:

11-10-08 : BI=112.5865
11-12-08 : BI=363.7410

This is what triggered my attention. Report sent to Cogeco returned a
favorable response and the posting stopped for almost a week. The
poster then started posting again through simonconsulting, (also the
web host) but at a reduced rate. Currently the postings are from 2-5
per day x 3 groups. The 45 day BI is currently 718.8215.

The request for Discussion was more for the way that Highwinds and
Newshosting handles (or lack of) requests regarding reseller feeds.
Since there had been no response from Simonconsulting and they are
the usenet provider for said.

The response for both Newshosting and Highwinds has always been:

"Thank you for contacting Newshosting Support. The posts in question
did not originate from one of our customers. You will need to
contact the Usenet provider of the poster."

"Thank you for contacting Highwinds Abuse. The posts in question
were not posted by a customer of ours. You will need to contact the
Usenet provider of the poster."

So it's been a endless circle of nothingness.

Regards,

Richard Leslie


Below I have listed a sample of the recent messages in question.

Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>
Message-ID: <***@69.16.176.253>

Loading...