On 02.04.22 14:00, Zi Yan wrote: > On 2 Apr 2022, at 3:52, Kalle Valo wrote: > >> Kalle Valo <kvalo@xxxxxxxxxx> writes: >> >>> David Hildenbrand <david@xxxxxxxxxx> writes: >>> >>>> On 01.04.22 16:22, David Hildenbrand wrote: >>>>> On 01.04.22 16:19, Zi Yan wrote: >>>>>> On 1 Apr 2022, at 10:12, David Hildenbrand wrote: >>>>>> >>>>>>> On 01.04.22 15:58, Zi Yan wrote: >>>>>>> >>>>>>> It's weird, your mails arrive on my end as empty body with attachment. I >>>>>>> first suspected Thunderbird, but I get the same result on the google >>>>>>> mail web client. >>>>>>> >>>>>>> Not sure why that happens. >>>>>> >>>>>> No idea. They look fine (except mangled links by outlook) on my outlook >>>>>> desk client and web client on my side. lore looks OK too: >>>>>> https://lore.kernel.org/linux-mm/20220401135820.1453829-1-zi.yan@xxxxxxxx/ >>>>> >>>>> I can spot in the raw mail I receive >>>>> >>>>> "Content-Type: application/octet-stream; x-default=true" >>>>> >>>>> But that seems to differ to the lore mail: >>>>> >>>>> https://lore.kernel.org/linux-mm/20220401135820.1453829-1-zi.yan@xxxxxxxx/raw >>>>> >>>>> >>>>> Maybe something in my mail server chain decides to do some nasty >>>>> conversion (grml, wouldn't be the first time) >>>>> >>>> >>>> Weird thing is that this only happens with your mails. I opened an >>>> internal ticket, sorry for the noise. >>> >>> Zi's patch emails I received didn't have Content-Type, that might have >>> something to do with this. (But his reply later in the thread did have >>> one.) Also last week I got one patch email with no Content-Type either >>> and my Gnus decided to convert it to octet-stream, I guess to be on the >>> safe side. No idea if something similar is happening to you, but wanted >>> to mention it anyway. > > The emails I got from linux-mm mailing list do not have Content-Type either, > but the ones I got directly from my git-send-email have it. David is in the > cc list, so the emails sent to him should have Content-Type. I assume I received them without a Content-type, or mail servers stripped them, and Mimecast servers (which RH uses) fail to auto-detect and add a wrong Content-type. Wouldn't be the first time that Mimecast messed with mail encodings etc, unfortunately. -- Thanks, David / dhildenb
