3 ms·
A typical Mutt configuration relies on the entry for text/html in ~/.mailcap. It's quite common to use lynx for rendering, as in the following: text/html;
by wampus 12y ago
A typical Mutt configuration relies on the entry for text/html in ~/.mailcap. It's quite common to use lynx for rendering, as in the following:
text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
Since lynx doesn't load images, that would be safe from this kind of tracking. But another configuration using a different renderer might allow it.
Furthermore, it is also possible to prefer the plaintext version of an email if there's a choice. From my ~/.muttrc:
alternative_order text/plain text text/html
I can't remember ever being put out by not being able to read messages that fetch images from the web. Even if I have to open a URL, I do it in Firefox, where I run RequestPolicy.
- gcr 12y agoAre you sure lynx doesn't fetch any external resources? Some text-mode browsers (I forget if elinks or w3m does this) fetches external CSS by default so they can attempt to render fonts on the the 16-color terminal. :) The "right" way of doing this (calling lynx in a network-restricted cgroup/chroot/container) sounds like a pain.
- wampus 12y agoLynx doesn't support images, CSS or script. It does support cookies and redirects (by default it prompts for both). Basically, it renders the bare HTML of the page you open, without fetching external resources. If you find it behaves differently, make sure your lynx command isn't actually symlinked to links (or another text browser with graphical/enhanced capabilities).