Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  nodelist  faq  login

In computing, the mean time to failure keeps getting shorter.


computers / comp.mail.mutt / Re: Problem emails

SubjectAuthor
* Problem emailscjsmall
+* Re: Problem emailsEike Rathke
|`* Re: Problem emailscjsmall
| `- Re: Problem emailsEike Rathke
`- Re: Problem emailsPeter Pearson

1
Subject: Problem emails
From: cjsmall
Newsgroups: comp.mail.mutt
Date: Tue, 12 Jan 2021 01:29 UTC
X-Received: by 2002:ae9:c107:: with SMTP id z7mr2267840qki.160.1610414947918;
Mon, 11 Jan 2021 17:29:07 -0800 (PST)
X-Received: by 2002:a37:9583:: with SMTP id x125mr2251300qkd.75.1610414947683;
Mon, 11 Jan 2021 17:29:07 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.mutt
Date: Mon, 11 Jan 2021 17:29:07 -0800 (PST)
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=67.160.27.106; posting-account=HkkpOQkAAADsR9HpuB7NpuJa7KNw-XVw
NNTP-Posting-Host: 67.160.27.106
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <83e48b8c-5caf-44b8-b9f7-d4fc0ef09b8dn@googlegroups.com>
Subject: Problem emails
From: jefferys...@gmail.com (cjsmall)
Injection-Date: Tue, 12 Jan 2021 01:29:07 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 187
View all headers
I'm running mutt 1.13.2 on an Xubuntu 20.04 system.

I have problems with certain base64-encoded emails.  I've noticed that they often originate on MacOS machines.  This one I'm discussing appears to have been generated in MacOutlook.  From the header:

user-agent: Microsoft-MacOutlook/16.44.20121301

When I try to view the message in mutt, I just see the raw encoded body.  When I press v and look at the attachments, mutt doesn't see any. this is what's reported on the attachment screen:

I   1 <no description>                      [text/plain, 7bits, 2.7M]

Something is ill-formed.  When I save the entire email and run munpack on it, the eleven embed images are unpacked, but the text and html sections are not.  Here is what munpack reports:

munpack: warning: Premature EOF
tempdesc.txt: File exists
image001.png (image/png)
image002.png (image/png)
munpack: warning: Premature EOF
image003.png (image/png)
image004.png (image/png)
image005.png (image/png)
image006.png (image/png)
munpack: warning: Premature EOF
image007.png (image/png)
munpack: warning: Premature EOF
image008.png (image/png)
image009.png (image/png)
image010.png (image/png)
image011.jpg (image/jpeg)
munpack: warning: Premature EOF

I'm no expert in mail format so I could use some help determining what's going on.  Below is a representation of the email.  I have replaced big sections with [[comments]] but left the Content-Type: blocks for examination.  When you see a [[base64 comment] sitting directly above the --014_* closing line or with a blank line between, this is just how it appears in the message body.  I suspect the missing blank lines are what's responsible for the "Premature EOF" warnings above.

Any ideas what's wrong with the message and why mutt and munpack cannot see the first two blocks?  If I knew what was wrong, I might be able to sent my messages through a pre-delivery filter and fix it.  Thanks for any insights.

Message:

[[Normal Email Header]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: multipart/alternative;
        boundary="_000_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_"

--_000_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

[[Base64 encoded text]]
--_000_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: text/html; charset="utf-8"
Content-ID: <94A071F24B517345833E0486257D0BA3@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

[[Base64 encoded html]]

--_000_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_--
--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image001.png"
Content-Description: image001.png
Content-Disposition: inline; filename="image001.png"; size=5563;
        creation-date="Mon, 11 Jan 2021 20:01:50 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:50 GMT"
Content-ID: <image001.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image002.png"
Content-Description: image002.png
Content-Disposition: inline; filename="image002.png"; size=1883;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image002.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]
--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image003.png"
Content-Description: image003.png
Content-Disposition: inline; filename="image003.png"; size=1824;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image003.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image004.png"
Content-Description: image004.png
Content-Disposition: inline; filename="image004.png"; size=2070;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image004.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image005.png"
Content-Description: image005.png
Content-Disposition: inline; filename="image005.png"; size=1671;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image005.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image006.png"
Content-Description: image006.png
Content-Disposition: inline; filename="image006.png"; size=5570;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image006.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]
--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image007.png"
Content-Description: image007.png
Content-Disposition: inline; filename="image007.png"; size=1892;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image007.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]
--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image008.png"
Content-Description: image008.png
Content-Disposition: inline; filename="image008.png"; size=1833;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image008.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image009.png"
Content-Description: image009.png
Content-Disposition: inline; filename="image009.png"; size=2079;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image009.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/png; name="image010.png"
Content-Description: image010.png
Content-Disposition: inline; filename="image010.png"; size=1680;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:51 GMT"
Content-ID: <image010.png@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: image/jpeg; name="image011.jpg"
Content-Description: image011.jpg
Content-Disposition: inline; filename="image011.jpg"; size=2067743;
        creation-date="Mon, 11 Jan 2021 20:01:51 GMT";
        modification-date="Mon, 11 Jan 2021 20:01:52 GMT"
Content-ID: <image011.jpg@01D6E82A.AFD83160>
Content-Transfer-Encoding: base64

[[Base64 encoded image]]
--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_--


Subject: Re: Problem emails
From: Eike Rathke
Newsgroups: comp.mail.mutt
Organization: possibly
Date: Tue, 12 Jan 2021 14:29 UTC
References: 1
Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: erack+nu...@posteo.de (Eike Rathke)
Newsgroups: comp.mail.mutt
Subject: Re: Problem emails
Date: 12 Jan 2021 14:29:19 GMT
Organization: possibly
Lines: 34
Message-ID: <N3e8I5ffdb1d2T42af@kulungile.erack.de>
References: <83e48b8c-5caf-44b8-b9f7-d4fc0ef09b8dn@googlegroups.com>
X-Trace: individual.net mjUQeSzqmrQ/Q21JpJur0A1ejlCH5HILauJrjp0gYsA6nBYCg=
Cancel-Lock: sha1:etVgH6R5ueIt54L/iV4mERVvxxM=
X-Accept-Language: de,en
X-PGP-Hash: SHA256
X-PGP-Key: 0x6A6CD5B765632D3A
X-PGP-Sig: GnuPG-v2 From,Newsgroups,Subject,Message-ID
iQIzBAEBCAAdFiEEImXX86ewlcw5GGMLamzVt2VjLToFAl/9sdIACgkQamzVt2Vj
LTov8w/+PYi2isNdw0FSBO7PooRN3OqiXiDdIzF5J87CKrtd8+KZcs5nEfg/Hp0g
8wRyyqdGyLQyk/msJxpYtxWyW5UuE69BWBxyah5CwtuUJG06+7GO4Vl0eMv58se2
qy754CvnwwuUTRVoIUfa1O7x1nTJa9t/UdDxAPmJFDxzyBThdhqPFCLmgcef0C8N
GUyLqmAjIMFljL+HITttBrAu2FEELZZ6JPUyTjl4QulelIChn8ofqF+qEaC44TzN
g02n7371UOw2vt17qreklWRDyABPcyBV9DCVt/asgYd3IUvJyqCxt+sIwpm+ZABZ
7NZaCZaP5OuLUglOH8ZxJDW/vyXk9HIe9BVO+dtIo4O/gMb4+WDh5LRepGRUsWvG
FuyIPphEzxsS+dJ9W0BBIbBrJ4T4N/PFU2xUS4sZq4lb+h0x82QhY4d87vlmw7bx
EZXGrAS+KmZq8ohRkyiuMg4WcYNTJVbRjQT0nAx/1Rlfla957YqBSrI26cz4pngo
EkN/txpdWOhZBgGzqblDUGaIf+4rMtS3RNPbF+g1gtH6SKoM+6uC39rRuRED9eK/
A2fxdNEmFlnhTz59epnPDnlmeI2M0z3tjEsR5T4DSDaEI2UplHIiXi3hSX/d8OvN
O+/7Sbi6EBRL0piNRuXCTgRGcNegQpqjVqpkuX8dBkh4a5zsyFM= =NisL
User-Agent: slrn/1.0.3 (Linux)
View all headers
* cjsmall, 2021-01-12 01:29 UTC:
When I try to view the message in mutt, I just see the raw encoded body.  When I press v and look at the attachments, mutt doesn't see any. this is what's reported on the attachment screen:

I   1 <no description>                      [text/plain, 7bits, 2.7M]

Any ideas what's wrong with the message and why mutt and munpack cannot see the first two blocks?  If I knew what was wrong, I might be able to sent my messages through a pre-delivery filter and fix it.  Thanks for any insights.

Message:

[[Normal Email Header]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: multipart/alternative;
        boundary="_000_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_"
[...]
--_000_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_--
--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_

Apparently the message has nested multiparts, does that "Normal Email
Header" contain a

Content-Type: multipart/...; ...;
 boundary="_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_"

header? If not, that's the answer to why you're seeing only one
"attachment" and munpack just seems to get a boundary here from *within*
the text/plain stream.

  Eike

--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
Use LibreOffice! https://www.libreoffice.org/


Subject: Re: Problem emails
From: cjsmall
Newsgroups: comp.mail.mutt
Date: Tue, 12 Jan 2021 19:41 UTC
References: 1 2
X-Received: by 2002:ad4:4952:: with SMTP id o18mr617985qvy.27.1610480493446; Tue, 12 Jan 2021 11:41:33 -0800 (PST)
X-Received: by 2002:a37:6692:: with SMTP id a140mr1080130qkc.0.1610480493167; Tue, 12 Jan 2021 11:41:33 -0800 (PST)
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!tr3.eu1.usenetexpress.com!feeder.usenetexpress.com!tr2.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.mutt
Date: Tue, 12 Jan 2021 11:41:32 -0800 (PST)
In-Reply-To: <N3e8I5ffdb1d2T42af@kulungile.erack.de>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=67.160.27.106; posting-account=HkkpOQkAAADsR9HpuB7NpuJa7KNw-XVw
NNTP-Posting-Host: 67.160.27.106
References: <83e48b8c-5caf-44b8-b9f7-d4fc0ef09b8dn@googlegroups.com> <N3e8I5ffdb1d2T42af@kulungile.erack.de>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3c45ce00-32af-4c34-8873-852fa5f825bdn@googlegroups.com>
Subject: Re: Problem emails
From: jefferys...@gmail.com (cjsmall)
Injection-Date: Tue, 12 Jan 2021 19:41:33 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 56
View all headers
On Tuesday, January 12, 2021 at 6:29:20 AM UTC-8, Eike Rathke wrote:

Apparently the message has nested multiparts, does that "Normal Email
Header" contain a

Content-Type: multipart/...; ...;
boundary="_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_"

header? If not, that's the answer to why you're seeing only one
"attachment" and munpack just seems to get a boundary here from *within*
the text/plain stream.

Thanks for the reply, Eike.

No, there is no Content-Type: line in the header.  The first such line is in the body as shown above.  The message seems to have gone through a Microsoft mail server and the following line is in the header, but it's not applicable:

x-ms-exchange-antispam-messagedata:
 =?utf-8?B?VW1qYkxUb1c2aTF5REFRR2RtMDQ4eGFkUnRaZUpDRjdrOFZESjlNcVZHZmlM? =?utf-8?B?RWZpR295RCtuUno0ekttNmVJTnpOb2RpcXJ3QW1Vd29VS2NDNzFUQVhyVStI? =?utf-8?B?UFhPYTl3eWpyZlVkNmZ0c2swalIrdllKaWFvTEgvWXZhNm9PN1BvS0E5TEZV? =?utf-8?B?KzkySW02NVB0aWd1QWhMSUdQVWF0ZlV1TGRQWTYwUCsyRENhb285dU9oeDlU? =?utf-8?B?VUJuWUxROHlCaFMybU16WFR1Yys4R2o4Q2MyRmpoYzBkZTFzVGZXQlYvZlk1? =?utf-8?B?ZnlKNnVPOVBieTlzN1lUdGFjR2U3cHFxTTBxTmFlMGU1cjRMQ3ZkMTFzeXhh? =?utf-8?B?SkN4T2pJSjcyMHVYTTR6cGZUZDhzS3R1VFdjRVZRUWY5Q2FHNTlWR1J3SStv? =?utf-8?B?b1RWdVVLQkV4MldXQnRnZHQyTTU3OWNwelVIVS80bS9xMm1MQmU3NXExNWJC? =?utf-8?B?QXJBVEdmcjhrTnVCTThjRWlzVEJwYXZiMUx6Z0lWNzhOQTMxcWdTY2owaVVT? =?utf-8?B?YWdtOWtvMi9IWVlQRjlTMmUrTnhGUkFRb29PdytVaW5hcFJvM0s1Y05xT1NB? =?utf-8?B?akNGNG5HcVR2SmllVVhRVUxaSjNoK3NRVW1semVNOHdRNittOEhKYXNBTUkv? =?utf-8?B?c09WOTQ4NnVtV3NsVGxCT0c3dXcwWEZEeWFNNlV0SmZEcVZLTUh0QjhnMVVh? =?utf-8?B?WklEcTVZeFovQzJHVFNqYUFacm9rZW12SUdXTit5Y1NOY0hRS3RxZWtjbGFv? =?utf-8?B?WXpKRk16YlIxbGpqNlRERmdoaDdiSlUyNlNTNmNMNFBTbENGVFZSRXBCb3RV? =?utf-8?B?bHZabG03d2VBWEI1NEdDbmZ1S1BWalF6c3NGS2lBQVJiWWR4L0pVQ1ZJMTZs? =?utf-8?B?M2x1ajRWRUdONnpjZlJNVU9CV0xsTHlHZ2V3TVg3RUZHNmgyYmpVSFRFalIx? =?utf-8?B?LzhLSFlucnVRTW5yZ0lhVmpKY2VFcHhZNktBWlRLU2IrWkdkaS9tZjVVaFBt? =?utf-8?B?QmFxb1pOSzYvMEtaNG8rbTZiWUhzMEZ5Y3JzQUwzRm5rWFNiamdLWEYwUHJY? =?utf-8?B?U2pOckV5UDRuSE5HSjI3dk1zLzQ3dzhhVFpYLy9OUlk4OUJDQWlnd29WcmRh? =?utf-8?B?dTU4Q003UkVpdVBicENYQkF2SENPdUNleWIxL0JNSm9pNzgvVjU5WGJhUG92? =?utf-8?B?TGxsUkVTY3g5clcvY2pZQU8yOVNIeFNTdW9UQXkzdEtwKzl2SHhFRUw0M2I0? =?utf-8?B?aUtVbm8xdGpkL3ZnMm5NZFR4dlpxOWFXaFcyY2xjUnBWQ2xhUEVibUlTZFJ2? =?utf-8?Q?8hyfyw1KAK+py9GCQQq4dNiMX86FzJRQF1?Content-Type: multipart/related;
        boundary="_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_";
        type="multipart/alternative"

Any idea where the message is getting mangled?  As I said, I've seen this problem from some other people using Macs, so is Apple doing something bad or could the header be getting screwed up by something like the Microsoft email server?

I also still don't understand why the image blocks can be munpacked but why the first two blocks are skipped.  Since mutt doesn't show any attachments, does it just not look for them because the Content-Type: header line is missing?


Subject: Re: Problem emails
From: Eike Rathke
Newsgroups: comp.mail.mutt
Organization: possibly
Date: Tue, 12 Jan 2021 21:40 UTC
References: 1 2 3
Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: erack+nu...@posteo.de (Eike Rathke)
Newsgroups: comp.mail.mutt
Subject: Re: Problem emails
Date: 12 Jan 2021 21:40:18 GMT
Organization: possibly
Lines: 35
Message-ID: <N3e8I5ffe1708T37f3@kulungile.erack.de>
References: <83e48b8c-5caf-44b8-b9f7-d4fc0ef09b8dn@googlegroups.com>
<N3e8I5ffdb1d2T42af@kulungile.erack.de>
<3c45ce00-32af-4c34-8873-852fa5f825bdn@googlegroups.com>
X-Trace: individual.net lQspqwkqErK/XQ4Roth5SQgj4tNf2GU/F61MP3f4RipZgAiWo=
Cancel-Lock: sha1:RNNC6dXPKIABU7CT+vEFMJGKsZ4=
X-Accept-Language: de,en
X-PGP-Hash: SHA256
X-PGP-Key: 0x6A6CD5B765632D3A
X-PGP-Sig: GnuPG-v2 From,Newsgroups,Subject,Message-ID
iQIzBAEBCAAdFiEEImXX86ewlcw5GGMLamzVt2VjLToFAl/+FwkACgkQamzVt2Vj
LTq79BAAg9KsLqN9W3JxlXJ6Rv/ks5aWtkWk7M4N7b9rx4sW0hKBUS2bGBS61hTQ
Xxxpx58j0mSY2yDupiRatPXR+gKq5Rkg3Gqfy+IzkrnGj72MDujg741MMepUZVF4
hxXA13GCLvbOEoabmi6xDUIQ9iBE7BCT9CZtsJXgz94M/6a3g0tEkpkePxHpnyQC
JktIQms4xF3DydRsSO4cFPXx6oup7Av4XYwhuX6ajTiyZ6s1mYhzLpJJNuxk7J0/
bnp06fYVVtZvdMKj8ci8RHVYvheZykUC+KbOgH/jREVe+DTG4rbkAK1k2qAz4Mbv
SLkEjS7HlmpIFlpnBKOie/y6YL1MNEmxdhgUmK3SdGIf1iJ8Qx5OV0NlXC9YsjsC
rnj+QQptn5YoXQHQ5IyQ/56EUvuntbpCaM2/q2r9QOCZ6QhS/UMZLjak1tbxYIT5
i0vc5e0exQom8aGpE2YqXNq3wu3VYZFsBGGSUEXCSKjvhS8Ll27HReeSf4cCQ0cV
8BxRf4kj2jrxHptebB80+wK+P9iKus23s8ViBXXj8SJiiqNzlGV3AWtJ+2WDGOw4
dYmDEfdqy7/JVppGWsXGh4bDu1o01fQEJ/lcbQL+N3uhrHt4QNROXtASrC/WrWQf
J49WkFKgl9UP5AcpA1mXAdg4c6URQSt0WkgqJjbMcmv7GbShRmM= =9kAZ
User-Agent: slrn/1.0.3 (Linux)
View all headers
* cjsmall, 2021-01-12 19:41 UTC:
No, there is no Content-Type: line in the header.
The first such line is in the body as shown above.  The message seems to have gone through a Microsoft mail server and the following line is in the header, but it's not applicable:

x-ms-exchange-antispam-messagedata:
[...]
=?utf-8?Q?8hyfyw1KAK+py9GCQQq4dNiMX86FzJRQF1?Content-Type: multipart/related;
        boundary="_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_";
        type="multipart/alternative"

Any idea where the message is getting mangled?

As it is directly following an x-ms-exchange-... header without CRLF you
could ask Microsoft.

Also, if it is already bad in the original data and not just due to
copy-pasting, that x-ms-... header content contains no CRLF pairs (or
any LF at all), likely just CR because hey it's Mac (you could determine
by inspecting the original data), so that might be another related
problem or even the underlying cause for no CRLF in front of the
Content-Type header.

I also still don't understand why the image blocks can be munpacked but why the first two blocks are skipped.  Since mutt doesn't show any attachments, does it just not look for them because the Content-Type: header line is missing?

Yes. No Content-Type multipart header = no multiparts.

Apparently munpack tries to guess boundaries from the text/plain content
on the fly.

  Eike

--
OpenPGP/GnuPG encrypted mail preferred in all private communication.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
Use LibreOffice! https://www.libreoffice.org/


Subject: Re: Problem emails
From: Peter Pearson
Newsgroups: comp.mail.mutt
Date: Wed, 13 Jan 2021 21:27 UTC
References: 1
Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: pkpear...@nowhere.invalid (Peter Pearson)
Newsgroups: comp.mail.mutt
Subject: Re: Problem emails
Date: 13 Jan 2021 21:27:49 GMT
Lines: 38
Message-ID: <i696ulFm68U2@mid.individual.net>
References: <83e48b8c-5caf-44b8-b9f7-d4fc0ef09b8dn@googlegroups.com>
X-Trace: individual.net 1SrYy7tMcDhDAAHSqpVgaQ7FUyxfozDdDErjslRpwgStMRNdyK
Cancel-Lock: sha1:5e+QZv33/yNjtHBU8c3NzaeD5fw=
User-Agent: slrn/1.0.3 (Linux)
View all headers
On Mon, 11 Jan 2021 17:29:07 -0800 (PST), cjsmall wrote:
[snip]
When I try to view the message in mutt, I just see the raw encoded
body.  When I press v and look at the attachments, mutt doesn't see
any.
[snip]

Message:

[[Normal Email Header]]

--_014_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_
Content-Type: multipart/alternative;
        boundary="_000_38F8AFA1CFE745588061C7E41F3F7246fantiniusacom_"

Apologies if I'm just re-hashing stuff you already know.  I'm no
authority on email formats, but I have looked at several, and it
seems to me that a properly formatted multipart message has
a line like this in the header:

Content-Type: multipart/alternative; boundary="some_boundary_string"

Thereafter, each "part" of the message begins with a block like this:

--some_boundary_string
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
        charset=utf-8

The last "part" ends with the boundary string followed by "--":

--some_boundary_string--

Can you find all these pieces in the offending message?


--
To email me, substitute nowhere->runbox, invalid->com.


1
rocksolid light 0.7.2
clearneti2ptor