[107551] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: ingress SMTP

daemon@ATHENA.MIT.EDU (Jeff Kinz)
Fri Sep 5 13:38:44 2008

X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
Date: Fri, 5 Sep 2008 13:38:32 -0400
From: Jeff Kinz <jkinz@kinz.org>
To: nanog@nanog.org
Cc: nanog@nanog.org
In-Reply-To: <alpine.DEB.1.10.0809051032010.29587@uplift.swm.pp.se>
Errors-To: nanog-bounces@nanog.org

On Fri, Sep 05, 2008 at 10:35:15AM +0200, Mikael Abrahamsson wrote:
> On Fri, 5 Sep 2008, Simon Waters wrote:
> 
> >If the ISP blocks port 25, then the ISP is taking responsibility for
> >delivering all email sent by a user, and they have to start applying rate
> >limits.
> 
> MUAs should stop sending email via 25 and use 587 or equivalent instead. 
> There is little actual reason why someone should be able to send TCP/25 
> SMTP email from a residential connection when most software support 
> authenticated TCP/587 submits.

Just FYI- the ISP has the same 220 email address limit even when I send
thru port 587, authenticated.  (its comcast)
> 
> We don't allow most of our residential customer base to speak SMTP TCP/25 
> to anywhere at all (and we have millions of them). Wish more ISPs would do 
> the same.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

-- 


home help back first fref pref prev next nref lref last post