Re: [Asrg] What are the IPs that sends mail for a domain?

Paul Russell <prussell@nd.edu> Sun, 21 June 2009 02:36 UTC

Return-Path: <prussell@nd.edu>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C8C53A6901 for <asrg@core3.amsl.com>; Sat, 20 Jun 2009 19:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2YxKD2ZQjBW for <asrg@core3.amsl.com>; Sat, 20 Jun 2009 19:36:45 -0700 (PDT)
Received: from mx-p1.cc.nd.edu (mx-p1.cc.nd.edu [129.74.250.57]) by core3.amsl.com (Postfix) with ESMTP id 93C2F3A685B for <asrg@irtf.org>; Sat, 20 Jun 2009 19:36:45 -0700 (PDT)
Received: from mta-2.cc.nd.edu (mta-2.cc.nd.edu [129.74.250.37]) by mx-p1.cc.nd.edu (Switch-3.3.0/Switch-3.3.0) with ESMTP id n5L2XItI025009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <asrg@irtf.org>; Sat, 20 Jun 2009 22:33:19 -0400
Received: from [172.19.226.74] (nat20.cc.nd.edu [129.74.4.120]) (authenticated bits=0) by mta-2.cc.nd.edu (Switch-3.3.0/Switch-3.3.0) with ESMTP id n5L2aqNp023081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Sat, 20 Jun 2009 22:36:53 -0400 (EDT)
Message-ID: <4A3D9CC4.10303@nd.edu>
Date: Sat, 20 Jun 2009 22:36:52 -0400
From: Paul Russell <prussell@nd.edu>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <15942168.11245533549248.JavaMail.franck@somehost-4.sv2.equinix.net>
In-Reply-To: <15942168.11245533549248.JavaMail.franck@somehost-4.sv2.equinix.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Source-IP: 129.74.250.37
X-ND-MTA-Date: Sat, 20 Jun 2009 22:33:19 EDT
Subject: Re: [Asrg] What are the IPs that sends mail for a domain?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jun 2009 02:36:46 -0000

On 6/20/2009 17:33, Franck Martin wrote:
> yes I'm not sure that blocking port 25 will ever be possible. I think less and 
> less people want their mailbox tied up to an ISP, this is why they get a
> mailbox on yahoo, google, etc... So these services requires you usualy to
> connect via port 25 and authenticate, but that means for the ISP to let port
> 25 open. Blocking port 25 and letting port smtps/465 open to allow users to
> still submit email is better, but just a temporaray measures until botnet use
> smtps to submit.

Gmail supports secure authenticated message submission via port 587.

-- 
Paul Russell, Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame