  tschmidt Premium,MVM join:2000-11-12 Milford, NH
·Hollis Hosting
·Verizon Online DSL
·Fairpoint Communic..
| reply to Tweak Re: Boo
said by Tweak :Are you joking blocking outbound port 25 is one of the most effective methods in combating spam. How does blocking outbound Port 25 help? I agree inbound but fail to see what blocking outbound port 25 accomplishes.
What it will do is annoy customer's like me that have a hosted domain and use off network SMTP server.
/tom |
|
 NormanS Premium,MVM join:2001-02-14 San Jose, CA
·Pacific Bell - SBC
| said by tschmidt :How does blocking outbound Port 25 help? I agree inbound but fail to see what blocking outbound port 25 accomplishes. Outbound port 25 access allows a Verizon subscriber to access port 25 on a remote host. Such as an infected Verizon user's computer connecting to my mail server on port 25. If Verizon blocks outbound port 25 access, that means no 'bots on Verizon customers' infected computers can connect to my server.
The spammer does not need inbound port 25 access to the infected computer; any of the 65,535 TCP ports will suffice. But they can't get to the target gateway mail server from the Verizon network if the Verizon network chokes off port 25.
I watched the logs on my server, and, in 2004, SBC was the worst, followed by Comcast. In 2005, both SBC and Comcast implemented some form of blocking of outbound port 25. SBC opted for a blanket block on all users, and dubious connections from residential SBC IP addresses dropped dramatically. Comcast implemented a reactionary approach; block their subscribers when excessive SMTP activity was detected.
SBC dropped off the radar, and Comcast fell to near last place; Road Runner and Verizon became the top dogs in my dirty list.
The most recent rewrites of the email RFCs more clearly specify that port 25 access should be only used for mail transfer by email services, and that end user message submission should be done over port 587. -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum |
|
  tschmidt Premium,MVM join:2000-11-12 Milford, NH
·Hollis Hosting
·Verizon Online DSL
·Fairpoint Communic..
| said by NormanS :Outbound port 25 access allows a Verizon subscriber to access port 25 on a remote host. It has been common practice for residential ISPs to block inbound Port 25 for years for exactly that reason.
said by NormanS : that end user message submission should be done over port 587. I read it over last night after I posted. I'll have to contact my hosting service to see what they support. I'm in New England, Verizon sold assets to FairPoint but I have to assume they will adopt similar policy at some point.
I'm in favor of steps that reduce spam but some ISPs have adopted rather silly an ineffective anti-spam measures that make life difficult.
/tom |
|
  Tweak Premium join:2002-06-08 Oklahoma City, OK | Its not ineffective you have had fellow posters explain to you that its very effective in blocking spam. |
|
 NormanS Premium,MVM join:2001-02-14 San Jose, CA
·Pacific Bell - SBC
| reply to tschmidt said by tschmidt :said by NormanS :Outbound port 25 access allows a Verizon subscriber to access port 25 on a remote host. It has been common practice for residential ISPs to block inbound Port 25 for years for exactly that reason. Blocking inbound port 25 has no effect on compromised computers' access gateway (MX) mail servers. You could block inbound port 25 to every Verizon customer, leave outbound port 25 unblocked, and compromise Verizon customer computers would be able to make connections to my gateway mail server unimpeded (unless the source IP address was in a blocking list, and my server queried same).
FWIW, neither AT&T (in the legacy SBC regions), nor Comcast block inbound port 25 by default. Comcast only blocks port 25 on evidence of abuse from their customer; that is a bidirectional block when implemented. AT&T (legacy SBC regions only) just blocks outbound port 25; though their block is bidirectional for AT&T Worldnet DSL and AT&T Southeast (legacy Bellsouth) customers.
said by NormanS : that end user message submission should be done over port 587. I read it over last night after I posted. I'll have to contact my hosting service to see what they support. I'm in New England, Verizon sold assets to FairPoint but I have to assume they will adopt similar policy at some point. I'm in favor of steps that reduce spam but some ISPs have adopted rather silly an ineffective anti-spam measures that make life difficult. Port 25 blocking is neither silly, nor ineffective. In fact, it has led to an increase in malicious attempts to gain AT&T customer email log in details. Since outbound port 25 is no longer available to the 'botnet spammers, they attempt to steal authorized log in credentials to the SMTP AUTH message submission servers. Using social engineering to steal that access from the users. It would seem that outbound port 25 blocking is putting the hurt on 'botnet spammers, if they have to resort to stealing accounts to get their spam sent. -- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum |
|