kd6caeP2p Shouldn't Be A Crime
join:2001-08-27
Palmdale, CA Reviews:
 ·Vitelity VOIP
 ·AT&T U-Verse
| blocking outbound port 25 is stupid! Here's my personal view of providers that block port 25. For residential accounts, blocking inbound 25 I can live with, but what good is blocking outbound 25? I for instance prefer to send email via a friend's mail server. tell me what the devil is wrong with wanting to send email via a server that isn't your IsPS? As far as having a mail server listen on a nonstandard port such as 26, I suppose that may work however if I understand the way email works, the mail server sending the message to it's destination needs to comunicate with the destination mail server and all comunication between the servers is done on port 25! So if I send a message to you@yourdomain.com via my mail server if outbound port 25 was blocked at my mail server, then even if you were accepting connections on another port my server would assume the server was down! It has no way to connect with an alternate port. I guess what I'm saying is the only ports that should be blocked are inbound ports and even then only on residential accounts! Maybe on business accounts you could block ports 135-139, 445 and ports such as that that noone has ever used. And if someone needs to use those ports they should be able to unblock them for their connection. In other words give us some flexibility here. |
