Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: rendering HTML: how to disable
Date: Sat, 04 Apr 2015 14:25:46 +0200	[thread overview]
Message-ID: <87619culkl.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87bnj4oguw.fsf@pobox.com>

Bernardo writes:

> luckily (?) i kept an old LinkedIn email and it doesn't establish
> network connections when read, unlike the other one mentioned earlier;
> (checked with Wireshark too, there were no DNS address resolution calls
> either)
>
> however its header says the content is "multipart" rather than
> "text/html" and my guess is the renderer handles it better

Yes, this is what I suspected - with the multipart your configuration of
discouraged alternatives makes Gnus not choose the html-part, but when
there only _is_ text/html, it is displayed (rather than displaying
nothing). That is what "discouraged" is supposed to mean, as far as I
understand it.

That does not explain, however, why you get pictures when it seems like
you the default configuration, which should not fetch them. (Which I
can't reproduce, but maybe I'm doing something different).

> PS
>  didn't know about 'ngrep', looks interesting, will check that too,
>  thanks

I find it much easier to use than tcpdump, wireshark etc. :-)


  Best regards,

    Adam

-- 
 "It troo! Dat darn Kahlfin stole ma spacechip!"              Adam Sjøgren
                                                         asjo@koldfront.dk


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2015-04-04 12:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.14933.1417260021.1147.info-gnus-english@gnu.org>
2014-11-29 19:45 ` Emanuel Berg
2014-11-29 20:50   ` Bernardo
2014-11-29 21:12     ` Adam Sjøgren
2014-11-30  6:25       ` Bernardo
2014-11-30 12:07         ` Adam Sjøgren
2014-12-01 21:40           ` Bernardo
2014-12-01 21:53             ` Adam Sjøgren
2014-12-02 10:38               ` Bernardo
2014-12-02 10:43                 ` Adam Sjøgren
     [not found]     ` <mailman.14972.1417295555.1147.info-gnus-english@gnu.org>
2014-11-29 23:16       ` Emanuel Berg
2014-11-29 23:22         ` Adam Sjøgren
     [not found]         ` <mailman.14977.1417303389.1147.info-gnus-english@gnu.org>
2014-11-29 23:42           ` Emanuel Berg
2014-11-29 23:46             ` Adam Sjøgren
2014-11-30  4:00       ` Mike Kupfer
2014-11-30 11:31         ` Adam Sjøgren
2014-11-30 11:48         ` Adam Sjøgren
2014-11-30 12:07           ` Adam Sjøgren
2014-11-30 12:09             ` Adam Sjøgren
     [not found]           ` <mailman.14993.1417349281.1147.info-gnus-english@gnu.org>
2014-11-30 15:49             ` Mike Kupfer
2015-04-03  8:22     ` Bernardo
2015-04-03  9:57       ` Adam Sjøgren
2015-04-03 11:50         ` Bernardo
2015-04-03 12:05           ` Adam Sjøgren
2015-04-03 12:09             ` Adam Sjøgren
2015-04-04  0:51               ` Bernardo
2015-04-04 12:25                 ` Adam Sjøgren [this message]
     [not found]     ` <mailman.3220.1428049535.31049.info-gnus-english@gnu.org>
2015-04-03 18:27       ` Emanuel Berg
2014-11-29  8:57 Bernardo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87619culkl.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=info-gnus-english@gnu.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.
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 NNTP newsgroup(s).