Re: [Tools-discuss] Step backwards: <noreply@ietf.org>

On Wed, Mar 13, 2019 at 2:27 PM Adam Roach <adam@nostrum.com> wrote:

> On 3/12/19 10:57 PM, Henrik Levkowetz wrote:
> >
> > Since this was becoming increasingly troublesome, as more and more
> > domains were adopting stricter SPF settings, we've stopped sending
> > mail purporting to be sent by <reviewer@reviewers.domain>, and are
> > now sending from <noreply@ietf.org>, but we missed adding a Reply-To:
> > header field that would make replies work as before.
>
>
> By the way, this dovetails well into a conversation we had earlier about
> responses to IESG ballots being attached to the ballots, so that the
> entire conversation ends up in the ballot. This would greatly simplify
> the task of IESG members attempting to validate whether review comments
> received responses (and what those responses were). Please consider
> changing <noreply@ietf.org> to instead be <unique-token@ietf.org>, and
> make mail sent to <unique-token@ietf.org> turn into a comment which is
> then appended to whatever data structure originated the initial email.
>
>
Wow, that would be incredibly awesome.

W

> /a
>
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
>
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org
>

-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf