Re: problem dealing w/ ietf.org mail servers

Kurt Erik Lindqvist <kurtis@kurtis.pp.se> Fri, 04 July 2008 10:49 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 C914B3A6C11; Fri, 4 Jul 2008 03:49:33 -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 092EE3A6C11 for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 03:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level:
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.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 zkIf1fIj1FlU for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 03:49:31 -0700 (PDT)
Received: from lemland.kurtis.pp.se (lemland.kurtis.pp.se [IPv6:2001:670:87:2::25]) by core3.amsl.com (Postfix) with ESMTP id D5FA13A6B6B for <ietf@ietf.org>; Fri, 4 Jul 2008 03:49:30 -0700 (PDT)
Received: from [10.34.0.136] (unknown [194.209.131.192]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by lemland.kurtis.pp.se (Postfix) with ESMTP id D6AD178C2F; Fri, 4 Jul 2008 13:49:35 +0300 (EEST)
Message-Id: <CC2A5739-19C7-4B6D-887C-3496A0268562@kurtis.pp.se>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <486CDAE1.4040905@spaghetti.zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: problem dealing w/ ietf.org mail servers
Date: Fri, 04 Jul 2008 12:45:52 +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.924)
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:

> On Wed, Jul 02, 2008 at 10:47:53PM -0700, 'kent' wrote:
> [..]
>> However, this last address, 2001:470:1:76:2c0:9fff:fe3e:4009, is not
>> explicitly configured on the sending server; instead, it is being  
>> implicitly
>> configured through ip6 autoconf stuff:
>
> Which (autoconfig) you should either not be using on servers, or you  
> should be configuring your software properly to select the correct  
> outbound address. (I prefer to use the autoconfig one for  
> 'management' and using a 'service address' for the service).


What a shame that's not what's in the RFCs..:-)

Best regards,

- kurtis -



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf