Noreply (was: Last Call: <draft-ietf-netmod-ip-cfg-09.txt> (A YANG Data

Hi Clint,
At 13:39 22-04-2013, Clint Chaplin wrote:
> Why did this (and the other most recent) last 
> call also not go to IETF-Announce?
Here are some partial headers:

  From: The IESG <noreply(_at_)ietf(_dot_)org>
  To: IETF-Announce:;
  Subject: Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data
        Model for Interface Management) to Proposed Standard
  Message-ID: 
<20130419132524(_dot_)1622(_dot_)39563(_dot_)idtracker(_at_)ietfa(_dot_)amsl(_dot_)com>
  Date: Fri, 19 Apr 2013 06:25:24 -0700
  Cc: netmod(_at_)ietf(_dot_)org
  Reply-To: IETF Discussion List <ietf(_at_)ietf(_dot_)org>
  List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
  List-Post: <mailto:ietf-announce(_at_)ietf(_dot_)org>

I don't know who had the idea [1] to have the 
IESG use the noreply(_at_)ietf(_dot_)org email address 
[2].    The List-Post: mailto needs some work. :-)
Regards,
-sm

1. Mornië alantië
2. In all cases, the "From:" field REALLY 
[RFC6919] SHOULD NOT contain any mailbox that 
does not belong to the author(s) of the message.