RE: problem dealing w/ ietf.org mail servers
<michael.dillon@bt.com> Thu, 03 July 2008 16:38 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 59A043A6CFB; Thu, 3 Jul 2008 09:38:21 -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 09B503A6CF7 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 09:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 HCc4j26Rjxe5 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 09:38:19 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id E38F13A6D01 for <ietf@ietf.org>; Thu, 3 Jul 2008 09:36:26 -0700 (PDT)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.63]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 3 Jul 2008 17:36:09 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: problem dealing w/ ietf.org mail servers
Date: Thu, 03 Jul 2008 17:36:07 +0100
Message-ID: <C0F2465B4F386241A58321C884AC7ECC06F8DBDF@E03MVZ2-UKDY.domain1.systemhost.net>
In-Reply-To: <486CF53A.4060407@cs.utk.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: problem dealing w/ ietf.org mail servers
thread-index: AcjdJLdpQUDOd7pOQ8S4G9h3Et/4WgABHupQ
From: michael.dillon@bt.com
To: ietf@ietf.org
X-OriginalArrivalTime: 03 Jul 2008 16:36:09.0504 (UTC) FILETIME=[E5DF4A00:01C8DD2A]
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
> > Which (autoconfig) you should either not be using on > servers, or you > > should be configuring your software properly to select the correct > > outbound address. > that's a bizarre statement. the distinction between a client > and a server is an artificial one. either autoconfig is > useful for all kinds of machines, or it's almost useless. You are correct when talking about IP networks in general, however Jeroen is talking about the public Internet, not IP networks in general. Of course another way to make this less bizarre is to stop using the word "server" to refer to two different things. Jeroen is saying that an IPv6 devices that wishes to advertise its IPv6 address for the purposes of receiving SMTP connection requests, should not be configured in such a way that its IPv6 host ID is randomly assigned. Of course you could try to dynamically update your reverse DNS to match the random host IDs but that creates corner cases and race conditions which can be entirely avoided just by making the publicly visible IPv6 address a static one. Jeroen further pointed out that there is no reason for an interface, which has been assigned a random host ID, to suffer with only one address because IPv6 makes it straightforward to have multiple addresses on an interface. BTW, I do agree with your general viewpoint of Internet email architecture; it is horribly ugly and broken. --Michael Dillon _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- problem dealing w/ ietf.org mail servers 'kent'
- Re: problem dealing w/ ietf.org mail servers Mark Andrews
- Re: problem dealing w/ ietf.org mail servers Keith Moore
- Re: problem dealing w/ ietf.org mail servers Bill Manning
- Re: problem dealing w/ ietf.org mail servers Jeroen Massar
- Re: problem dealing w/ ietf.org mail servers John Levine
- Re: problem dealing w/ ietf.org mail servers Dave Crocker
- Re: problem dealing w/ ietf.org mail servers Keith Moore
- Re: problem dealing w/ ietf.org mail servers Keith Moore
- Re: problem dealing w/ ietf.org mail servers John Levine
- RE: problem dealing w/ ietf.org mail servers michael.dillon
- Re: problem dealing w/ ietf.org mail servers Keith Moore
- Re: problem dealing w/ ietf.org mail servers Mark Andrews
- Re: problem dealing w/ ietf.org mail servers Bill Manning
- Re: problem dealing w/ ietf.org mail servers TS Glassey
- Re: problem dealing w/ ietf.org mail servers Mark Andrews
- Re: problem dealing w/ ietf.org mail servers kent
- Draft on how to correctly configure servers and o… Jeroen Massar
- Re: problem dealing w/ ietf.org mail servers Kurt Erik Lindqvist
- Re: problem dealing w/ ietf.org mail servers Kurt Erik Lindqvist
- Re: problem dealing w/ ietf.org mail servers John C Klensin
- Re: problem dealing w/ ietf.org mail servers Jeroen Massar
- Re: problem dealing w/ ietf.org mail servers Keith Moore
- Re: problem dealing w/ ietf.org mail servers kent
- Re: problem dealing w/ ietf.org mail servers Ned Freed
- Re: problem dealing w/ ietf.org mail servers Dave Crocker
- Re: problem dealing w/ ietf.org mail servers Iljitsch van Beijnum
- Re: problem dealing w/ ietf.org mail servers Francis Dupont
- Re: problem dealing w/ ietf.org mail servers Keith Moore
- Re: problem dealing w/ ietf.org mail servers SM
- Re: problem dealing w/ ietf.org mail servers Kurt Erik Lindqvist
- Re: problem dealing w/ ietf.org mail servers Keith Moore
- Re: problem dealing w/ ietf.org mail servers Kurt Erik Lindqvist
- Re: problem dealing w/ ietf.org mail servers Jeroen Massar