[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Changes to forw(1)
From: |
David Levine |
Subject: |
Re: [Nmh-workers] Changes to forw(1) |
Date: |
Thu, 13 Oct 2016 20:05:18 -0400 |
Ken wrote:
> I can boil it down to this: these headers may leak out, if there are bugs
> or unusual behavior. But I have realized ... I don't care.
I do care. "Be conservative in what you do"
> Thinking about it more, we already leak some "internal" headers out.
Water under the bridge. Let's do the right thing moving forward.
You mentioned "harm": it depends on how that's defined. Sure, MUAs can
igore headers, so no harm there. But, I define each of intentionally
withholding traceability and polluting a namespace as harmful.
> I mean, yeah, it's not something we should do,
Then let's not.
David
- Re: [Nmh-workers] Changes to forw(1), (continued)
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/13
- Re: [Nmh-workers] Changes to forw(1), Ralph Corderoy, 2016/10/13
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/13
- Re: [Nmh-workers] Changes to forw(1), Ralph Corderoy, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), Paul Fox, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), David Levine, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), Ralph Corderoy, 2016/10/15
- Re: [Nmh-workers] Changes to forw(1),
David Levine <=
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/13
- Re: [Nmh-workers] Changes to forw(1), David Levine, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), David Levine, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), Paul Fox, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), Ken Hornstein, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), Robert Elz, 2016/10/14
- Re: [Nmh-workers] Changes to forw(1), Ralph Corderoy, 2016/10/15
- Re: [Nmh-workers] Changes to forw(1), Steffen Nurpmeso, 2016/10/15
- Re: [Nmh-workers] Changes to forw(1), David Levine, 2016/10/14