Using gmail with mutt (2016)

Re:Using gmail with mutt (2016) by funzis on Monday April 30, 2018 @06:14PM (#16962911)

I've been using mutt as my only email client for over 10 years now. You are right that a lot of emails are HTML only, but you can use something like w3m or lynx to render the HTML inside of mutt, and it is pretty rare that images in emails actually matter. (Mostly they are company logos or other non-useful crap...)

[ Parent | on HN ]

Re:Using gmail with mutt (2016) by zAy0LfpBZLC8mAC on Monday April 30, 2018 @07:09PM (#16963305)

And even better: You avoid loading any external resources, which both avoids the data leak, and prevents the sender from modifying the content of the received email.

[ Parent | on HN ]

Re:Using gmail with mutt (2016) by lstamour on Monday April 30, 2018 @11:19PM (#16964364)

Gmail relatively recently changed to intercept images and cache them all for you, preventing the leak. But then, this is Google we’re talking about. I’m sure there’s still a leak, maybe via AMP for Email. (Of course, hyperlinks are also often used for tracking.)

[ Parent | on HN ]

Re:Using gmail with mutt (2016) by zAy0LfpBZLC8mAC on Tuesday May 01, 2018 @07:23AM (#16966114)

Only images? So, fonts can still be used to leak and manipulate?

[ Parent | on HN ]

Re:Using gmail with mutt (2016) by lstamour on Tuesday May 01, 2018 @10:21PM (#16973574)

Well, no, custom web fonts generally aren’t supported by email clients, email within Gmail is sanitized by default.

And I stand slightly corrected: by customizing email image URLs, you can apparently track the first open, but not user details (IP address, device, subsequent opens, etc.) https://customer.io/blog/gmail-loading-images.html

[ Parent | on HN ]

Re:Using gmail with mutt (2016) by swiley on Monday April 30, 2018 @08:29PM (#16963731)

When I use the web mail I always keep images off anyway.

[ Parent | on HN ]