On 2020-04-23 09:47:08 +0200, Claus Assmann wrote:
> On Wed, Apr 22, 2020, Kevin J. McCarthy wrote:
>
> > I think I would prefer to make "exact address" deprecated in 1.14 and remove
> > it for 1.15.
>
> Then I would not upgrade to 1.15 (not that anyone would care...)
>
> I hate it if a program "hides" the actual data and instead presents
> some form its authors prefer - hiding information is generally a
> bad idea unless it's for lusers.
If I understand correctly, "exact address" does 2 things:
(1) it displays the address fields as they are, i.e. does not "hide"
the actual data;
(2) it keeps the obsolete form when replying.
And the reported issue (bad generated encoding) was for (2).
So, maybe drop only (2).
> It's annoying when someone tells me there is a problem in one of
> the MTAs that I maintain because it would mishandle some addresses
> but those addresses are actually not the ones which the MTA receives
> (just like a certain MTA logs addresses differently then they
> actually were - and it's not a bijective mapping. I wasted a lot
> of time trying to debug those cases).
In any case, Mutt will not show the actual data, because it does
MIME decoding of the headers. Some MUAs have a feature to show the
"raw headers", but not Mutt, AFAIK. However, I don't think that
this is an issue, as one can pipe the raw message to a pager,
which has more or less the same effect (one does not benefit from
Mutt's coloring, but is that important?). Thanks to this pipe
feature, I would not need "exact address" at all.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
