How to view attached images as part of the e-mail?

Most other e-mail clients have the (IMHO obvious) functionality that attached images will simply be displayed at the bottom of the e-mail. Someone sends you a bunch of photos, you scroll down, boom, there they are. Claws-Mail and Thunderbird on the desktop work like that, as does FairEmail on Android.

In K-9 however, I do not get to see the pictures. There’s only an indication that attachments exist. I can view the files as attachments and when I tap on them, it’ll open them in the default image viewing app. But I have to do this for every single photo. Tap to open, then go back and tap on the next, etc. Instead of just scrolling through the bunch of them.

I’m sure I’m just too stupid to find the setting to fix this. There’s the option for viewing images under account settings → reading mails where you can select “never”, “only from contacts”, or “always”. But setting it to “always” doesn’t change anything, and I assumed that is a slightly different function anyway (referring to embedded image links in HTML, often used for tracking purposes).

Can someone point me to the correct setting?

Hi @NeedMoreCoffee

Welcome to the forum.

This issue is discussed in this thread where you’ll find more information.

The developers are working on a fix for the feature regression.

Huh. I thought that thread was referring to a different function (inline HTML image links for tracking).

Why would there even be a need to disable showing images that are already part of the e-mail? Maybe to minimize traffic, but then I’d expect the control option to read something like “display images → always/only in wifi/never”. Not based on the contact.

No, the regression followed a change to move attachments from the bottom on an email chain to a summary row at the top. This resulted in attached images not being displayed at the bottom of emails any longer. Users also report attached inline images not being displayed. Both needing to be opened in an external viewer.

Developers are working on a fix.

See designers feedback here and fix development here.

Ah! Well, thanks for clearing that up! :+1: