Removal request from SPEWS - 216.31.173.249
Peter Mihailov
I really hate spam and to tell you the truth now I hate it much more
after spending the entire Sunday in trying to understand why my emails
won't be accepted by some domains etc..
Can you please remove 216.31.173.249 from your list. I am not a
spammer and just got dedicated server from oc3networks.com - if you
want to make sure call them and ask them about this IP -
216.31.173.249
Please remove me because my email does not reach certain domains etc..
Peter
Jim Seymour
pete...@yahoo.com (Peter Mihailov) writes:
> Hello,
>
> I really hate spam and to tell you the truth now I hate it much more
> after spending the entire Sunday in trying to understand why my emails
> won't be accepted by some domains etc..
Shouldn't have taken *that* long. That is: If the reject/bounce
messages that prompted you to look at this weren't being destroyed
by a lame email client.
>
> Can you please remove 216.31.173.249 from your list. I am not a
> spammer and just got dedicated server from oc3networks.com - if you
> want to make sure call them and ask them about this IP -
> 216.31.173.249
*You*, specifically, aren't being called a spammer. The problem is
this:
http://www.spews.org/html/S786.html
thebvg/oc3n
|--------------------
.
1, 216.31.141.130/31, ns1.oc3networks.com / ns2.oc3networks.com
1, 216.31.141.0/24, oc3networks.com (Pajo)
1, 216.31.173.0/24, oc3networks.com (Pajo)
.
---------------------|
It's unclear to me what the exact relationship is between "thebvg"
and oc2networks, but it *appears* that this all stems from thebvg
spamming from oc3n space? I'm guessing oc3n did nothing to address
the problem, so the listing was expanded to 216.31.141.0/24, and
later to 216.31.173.0/24 when there continued to be no acceptable (to
SPEWS) resolution.
>
> Please remove me because my email does not reach certain domains etc..
Unless there's a *mistake* in the listing (e.g.: The listed space
turns out to have no relation to any of the offending parties, for
example): That's highly unlikely, I suspect.
If you haven't already: I suggest you go read the SPEWS FAQ at:
*carefully*. I believe you'll find all the answers, in that FAQ,
to any question you might have regarding this SPEWS listing.
--
Jim Seymour | "Some of the lies are so strange it
jsey...@LinxNet.com | makes you wonder about the spammer's
LinxNet Spam Files: | sanity."
http://www.LinxNet.com/misc/spam | - Ed Foster, "The Gripe Line" 6/24/02
Spambo
First, you should realize that you are posting to a Usenet newsgroup.
This is *NOT* SPEWS or any other blocklist. SPEWS does *NOT* respond to
posts in this newsgroup (or by email). The only response you'll see
from SPEWS is changes in the "S" records on its website.
216.31.173.249 seems to be listed because the PAJO is providing services
to oc3networks.com.
From http://spews.org/html/S786.html
<quote>
thebvg/oc3n
[...]
1, 216.31.141.130/31, ns1.oc3networks.com / ns2.oc3networks.com
1, 216.31.141.0/24, oc3networks.com (Pajo)
1, 216.31.173.0/24, oc3networks.com (Pajo)
<end quote>
It seems to me that you're buying services from a known spam operation
and the SPEWS listing is likely to remain as long as PAJO is hosting
oc3networks. As such, your best options are either to find a new host
or to make arrangements to send your email from a different provider in
cleaner net space.
--
Emailed responses are not wanted. If a response is necessary please
reply in the newsgroup only.
Robyn Banks
Peter, you crack me up!
The Pajo Group PAJO03 (NET-216-31-128-0-1)
216.31.128.0 - 216.31.191.255
OC3 Networks OC3-NETWORKS-12 (NET-216-31-173-128-1)
216.31.173.128 - 216.31.173.255
There's not much news in nanas on Pajo recently, but many have a
trigger finger when it comes to spam from their netspace. I do.
Frankly, I never took 'em out of the local blocklists and probably
won't until they have a year or more of spam-free behavior. Even
then, unless one of my users complains about not getting
legitimate mail from that netspace, they may stay blocked forever.
My recommendation to you is: move.
Mike Easter
> *You*, specifically, aren't being called a spammer. The problem is
> this:
>
> http://www.spews.org/html/S786.html
> thebvg/oc3n
>|--------------------
> .
> 1, 216.31.141.130/31, ns1.oc3networks.com / ns2.oc3networks.com
> 1, 216.31.141.0/24, oc3networks.com (Pajo)
> 1, 216.31.173.0/24, oc3networks.com (Pajo)
> .
> ---------------------|
>
> It's unclear to me what the exact relationship is between "thebvg"
> and oc2networks, but it *appears* that this all stems from thebvg
> spamming from oc3n space? I'm guessing oc3n did nothing to address
> the problem, so the listing was expanded to 216.31.141.0/24, and
> later to 216.31.173.0/24 when there continued to be no acceptable (to
> SPEWS) resolution.
It must be a heavy duty attack on the nameservice situation for
321SEND.COM which used to have
321send.com NS ns1.oc3networks.com
321send.com NS ns2.oc3networks.com
which used to live in:
1, 216.31.141.0/24, oc3networks.com
and then, spews went after another different Pajo /24 -
216.31.173.0/24 - which doesn't have anything to do with oc3networks, I
suppose as a warning to Pajo that the whole /18 might be next:
OrgName: The Pajo Group
NetRange: 216.31.128.0 - 216.31.191.255
CIDR: 216.31.128.0/18
In any case, 321send.com seems to have lost its connectivity, and
doesn't have that nameservice anymore.
--
Mike Easter
Tom Betz
news:9334d72c.03072...@posting.google.com:
> Can you please remove 216.31.173.249 from your list.
I am not SPEWS, but I can tell you that it's probably not going to happen.
<http://openrbl.org/ip/216/31/173/249.htm> shows your space in 7 different
DNSbls, and <http://spews.org/ask.cgi?S786> (wait for it) shows how the
listing has grown.
Pajo Networks has a long history of spammer support, and as long as you are
their customer, you're likely to have serious connectivity problems.
I know that, SPEWS or no SPEWS, I consider Pajo to be "block on sight".
That's NEVER going to change.
Mike Andrews
As he said. There are other networks for which Rathbun's Dictum holds
true:
I think it likely that when the successor to IPV6
is just about to be deployed throughout the Solar
System there will still be null routes and deny table
entries for 205.199.212.0/24 in an uncountable number
of places.
-- Michael Rathbun
--
Mike Andrews
mi...@mikea.ath.cx
Tired old sysadmin since 1964
McWebber
news:9334d72c.03072...@posting.google.com...
321send.com/net appears gone as do any domains that implicate
oc3networks.com
--- DNS lookup for "321send.com", please wait...
--- contacting nameserver: ns1.oc3networks.com [216.31.141.130]
DNS Server Response 3: Name Error.
--- contacting nameserver: ns2.oc3networks.com [216.31.141.131]
DNS Server Response 3: Name Error.
No match for "321send.com" in the registrar database.
Domain Name: 321SEND.COM
Registrar: GO DADDY SOFTWARE, INC.
Whois Server: whois.godaddy.com
Referral URL: http://registrar.godaddy.com
Name Server: NS1.OC3N.COM
Name Server: NS2.OC3N.COM
Name Server: PARK7.SECURESERVER.NET
Name Server: PARK8.SECURESERVER.NET
Status: REDEMPTIONPERIOD
Updated Date: 23-jul-2003
Creation Date: 13-jun-2002
Expiration Date: 13-jun-2003
321send.net is available to register.
321optin.com has moved. ns1/ns2.oc3networks.com is no longer authoritative
for it. Ditto for OPTMAILER.NET
Registrant:
tech manger
6278 North federal Highway # 187
Fort lauderdale, Florida 33308
US
Registrar: DOTSTER
Domain Name: 321OPTIN.COM
Created on: 02-DEC-02
Expires on: 02-DEC-03
Last Updated on: 11-FEB-03
Administrative Contact:
manger, tech bbpl...@aol.com
6278 North federal Highway # 187
Fort lauderdale, Florida 33308
US
954-290-1050
Technical Contact:
manger, tech bbpl...@aol.com
6278 North federal Highway # 187
Fort lauderdale, Florida 33308
US
954-290-1050
Domain servers in listed order:
NS1.OC3N.COM
NS2.OC3N.COM
Registrant:
tech manger
6278 North federal Highway # 187
Fort lauderdale, Florida 33308
US
Registrar: DOTSTER
Domain Name: OPTMAILER.NET
Created on: 02-DEC-02
Expires on: 02-DEC-03
Last Updated on: 11-FEB-03
Administrative Contact:
manger, tech bbpl...@aol.com
6278 North federal Highway # 187
Fort lauderdale, Florida 33308
US
954-290-1050
Technical Contact:
manger, tech bbpl...@aol.com
6278 North federal Highway # 187
Fort lauderdale, Florida 33308
US
954-290-1050
Domain servers in listed order:
NS1.OC3N.COM
NS2.OC3N.COM
oc3n.com has expired.
http://whois.dotregistrar.com/drs/wwwhois.pl?domain=oc3n&tld=.COM&Check=Check
EXPIRED DOMAIN
Registrant:
OC3N DNS Services (OC3N-COM-DOM)
19528 Ventura Blvd. #433
Tarzana, CA 91356
US
818-3473431
sy...@oc3n.com
Domain Name: OC3N.COM
Administrative Contact:
OC3N DNS Services sy...@oc3n.com
19528 Ventura Blvd. #433
Tarzana, CA 91356
US
818-3473431
Technical Contact, Zone Contact:
OC3N DNS Services sy...@oc3n.com
19528 Ventura Blvd. #433
Tarzana, CA 91356
US
818-3473431
Record last updated on 30-May-2003.
Record expires on 05-May-2003.
Record created on 05-May-2002.
Domain servers in listed order:
Name Server: ns1.oc3n.com
Name Server: ns2.oc3n.com
--
McWebber
No email replies read
If someone tells you to forward an email to all your friends
please forget that I'm your friend.
Erik Warmelink
> I really hate spam and to tell you the truth now I hate it much more
> after spending the entire Sunday in trying to understand why my emails
> won't be accepted by some domains etc..
>
> Can you please remove 216.31.173.249 from your list. I am not a
> spammer and just got dedicated server from oc3networks.com - if you
> want to make sure call them and ask them about this IP -
> 216.31.173.249
oc3networks.com is listed, why would an assurance by them that you are
no spammer help?