Mailing List Archive

RE: BLOCK: even more useless spam stats
> -----Original Message-----
> From: Steven Champeon [mailto:schampeo@HESKETH.COM]
> Sent: Wednesday, February 11, 2004 10:12 PM
> To: SPAM-L@PEACH.EASE.LSOFT.COM
> Subject: BLOCK: even more useless spam stats
>
>
> The perennial question here seems to be "where does it all come from",
> and in the spirit of answering that question, here are the top however
> many sending domains/cc.tlds for messages we rejected as spam (which,
> given how much we reject, is a lot more accurate than "spam
> we received")
> since 1/1/04 (domains/cc.tlds with more than 5 attempts):
>
> 585 comcast.net
> 402 rr.com
> 188 attbi.com
> 175 pacbell.net
> 165 ameritech.net
> 130 shawcable.net
> 128 adelphia.net
> 125 optonline.net
> 106 wanadoo.fr
> 105 verizon.net
> 103 bellsouth.net
*snip*
> 15 cox-internet.com
*snip*
>
> Comcast should feel right at home with Disney.
>

I just changed my outlook on my ISP. Cox.net (which I think is slightly
different from cox-internet.com) I hate that they are a monoploy, but look
at this from there website:

"To reduce unsolicited bulk email sent on our Cox High Speed Internet
network, Cox instituted outbound SMTP traffic filtering (port 25 filtering).
Currently Cox also filters all inbound SMTP traffic in an effort to protect
unsecured computers on the network from being used as mail relay by
potential spammers.

The outbound SMTP traffic blocking security measure is designed to protect
Internet users and the Cox High Speed Internet network. The vast majority of
customers are not affected by this practice in any way. However, a small
number of customers who use e-mail addresses outside of the @cox.net domain
and who do not currently have their SMTP servers set for Cox mail servers do
need to change their settings. The requirement that Cox servers be used for
all outgoing mail is simply so that Cox can observe and control spammers by
removing them from the network.

Outbound SMTP traffic blocking is quickly becoming an industry standard.
Other ISPs who block port 25 include Bellsouth, Earthlink, Mindspring,
Verizon, Mediaone, and MSN.
Since the implementation of the port 25 blocking procedure, Cox has seen
significant decreases in the residential Cox High Speed Internet complaint
counts for different abuse types impacted by the port 25 blocking. Port
scanning complaints decreased by 36%, virus complaints by 41%, spam
complaints by 52%, and open proxy by more than 78%.

Port 25 blocking also helped to control the impact viruses that have
polluted the network by preventing their spread via email routing through
port 25. "

Apparently Verizon and Bellsouth block??? Doesn't look like it!!!

--Chris
Re: BLOCK: even more useless spam stats [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Chris Santerre writes:
> > -----Original Message-----
> > From: Steven Champeon [mailto:schampeo@HESKETH.COM]
> > Sent: Wednesday, February 11, 2004 10:12 PM
> > To: SPAM-L@PEACH.EASE.LSOFT.COM
> > Subject: BLOCK: even more useless spam stats
> >
> >
> > The perennial question here seems to be "where does it all come from",
> > and in the spirit of answering that question, here are the top however
> > many sending domains/cc.tlds for messages we rejected as spam (which,
> > given how much we reject, is a lot more accurate than "spam
> > we received")
> > since 1/1/04 (domains/cc.tlds with more than 5 attempts):
> >
> > 585 comcast.net
> > 402 rr.com
> > 188 attbi.com
> > 175 pacbell.net
> > 165 ameritech.net
> > 130 shawcable.net
> > 128 adelphia.net
> > 125 optonline.net
> > 106 wanadoo.fr
> > 105 verizon.net
> > 103 bellsouth.net
> *snip*
> > 15 cox-internet.com
> *snip*
> >
> > Comcast should feel right at home with Disney.

BTW -- a comment on these. Whatever you do, don't get the impression that
blocking these hosts in any way is a good idea -- SC hasn't provided any
info on *non*spam output, so there's no indication of what the baseline
is, or what *proportion* of mail from those servers is spam.

- --j.

>
> I just changed my outlook on my ISP. Cox.net (which I think is slightly
> different from cox-internet.com) I hate that they are a monoploy, but look
> at this from there website:
>
> "To reduce unsolicited bulk email sent on our Cox High Speed Internet
> network, Cox instituted outbound SMTP traffic filtering (port 25 filtering).
> Currently Cox also filters all inbound SMTP traffic in an effort to protect
> unsecured computers on the network from being used as mail relay by
> potential spammers.
>
> The outbound SMTP traffic blocking security measure is designed to protect
> Internet users and the Cox High Speed Internet network. The vast majority of
> customers are not affected by this practice in any way. However, a small
> number of customers who use e-mail addresses outside of the @cox.net domain
> and who do not currently have their SMTP servers set for Cox mail servers do
> need to change their settings. The requirement that Cox servers be used for
> all outgoing mail is simply so that Cox can observe and control spammers by
> removing them from the network.
>
> Outbound SMTP traffic blocking is quickly becoming an industry standard.
> Other ISPs who block port 25 include Bellsouth, Earthlink, Mindspring,
> Verizon, Mediaone, and MSN.
> Since the implementation of the port 25 blocking procedure, Cox has seen
> significant decreases in the residential Cox High Speed Internet complaint
> counts for different abuse types impacted by the port 25 blocking. Port
> scanning complaints decreased by 36%, virus complaints by 41%, spam
> complaints by 52%, and open proxy by more than 78%.
>
> Port 25 blocking also helped to control the impact viruses that have
> polluted the network by preventing their spread via email routing through
> port 25. "
>
> Apparently Verizon and Bellsouth block??? Doesn't look like it!!!
>
> --Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFAK8dEQTcbUG5Y7woRAkLzAJ9QsWHFmYUCt2MHta5ZUaE+EVDCHwCfeDzS
gwv6xgyI+vhHsZjEqNRjCHw=
=yK0j
-----END PGP SIGNATURE-----