list reply-to has changed?

Glenn Satchell Glenn.Satchell at
Thu Nov 20 12:50:34 UTC 2008

Hi Evan and David,

Thanks for sorting it out so quickly. It would appear to be back to the
original 'reply to list' behaviour. I dare not say "fixed" :)

One other thing I have noticed is the time between sending a message
and receiving the return from the list. With the old mail system I
would often see the return back in a few minutes, now there seems to be
about an hour delay. Looking at the Received headers this appears to be
between and Maybe I was lucky and was near
the top of the list before but now I am well down the alphabet? :)

Headers below, (btw great geek factor: IPv6 and TLS :)

>Received: from ( [IPv6:2001:4f8:1:d::12]) by (Postfix) with ESMTP id 8481C11416F; Wed, 19 Nov 2008 10:35:25 +0000 
(UTC) (envelope-from dhcp-users-bounces at

>Received: from ( [IPv6:2001:4f8:0:2::1c]) (using TLSv1 
with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "", Issuer 
"ISC CA" (verified OK)) by (Postfix) with ESMTPS id 701CF10E41D 
for <dhcp-users at>; Wed, 19 Nov 2008 09:53:27 +0000 (UTC) 
(envelope-from Glenn.Satchell at


>Date: Wed, 19 Nov 2008 15:12:59 +0000
>From: Evan Hunt <Evan_Hunt at>
>To: Glenn Satchell <Glenn.Satchell at>
>Subject: Re: list reply-to has changed?
>Content-Disposition: inline
>Cc: dhcp-users at
>X-BeenThere: dhcp-users at
>> I notice that with the re-org of the list to that the
>> Reply-to header has disappearred. Previously any message sent to the
>> list got a reply to the list, so everyone saw all messages and
>> solutions were visible in the archives.
>>   Reply-to: dhcp-users at
>> I know this has been a hot topic on just about every mailing list you
>> can imagine, and my intention is not to distract members from working
>> with dhcp questions.
>> Is this an oversight or deliberate decision? The ramification for people 
>> responding is to now hit Reply-all so a copy goes back to the list.
>> If an oversight, can you set it back to the way it was please?
>Thanks for pointing this out.  It was an oversight, and I'm told it's
>been corrected now (check the header of this message to find out for
>Evan Hunt -- evan_hunt at
>Internet Systems Consortium, Inc.
>dhcp-users mailing list
>dhcp-users at

More information about the dhcp-users mailing list