28 lines
1.1 KiB
Plaintext
28 lines
1.1 KiB
Plaintext
MBOX-Line: From arnt at gulbrandsen.priv.no Sat Feb 16 12:30:59 2008
|
|
To: imap-protocol@u.washington.edu
|
|
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
|
|
Date: Fri Jun 8 12:34:41 2018
|
|
Subject: [Imap-protocol] header.fields fetching
|
|
In-Reply-To: <8782ACCD-1349-445D-BEAA-EB5409610D24@iki.fi>
|
|
References: <1203188859.4901.147.camel@hurina>
|
|
<rLpAj0qCNeD2mVCkSSk87w.md5@libertango.oryx.com>
|
|
<8782ACCD-1349-445D-BEAA-EB5409610D24@iki.fi>
|
|
Message-ID: <oeGcRgEh/G5xGlxJ8jHQ3g.md5@libertango.oryx.com>
|
|
|
|
Timo Sirainen writes:
|
|
> Note that I'm specifically talking about HEADER.FIELDS fetching.
|
|
> Fetching the entire message, the header of the message or
|
|
> HEADER.FIELDS.NOT would show the headers in their original form. Your
|
|
> answer sounded more like you assumed the headers were permanently
|
|
> changed for all of them.
|
|
|
|
I think it's the same issue. IMO it's (usually but not invariably) the
|
|
same issue even if the the strings are changed only by the display
|
|
agent before display.
|
|
|
|
What matters is what the user sees. Or rather, what the user understands
|
|
(To: tss in times is the same as To: tss in courier, say I).
|
|
|
|
Arnt
|
|
|