dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
60

graysonf
MVM
join:1999-07-16
Fort Lauderdale, FL

1 recommendation

graysonf to ArrayList

MVM

to ArrayList

Re: Comcast decides to block port 25 IN and OUT with no notice.

Get a free shell account on »www.cjb.net

Connect anywhere you want to destination port TCP 25.

JohnInSJ
Premium Member
join:2003-09-22
Aptos, CA

1 recommendation

JohnInSJ to ArrayList

Premium Member

to ArrayList
said by ArrayList:

said by JohnInSJ:

said by ArrayList:

the server is not run on the business class connection. That alone says that you don't need business level service.

I have no idea what you're saying here.

I don't run a server on my connection, why can't I open a tcp connection to a remote server over port 25 without paying more money for the privilege to do so? I really don't care either way. Spammers will spam regardless of what Comcast does.

Port 25 communications is reserved for servers. That's why.

NormanS
I gave her time to steal my mind away
MVM
join:2001-02-14
San Jose, CA
TP-Link TD-8616
Asus RT-AC66U B1
Netgear FR114P

NormanS to ArrayList

MVM

to ArrayList
said by ArrayList:

Spammers will spam regardless of what Comcast does.

Prior to 2002, when SBC blocked customer access to port 25, SBC residential hosts were the most prevalent spam source IP addresses in my server logs. Subsequent to the blocking, SBC residential hosts dropped to near last. While spammers continued to spam, they were much less successful at using compromised SBC residential customer hosts.

FWIW, SBC led Comcast until the blocks. After the SBC blocks, SBC dropped behind Comcast as a spam source. From which I deduced that blocking port 25 reduced the amount of abuse coming from SBC.