Re: Fwd: Re: Fwd: Re: printing problem (no remote images)

--===============4005871838286896960==
Content-Type: multipart/signed; micalg=PGP-SHA512;
	protocol="application/pgp-signature"; boundary="=-nO6yV23SL83ESFEQ9omW"

--=-nO6yV23SL83ESFEQ9omW
Content-Type: text/plain; charset=UTF-8; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Jack,

thanks a lot for testing!

Am 19.06.22 15:40 schrieb(en) John Doe via balsa-list:
> The email in question contains a plain text part with a plain text/HTML a=
ttachment. This plain text/HTML attachment can only be printed after tickin=
g 'force inline for all parts' (see attached screen dump).

This is usually controlled by the =E2=80=9CContent-Disposition=E2=80=9D hea=
der of every part.  RFC 2183, Sect. 2.1 and 2.2 define that

> a bodypart should be marked `inline' if it is intended to be displayed au=
tomatically upon display of the message

and

> bodyparts can be designated `attachment' to indicate that they are separa=
te from the main body of the mail  message, and that their display should n=
ot be automatic, but contingent upon some further action of the user.

In libbalsa/body.c, function libbalsa_message_body_is_inline() a comment st=
ates that

> Default disposition is in-line for text/plain, and generally attachment f=
or other content types.

Thus, I can only guess that the HTML attachment either is explicitly marked=
 as =E2=80=9Cattachment=E2=80=9D or lacks that header, resulting in the beh=
aviour you observed.  However, iff balsa has been built with HTML support, =
we might actually want to default to inline for HTML attachments, too (and =
the aforementioned function looks a little fishy anyway, btw).  I'll look i=
nto that, but only after my vacation (without computer=F0=9F=98=89=EF=B8=8F=
), so please don't expect any progress within the next ~3 weeks=E2=80=A6

Best,
Albrecht.
--=-nO6yV23SL83ESFEQ9omW
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEcCEPemLFTtyGf4zATKlvDmfn2fgFAmKzO6IACgkQTKlvDmfn
2fiQkgf9H2wtNhECxYYO7XGOZueU0L4sEyWB1WFvEbsFUGGZoOoIHwfv1QFpaZns
KaNYnEGWpgwHQbBCdZyyJQINYjA+2mZqzC3NyujJFGO0CQpsCXOUkiVVcn8TvNI0
cDixgTYSQbgW0FyjYJ7X3Ib2LP3STkHAOA0lQLzmeorXZMiEvqt9pycYzhcTDhwH
1FIpiIj7cEIvDD9Tahnygl4z+rMMGrcInPyQzI0xYFZ+RTSs/nUluxl4t0Uk4GFi
25zr/k9NmLdYUxU3du/OvVVAexvAaI1PmdQ5T1QXXb72m+MoyzteCIaVV/e0Tf0y
eUL+e37KLLtsEWqDO2bUjBkoIkvG0g==
=OWEw
-----END PGP SIGNATURE-----

--=-nO6yV23SL83ESFEQ9omW--

--===============4005871838286896960==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list

--===============4005871838286896960==--