Re: problem dealing w/ ietf.org mail servers

Iljitsch van Beijnum <iljitsch@muada.com> Mon, 07 July 2008 16:18 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C67213A68DD; Mon, 7 Jul 2008 09:18:51 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AEB13A68D7 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 09:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 Qn9QwHVfA9LA for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 09:18:50 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id D11D23A6983 for <ietf@ietf.org>; Mon, 7 Jul 2008 09:18:49 -0700 (PDT)
Received: from [IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb] ([IPv6:2001:720:410:1001:21b:63ff:fe92:9fbb]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id m67GIg8E043987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Jul 2008 18:18:43 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <3B44A0DE-151E-4BF8-B9E9-E0AF5643829B@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <486CDAE1.4040905@spaghetti.zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Re: problem dealing w/ ietf.org mail servers
Date: Mon, 07 Jul 2008 18:18:43 +0200
References: <013301c8dca5$22ca0a80$685e1f80$@us> <20080703054752.GM6185@lark.songbird.com> <20080703134655.GA17472@boreas.isi.edu> <486CDAE1.4040905@spaghetti.zurich.ibm.com>
X-Mailer: Apple Mail (2.926)
Cc: ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>, Richard Shockey <richard@shockey.us>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On 3 jul 2008, at 15:57, Jeroen Massar wrote:

> Which (autoconfig) you should either not be using on servers, or you  
> should be configuring your software properly to select the correct  
> outbound address.

Is it the IETF's job to tell people how to run their networks?

In my opinion, stateless autoconfig is a perfectly acceptable way to  
configure servers.

> SMTP shows that it is perfectly usable for these situations as it  
> nicely rejects the message with a proper message automatically  
> telling you on how to solve it.

I ran into the issue with the non-existant IPv6 reverse mapping twice.  
I would prefered to have solved this by getting proper delegation from  
my ISP, but I haven't been able to get this done for years.

Anyway, the first time I opened a ticket they told me it was fixed.  
Then the problem returned and they told me I was put on a whitelist.  
As this thread indicates, that's hardly a solution, especially since I  
was unable to get Sendmail to NOT use IPv6 without completely  
disabling the protocol on my system, making it completely impossible  
for me to deliver mail to the IETF servers. (Serves me right for  
running Sendmail I guess.)

> Those boxes are not set up correctly thus should not be sending  
> email in the first place. For that matter you should actually be  
> firewalling+logging port 25 outbound so you can monitor any host in  
> your network doing illegal SMTP connects.

In my opinion, filtering at layer 4 because a layer 7 protocol is  
broken is a bad idea.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf