MBOX-Line: From blong at google.com  Wed May 20 12:29:51 2015
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun  8 12:34:55 2018
Subject: [Imap-protocol] Registration of keyword which enables fetching
 external images
In-Reply-To: <CALFQBW3kRQo3S27Sq9a5r__AvLshN36n5FP8U9P23zSrcqeeWA@mail.gmail.com>
References: <5f24e38f-5968-4367-97f6-fa4008f582fd@flaska.net>
	<14D026C7F297AD44AC82578DD818CDD047B37C34E0@TUS1XCHEVSPIN35.SYMC.SYMANTEC.COM>
	<c4a7510f-bd4a-49cb-abda-e6b1b1448078@flaska.net>
	<CALFQBW3kRQo3S27Sq9a5r__AvLshN36n5FP8U9P23zSrcqeeWA@mail.gmail.com>
Message-ID: <CABa8R6uW8vXuvoAVoSYy_JOs8U9jNeGFgL7b0Siz3OSmxrq0cA@mail.gmail.com>

On Wed, May 20, 2015 at 12:07 PM, Andrew Sutherland <asuth@mozilla.com>
wrote:

> On Wed, May 20, 2015 at 8:47 AM, Jan Kundr?t <jkt@flaska.net> wrote:
>
>> Are some other client developers interested in this?
>
>
> It seems reasonable to me to standardize a flag for this purpose, even if
> many clients prefer to keep the setting local-only.  Thunderbird uses a
> per-message "remoteContentPolicy" property that is persisted locally in the
> msf files but never persisted to IMAP servers.  Once set, it allows
> external images for the specific messages to be fetched going forward.
>  (Some information leakage will be suppressed on repeated viewings because
> of the network cache, but the images/etc. are likely to be rotated out.)
>
> Note: I no longer actively contribute to Thunderbird, so if anyone is
> going to change things to use the flag it won't be me.  I work on the
> Firefox OS email app, and we currently have no plans to persist "show
> extenal images" on a per message basis, but if we did, we would use the
> proposed flag since we would synchronize the flag to the server when
> possible.
>

I think we persist per sender, not per message... and we know proxy most of
that stuff, so I think a lot of users just show all messages... or we have
some complicated logic about when it's ok to show and when it's not which
is calculated on the fly and not exposed.

Not opposed to a standard, of course, just seems unlikely we'll use it.

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20150520/e6c1af94/attachment.html>
