From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: oub@mat.ucm.es, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs/Mutt and Efail or OpenPGP is safer than S/MIME?
Date: Wed, 16 May 2018 20:38:25 +0300 [thread overview]
Message-ID: <831sebjyb2.fsf@gnu.org> (raw)
In-Reply-To: <87lgcjo736.fsf@igel.home> (message from Andreas Schwab on Wed, 16 May 2018 19:15:09 +0200)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: rms@gnu.org, oub@mat.ucm.es, emacs-devel@gnu.org
> Date: Wed, 16 May 2018 19:15:09 +0200
>
> On Mai 16 2018, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > E.g., Rmail renders HTML messages, but doesn't access external URL
> > references, it creates a button out of each reference that the user
> > needs to activate to cause Emacs to fetch the URL.
>
> There is a difference between anchors that form links to other pages,
> and elements like images that are part of the contents, but use external
> references (instead of using data that is part of the message). In
> order to render the latter the external reference must be fetched.
I agree that there's a difference, but a good MUA should treat them
the same, and only download images after the user confirms.
(And private/secret correspondence shouldn't include such external
references in the first place, IMHO.)
next prev parent reply other threads:[~2018-05-16 17:38 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 8:44 Emacs/Mutt and Efail or OpenPGP is safer than S/MIME? Uwe Brauer
2018-05-15 9:42 ` Lars Ingebrigtsen
2018-05-15 19:26 ` Uwe Brauer
2018-05-15 21:48 ` Lars Ingebrigtsen
2018-05-16 8:22 ` Uwe Brauer
2018-05-16 9:31 ` Lars Ingebrigtsen
2018-05-16 9:56 ` Lars Ingebrigtsen
2018-05-16 8:43 ` Uwe Brauer
2018-05-16 9:32 ` Lars Ingebrigtsen
2018-05-16 10:24 ` Uwe Brauer
2018-05-16 10:30 ` Lars Ingebrigtsen
2018-05-16 2:52 ` Richard Stallman
2018-05-16 8:24 ` Uwe Brauer
2018-05-16 9:30 ` Lars Ingebrigtsen
2018-05-17 3:03 ` Richard Stallman
2018-05-17 7:16 ` Robert Pluim
2018-05-16 15:56 ` Eli Zaretskii
2018-05-16 17:15 ` Andreas Schwab
2018-05-16 17:38 ` Eli Zaretskii [this message]
2018-05-16 18:58 ` Andreas Schwab
2018-05-18 2:30 ` Richard Stallman
2018-05-18 12:37 ` Uwe Brauer
2018-05-18 14:05 ` Lars Ingebrigtsen
2018-05-19 8:29 ` Uwe Brauer
2018-05-19 9:59 ` Eli Zaretskii
2018-05-19 10:08 ` Uwe Brauer
2018-05-19 10:12 ` Lars Ingebrigtsen
2018-05-20 3:15 ` Richard Stallman
2018-05-20 3:15 ` Richard Stallman
2018-05-20 17:33 ` Uwe Brauer
2018-05-21 4:15 ` Richard Stallman
2018-05-20 17:34 ` Lars Ingebrigtsen
2018-05-21 4:15 ` Richard Stallman
2018-07-22 13:58 ` Lars Ingebrigtsen
2018-05-16 19:52 ` Joost Kremers
2018-05-17 3:05 ` Richard Stallman
2018-05-17 3:05 ` Richard Stallman
2018-05-17 15:09 ` Eli Zaretskii
2018-05-18 2:34 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831sebjyb2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).