{Disarmed} Re: Listen on different port

[Gerard]

On Mon, 07 Jan 2008 10:56:48 -0600
Ken Anderson <ka at pacific.net> wrote:

> 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? :-)

From what little I have been able to gleam from Comcast themselves, it
appears that they are attempting to stop their non-business customers;
i.e., users willing to pay $100 or more per month for static IP, from
running mail servers.

For the record, that is one more reason why I am investigating FIOS as
a replacement for Comcast cable.

-- 

Gerard
gerard at seibercom.net

MARRIAGE:
	Convertible bonds.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20080107/3feffd7e/signature.bin