{Disarmed} Re: Listen on different port

[Ken A]

Scott Silva wrote:
> on 1/7/2008 8:56 AM Ken Anderson spake the following:
>> Gerard wrote:
>>> On Mon, 07 Jan 2008 10:18:46 -0600
>>> Ken Anderson <ka at pacific.net> wrote:
>>>
>>>> You really should relay out through your ISP's mailserver. Your ISP
>>>> will not be blocking port 25 incoming, so your listening sendmail on
>>>> port 25 should be able to receive mail from the Net just fine. Your
>>>> ISP's block on port 25 outgoing will not be worked around by setting
>>>> up your sendmail to listen on an additional port. You need to set
>>>> smart host in your sendmail.mc and rebuild sendmail.cf.
>>>
>>> Comcast, at least in selected markets, has been blocking port 25 both
>>> in & out. In fact, they are enforcing TLS/SSL on port 587, again in
>>> selected markets. Actually, it is not such a bad idea if it stops
>>> 'bots' from sending SPAM.
>>>
>>>
>>
>> Enforcing TLS on AUTH date makes sense, but why block port 25 
>> incoming? There are no bots that deliver directly to end users. Is MS 
>> messenger now listening on port 25? :-)
>> Ken
>> Pacific.Net
> Because these ISP's sell "business" accounts that cost more. They 
> consider anyone who runs any outside reachable service in violation of 
> their use contracts unless you pay 3 to 5 times more for one of these 
> business contracts. And it is a lot easier to stop all traffic on a port 
> across your system then to selectively track down the offenders.
> 

Ah, giving small ISPs another advantage by mistreating their customers 
again! Now if we could only get access to that cable.
Ken


-- 
Ken Anderson
Pacific.Net