Please remove our range from spews S3046
briant
have removed the spammer from his network. None of the following sites
are active. Please remove our ip ranges from spews.
Please let us know if any active site still exist on 209.128.78.0 range
and we will continue to work with our customer to ensure that they will
all be removed.
http://209.128.78.29/call8/assets/cdsetup9.exe
http://www.trendhost.org/download1/pap1/index.html
http://209.128.78.29/build7/index.php
http://209.128.78.29/tekk5/index.php
https://www.clearcredit.com/registration/default.asp?cpID=c02248p2402&n=b
http://www.promohost.org/download1/
http://www.promohost.org/download1/AFFCODE/index.html
http://209.128.78.29/tekk5/index.php
http://www.fullhost.org/softsite/dnp2/index.html
http://www.fullhost.org/softsite/dnp2/cdlg.gif
fullhost and reliahost are all part of promohost.org. We don't find any
reference between these providers and our customer.
If you find any backdoor or active site to this customer of our, please
let us know. We appreciate for your help.
BAIS NOC
--
Comments posted to news.admin.net-abuse.blocklisting
are solely the responsibility of their author. Please
read the news.admin.net-abuse.blocklisting FAQ at
http://www.blocklisting.com/faq.html before posting.
yukio
"briant" <bri...@bayarea.net> wrote in message
news:40D7398...@bayarea.net...
> Our support staffs have gone through the following list. Our customer
> have removed the spammer from his network. None of the following sites
> are active. Please remove our ip ranges from spews.
> Please let us know if any active site still exist on 209.128.78.0 range
> and we will continue to work with our customer to ensure that they will
> all be removed.
You are back on the SBL for hosting the shareyourexperiences spammers
(again).
http://www.spamhaus.org/sbl/sbl.lasso?query=SBL16113
Actions, bucky....actions.
briant
complaint arrive from machine 209.128.108.231, customer will take down
machine.
Please remove our range from S3046
BAIS NOC
briant
from SPEWS listing. 209.128.64.0/23 209.128.78.0/24
BAIS NOC
Perusion Hostmaster
> We have taken down server 209.128.108.231. Please remove our IP range
> from SPEWS listing. 209.128.64.0/23 209.128.78.0/24
You know that people here don't like top-posting, yet you still do it.
This might be the reason that SPEWS is not doing anything -- they might
be like me; I often ignore top-posters.
You still refuse to explain what you have done that would mitigate
this listing.
You claimed to have terminated the customer only to have them *again*
spam -- in fact, I complained to you myself about a spam after you showed
up here claiming to have booted them.
SPEWS, I recommend you keep this top-posting person in your list until
such time as they gain a clue. They need to explain who the customer
is/was, who the reseller is/was, and why the spammer showed up again
after BAIS claimed they were terminated.
>
> BAIS NOC
>
> briant wrote:
>> Our customer has removed the spammer from his network. If further spam
>> complaint arrive from machine 209.128.108.231, customer will take down
>> machine.
>>
>> Please remove our range from S3046
>>
>> BAIS NOC
>>
>> yukio wrote:
>>
>>> "briant" <bri...@bayarea.net> wrote in message
>>> news:40D7398...@bayarea.net...
>>>
>>>> Our support staffs have gone through the following list. Our customer
>>>> have removed the spammer from his network. None of the following sites
>>>> are active. Please remove our ip ranges from spews.
>>>> Please let us know if any active site still exist on 209.128.78.0 range
>>>> and we will continue to work with our customer to ensure that they will
>>>> all be removed.
>>>
>>>
>>>
>>> You are back on the SBL for hosting the shareyourexperiences spammers
>>> (again).
>>>
>>> http://www.spamhaus.org/sbl/sbl.lasso?query=SBL16113
>>>
>>> Actions, bucky....actions.
>>>
>>>
>>
>
--
Prove you aren't stupid. Say NO to Passport.
The Open Sourceror's Apprentice
news:slrnce1ko8...@bill.heins.net:
> You know that people here don't like top-posting, yet you still do it.
> This might be the reason that SPEWS is not doing anything -- they might
> be like me; I often ignore top-posters.
Honestly, I doubt that SPEWS ignores him. I'm sure he's missing something,
but I don't know what it is.
Perhaps if he *didn't* top-post, someone would take the time to help him
figure out what he's still missing.
--
Tired of spam in your mailbox?
Come to http://www.spamblocked.com
. . .
Who is Brad Jesness? http://www.wilhelp.com/bj_faq/
Shmuel (Seymour J.) Metz
at 11:59 PM, briant <bri...@bayarea.net> said:
>We have taken down server 209.128.108.231. Please remove our IP
>range from SPEWS listing. 209.128.64.0/23 209.128.78.0/24
Have you taken down the customer, or just the server?
--
Shmuel (Seymour J.) Metz, truly insane Spews puppet
<http://patriot.net/~shmuel>
Unsolicited bulk E-mail will be subject to legal action. I reserve
the right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spam...@library.lspace.org
briant
policy on spamming themselve. And if spammer exist in their network,
they will try to remove that spammer from their network.
Shmuel (Seymour J.) Metz wrote:
> In <40E03BEE...@bayarea.net>, on 06/28/2004
> at 11:59 PM, briant <bri...@bayarea.net> said:
>
>
>>We have taken down server 209.128.108.231. Please remove our IP
>>range from SPEWS listing. 209.128.64.0/23 209.128.78.0/24
>
>
> Have you taken down the customer, or just the server?
>
--
The Open Sourceror's Apprentice
> Server has been shutdown, not the customer. Our customer have strict
> policy on spamming themselve. And if spammer exist in their network,
> they will try to remove that spammer from their network.
If outright cancellation of services fails, well, there is no problem which
cannot be solved by the proper application of sufficient quantities of high
explosive.
Or, to paraphrase Yoda: "Try? There is no try. Either remove, or not remove."
I think SPEWS works on a strictly tit-for-tat basis: You remove the spammer,
SPEWS removes the listing. SPEWS is more patient and kind than I am.
--
Tired of spam in your mailbox?
Come to http://www.spamblocked.com
. . .
Who is Brad Jesness? http://www.wilhelp.com/bj_faq/
--
ru.ig...@usask.ca
>Server has been shutdown, not the customer. Our customer have strict
>policy on spamming themselve. And if spammer exist in their network,
>they will try to remove that spammer from their network.
>Shmuel (Seymour J.) Metz wrote:
>> In <40E03BEE...@bayarea.net>, on 06/28/2004
>> at 11:59 PM, briant <bri...@bayarea.net> said:
>>
>>>We have taken down server 209.128.108.231. Please remove our IP
>>>range from SPEWS listing. 209.128.64.0/23 209.128.78.0/24
>>
>> Have you taken down the customer, or just the server?
I think it might be helpful if you, briant, differentiated customers
in your responses. It seemed to me the question assumed that your
customer was the spammer (effectively, it was), rather than the
spammer being a customer of your customer. I assume from your
response that the server was being used by the customer of your
customer, and that is why you didn't terminate your customer.
If that is the case, the logical question is the extension of
the question: did the spamming customer get terminated or just
did it just lose the server?
This matters. You are being held responsible for the spamminess
of your customer, and you are (should be) holding your customer
responsible for the spamminess of their customer. If you are
demonstrating that you do clamp down on your customers for their
spamminess, you might be given some lattitude while your customer
remains in the block list, e.g. if you are willing to summarily
yank servers used by your customer's customer. The problem is,
if all your customer did was ask you to yank the server, BUT
didn't terminate their spamming customer, there is a good chance
that SPEWS will keep them (and hence, possibly you) listed. The
IP and server matters a fair bit less than the presence of a
known spammer's account in a system. So the question is really
is, did the spammer's account get taken down or just his server?
ru
--
I am not SPEWS.
phil-new...@ipal.net
| Server has been shutdown, not the customer. Our customer have strict
| policy on spamming themselve. And if spammer exist in their network,
| they will try to remove that spammer from their network.
Try? How can trying possibly fail, unless they don't have control over
their own network?
--
-----------------------------------------------------------------------------
| Phil Howard KA9WGN | http://linuxhomepage.com/ http://ham.org/ |
| (first name) at ipal.net | http://phil.ipal.org/ http://ka9wgn.ham.org/ |
-----------------------------------------------------------------------------
Shmuel (Seymour J.) Metz
at 10:32 PM, ru.ig...@usask.ca said:
>I think it might be helpful if you, briant, differentiated customers
>in your responses. It seemed to me the question assumed that your
>customer was the spammer
Not really; it just assumed that SPEWS wouldn't accept plausible
deniability as an excuse, and that if the customer was unable to stay
clean then SPEWS wanted him gone, whether the reason was incompetence,
negligence or pink contracts. I'm still waiting for an explanation
from Briant as to what he and his customer have done to prevent a
recurrence, and I suspect that SPEWS is just as interested in the
answer as I am.
--
Shmuel (Seymour J.) Metz, truly insane Spews puppet
<http://patriot.net/~shmuel>
Unsolicited bulk E-mail will be subject to legal action. I reserve
the right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spam...@library.lspace.org
--
Rex Karz
> Server has been shutdown, not the customer. Our customer have strict
> policy on spamming themselve. And if spammer exist in their network,
> they will try to remove that spammer from their network.
>
>> [snip]
>> Have you taken down the customer, or just the server?
>>
>
--
The email address in the From: line of this message is a
spamtrap. Mail sent to this address may get the sender's
mailserver listed in one or more DNSBLs. -- Rex Karz
briant
And if necessary, they will take down the machine to prevent any further
spamming from happening.
We have been working with our customers to try to trace any possible
spamming sources for the past few weeks.
If something is missing that we are not aware of, we will be happy to
get any feedback or comments.
BAIS NOC
--
Mike Andrews
> Our customer is very proactive about responding to our abuse request.
> And if necessary, they will take down the machine to prevent any further
> spamming from happening.
> We have been working with our customers to try to trace any possible
> spamming sources for the past few weeks.
> If something is missing that we are not aware of, we will be happy to
> get any feedback or comments.
> BAIS NOC
Briant,
=================================================================
== ==
== You have been asked _several_ times to stop top-posting ==
== -- that is, to put your responses _AFTER_ the text ==
== to which you are responding. One last time: _Please_ ==
== _Stop_ _Top-posting_. ==
== ==
=================================================================
As to your customers and their "possible spamming sources", use the
complaints that you and they doubtless have. Terminate the spammers
and post notices here that you have done so. Where the spammer had a
machine all to him/her/itself, disconnect that machine and post a
notice here that you have done so.
If your customers were proactive about abuse requests, then you would
not have to make them. If your customer were proactive about stopping
abuse, then you would not have to ask your customer to stop the abuse.
Your customer appearently is not at all proactive about abuse.
--
Mike Andrews
mi...@mikea.ath.cx
Tired old sysadmin
Shmuel (Seymour J.) Metz
at 03:08 AM, briant <bri...@bayarea.net> said:
>Our customer is very proactive about responding to our abuse request.
They need to start acting decisively and expeditiously on complaints
sent by spam victims, instead of ignoring them until you complain.
Even that wouldn't qualify as proactive; for that word to apply they
would need to salt spamtrap addresses, monitor outgoing traffic, etc.,
in order to catch some spam before any complaints come in.
--
Shmuel (Seymour J.) Metz, truly insane Spews puppet
<http://patriot.net/~shmuel>
Unsolicited bulk E-mail will be subject to legal action. I reserve
the right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to spam...@library.lspace.org
--
briant
to prevent further spamming, they removed the server 209.128.108.231
from their network.
--
briant
No try,
The spammer has been removed from our customer's network.
Rex Karz wrote:
> briant wrote:
>
>> Server has been shutdown, not the customer. Our customer have strict
>> policy on spamming themselve. And if spammer exist in their network,
>> they will try to remove that spammer from their network.
>>
> There is no try. There is only do. -- Yoda
>
>>> [snip]
>>> Have you taken down the customer, or just the server?
>>>
>>
>
>
--
briant
from the listing.
Thanks,
Mike Andrews
> We haven't receive a respond on this issue yet. Please help remove us
> from the listing.
SPEWS _will_ _not_ respond. Read the FAQ at http://www.spews.org.
We can not remove you from the listing.
If you're listed, you may be able to remove yourselves from the
listing by changing your ways and making a public statement to that
effect,
If your upstream is listed, then your upstream may be able to remove
itself in the same way.
But _we_ who read NANABl and comment in that group can only observe
and advise.
--
Mike Andrews
mi...@mikea.ath.cx
Tired old sysadmin
--
The Open Sourceror's Apprentice
> We haven't receive a respond on this issue yet. Please help remove us
> from the listing.
What part of the SPEWS FAQ did you fail to grasp? This part?
"Q36: Where can I go and see discussions about SPEWS, spam and other email
abuse issues.
"A36: The Usenet has newsgroup forums for this, there is a SPAM-L mailing
list, SpamCop.net has a mailing list and User Forum. Note that posting
messages in these newsgroups & lists will not have any effect on SPEWS
listings, only the discontinuation of spam and/or spam support will."
Or this part?
"Q41: How does one contact SPEWS?
"A41: One does not. SPEWS does not receive email - it's just an automated
system and website, general blocklist related issues can be discussed in
the public forums mentioned above. The newsgroups news.admin.net-
abuse.blocklisting (NANABL) and news.admin.net-abuse.email (NANAE) are good
choices. Google makes it quite easy to post messages via the Web in the
unmoderated NANAE group. Newsreader software should be used to post to the
prefered moderated NANABL group. First time newsgroup posters should read
the NANAE FAQ. Note that posting messages in these newsgroups & lists will
not have any effect on SPEWS listings, only the discontinuation of spam
and/or spam support will. Be aware that posting ones email address to any
publicly viewable forum or website makes it instantly available to
spammers. If you're concerned about getting spammed, change or "mung" the
email address you use to post with."
The only "respond" you're going to get will be a delisting *when SPEWS is
satisfied that you aren't supporting spam any more.*
--
Tired of spam in your mailbox?
Come to http://www.spamblocked.com
. . .
Who is Brad Jesness? http://www.wilhelp.com/bj_faq/
--
chrisgreville
> We haven't receive a respond on this issue yet. Please help remove us
> from the listing.
>
> Thanks,
>
> briant wrote:
> > Our customer did removed the spammer from their network, further more,
> > to prevent further spamming, they removed the server 209.128.108.231
> > from their network.
> >
<SNIP Top Posting>
Might I ask what bit of "Please do NOT top post" do you not understand?
You have been asked many times before not to do it, yet you persist in
continuing in top posting. It makes following your answers to specific
questions (when you bother to answer them) very hard to understand.
Might I add that once again you */read/* and */understand/* the Spews FAQ
that specifically states that Spews is an automated system that contacts no
one. Only when they are satisfied that you have taken the actions required
by the FAQ will your listing be downgraded or removed.
But I am only repeating what you have already been told many times already.
Posting on here is not a "write only" medium, please take time to read the
very knowledgeable advice that you have been given. If you do not understand
the answers, please get someone from your company that does understand to
post on here. Then sit back and consider that you may be in the wrong job,
and then what are you going to do about it.
A good place to start to read the Spews FAQ would be:
"Q41: How does one contact SPEWS?
"A41: One does not. SPEWS does not receive email - it's just an automated
system and website, general blocklist related issues can be discussed in
the public forums mentioned above. The newsgroups news.admin.net-
abuse.blocklisting (NANABL) and news.admin.net-abuse.email (NANAE) are good
choices. Google makes it quite easy to post messages via the Web in the
unmoderated NANAE group. Newsreader software should be used to post to the
prefered moderated NANABL group. First time newsgroup posters should read
the NANAE FAQ. Note that posting messages in these newsgroups & lists will
not have any effect on SPEWS listings, only the discontinuation of spam
and/or spam support will. Be aware that posting ones email address to any
publicly viewable forum or website makes it instantly available to
spammers. If you're concerned about getting spammed, change or "mung" the
email address you use to post with."
HTH, HAND
Chris Greville