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

Hello Albrecht,

I copied the header partly:

Content-Type: multipart/mixed;

        Content-Type: text/plain; charset=\"iso-8859-1\"

        Content-Type: message/rfc822
        Content-Disposition: attachment;

        Content-Type: multipart/related;

        Content-Type: text/plain; charset=\"iso-8859-1\"

        Content-Type: text/html; charset=\"iso-8859-1\"

        Content-Type: image/png; name=\"ATT00001.png\"
        Content-Description: ATT00001.png
Content-Disposition: inline; filename=\"ATT00001.png\"; size=1275;
        \tcreation-date=\"Fri, 01 Apr 2022 12:12:33 GMT\";
        \tmodification-date=\"Fri, 01 Apr 2022 12:12:33 GMT\"
        Content-ID: <_4_2159F0002159ECA0004301D9C1258817>
        Content-Transfer-Encoding: base64

        Content-Type: image/png; name=\"ATT00002.png\"
        Content-Description: ATT00002.png
Content-Disposition: inline; filename=\"ATT00002.png\"; size=747;
        \tcreation-date=\"Fri, 01 Apr 2022 12:12:33 GMT\";
        \tmodification-date=\"Fri, 01 Apr 2022 12:12:33 GMT\"
        Content-ID: <_4_237AAA58237AA648004301D9C1258817>
        Content-Transfer-Encoding: base64

The company I work for part time uses MS Office and MS Exchange but I use Balsa from my home office. Hope the information above helps.

On 10 Apr 2022 19:51:41, Albrecht Dreß via balsa-list wrote:
Hi Jack:

Am 10.04.22 17:23 schrieb(en) JohnJackDoe tele2 de:
Recently I received an email containing a plain text part and a html part. The contents of both was different.

Are these two parts encapsulated in a multipart/mixed (“mixed parts”) or in a multipart/alternative (“alternative parts”)? In the latter case, the content should actually be the same, according to RFC 2046, Sect. 5.1.4, but this requirement is sometimes violated, in particular by messages created by scripts (usually not by real MUA's)…

So I couldn't read them as one email. Printing was not possible.

…quite often, (commercial, spam) messages are constructed as

text/plain -> with a body reading “your MUA doesn't support HTML” or similar
        text/html -> the real content…
        image/png -> …and some extra stuff referenced by the html

Printing such messages is currently broken in Balsa (see issue #75, item 3), working on that.

If my assumptions are completely wrong, it would be great if you could give more details (or even share the message).

Thanks, Albrecht.

------quoted attachment------
balsa-list mailing list
balsa-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]