What do you have for View/Message Body As? Press Alt if the Menu Bar is hidden. Do all the newsletters look OK in webmail? Do the 'control codes' look like they are provided by word processing , e.g. mso entries?

Good questions. Since I get the newsletter once a month and I read my email using Thunderbird, there won't be a newsletter to check in the Gmail host inbox for another 30 days. However, your question gave me a thought and I forwarded the May newsletter which doesn't display to myself and closed Thunderbird. When I attempted to view it in the Gmail inbox the body was blank. Not a perfect test but possibly an indicator. I attempted to attach text files with the newsletter content and unless I convert it to an image, they won't upload. It doesn't even look like a PDF is supported. Since your reply came from a "no-reply" address I tried it the hard way, printing to a PDF and saving the pages to image files. Do you want me to attach 71 pages/images (20.6 MB) here for you to look at? Or are there alternate solutions such as copying and pasting the text of the newsletter message view into a response here? I don't know if there are any size limitations but the saved text files of the newsletter code is in the area of 140K. I'll do anything you like to make this as easy as possible to diagnose. Please let me know what to do next. Thank you again for your time and effort... Peter Bradish P.S. I don't know what "mso entries" are. However, I'm pasting some of the lines from the "Subject:" line down into the beginning of the March email body (this is from one which won't display) which might help.

Subject: Old Guns and Other Stuff Newsletter for March 2020 Date: Fri, 13 Mar 2020 17:27:24 -0000 X-CTCH-Spam: Unknown X-CTCH-VOD: Unknown X-CTCH-RefID: str=0001.0A09020F.5E6BC280.003D,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CSC: 0 X-CHA: v=2.3 cv=PZqBeRpd c=1 sm=1 tr=0 b=1 cx=a_idp_d a=tenBiR0PCuRG+iBb9p3nWw==:117 a=tenBiR0PCuRG+iBb9p3nWw==:17 a=IkcTkHD0fZMA:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=SS2py6AdgQ4A:10 a=TH8GJYOdbVEA:10 a=4zemTso8mxEA:10 a=ZZnuYtJkoWoA:10 a=Z-zZw_0cAAAA:8 a=3-idFmPuAAAA:8 a=pDJIllfoAAAA:8 a=NAbJNu0VAAAA:8 a=iIJp1dYiAAAA:8 a=oNFtUEMmAAAA:8 a=RTiUxO3KAAAA:8 a=u0IcT4VVAAAA:8 a=mHFh7uMkAAAA:8 a=PfvezVdxAAAA:8 a=CzDSEw-1LE4NhEidVWAA:9 a=Qr1z3_A_5kkKkMU0:21 a=HrZOfe4RLcnjy9pc:21 a=QEXdDO2ut3YA:10 a=XNNXxzpft88A:10 a=gdwm71Z0w28A:10 a=LuM-9UpyfSYA:10 a=RJFNVWq7macA:10 a=afJrZ1l2WUwA:10 a=-FEs8UIgK8oA:10 a=NWVoK91CQyQA:10 a=SSmOFEACAAAA:8 a=pPkVz1VfjGJiBTT3tMMA:9 a=pdWXQ0cZ6zjb6oSK:21 a=IKbtQdL4KBV_wVyj:21 a=XhnL2k68eJp6xBYC:21 a=_W_S_7VecoQA:10 a=VkTJwBIh2koRuL6HRgbG:22 a=wtY4T6hn7PjB0oMxQoYK:22 a=FQSvnIhFvpVQrs41iAv4:22 a=zFkEywS1De8D2zmgQL6o:22 a=Gf35tdBnXvls8YOwx7Dw:22 a=Bti97eou4alz2QUUHtQv:22 a=HQEt9TzzOQq8o8QOxM_l:22 a=OazSXjJWHpGfNJTEFf8J:22 cc=prm X-Origin-Country: US X-WHL: LR X-SA-Poll-Id: 1584120565509..771b01000cf29b55..1..1584120444000 X-SA-USERIDNR: 310416 X-SA-MPREASON: sender enabled (newsletter+cornellpubs.com@mnb.email)

--===============2214747735309397185== Content-Type: multipart/alternative; boundary="===============1643499299657113912==" MIME-Version: 1.0

--===============1643499299657113912== MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"

March 2020 Newsletter

http://report.mnb.email/t.js?s=3D5e6bc26b6426c7570362ebc4&u=3D42737350&v=

3D3&key=3D608b&skey=3Db96565a058&url=3Dhttps%3A%2F%2Fwww.usatoday.com%2Fst

ory%2Fnews%2Fnation%2F2020%2F01%2F01%2Ftumbleweeds-bury-cars-drivers-washin= gton-state%2F2792122001%2F

EF=BB=BFGee, Mrs. McGillicuddy, I was just driving Rosie home when Tumbleg

eddon happened" Several motorists spent New Year's Eve trapped in their cars on a Washingto= n state highway by giant piles of tumbleweed 30 feet high. After high winds=

blew in the weeds, five cars and a truck were buried for hours before snow=

plows were able to clear the road.

The newsletter archive is here, and the March version is here. It looks OK in my browser, May issue also, so no idea why it doesn't render in TB. Did you try different options for View/Message Body As?

Yes, that's how I look at the newsletters when they don't display. They all display fine in my browser (Firefox) too. I'd never noticed the "Message Body As" choice in the "View" menu before. I just tried all three choices: Original HTML, Simple HTML and Plain Text. None of them displayed the email body for the April or May emails, but did display the March email issue.

BTW, I checked the forwarded copy of the newsletter article that didn't display in the Gmail inbox and the body wasn't there (viewing the Message Source) so that wasn't a valid test. It makes me suspect that if I forwarded one of my non-displaying emails to you the body would also be absent so I looked at my "Sent" folder and the forwarded email had only basic HTML without content for the body. eg: <meta http-equiv="content-type" content="text/html; charset=windows-1252">

It looks like the best I can do for providing information would be to send the text file with the Message Source to you but I'd need an email address to do that unless you want the 71 page images sent here instead.

Is there anything else you would like me to do?

Thanks for everything. Hope we can figure this one out. :-) Take care... Peter

Sorry, the HTML I included above didn't all show but there only an "html" followed by "head" and "/head" around the "meta" instruction, followed by a "body", "p", "br" "/p", "/body" and ending with "/html".

If mail or newsletters from every sender didn't display in TB, I would suspect there's a problem with your setup. If it's only with one or two senders, and only occasionally, it's more likely an issue with the html formatting made by the newsletter composer, and that is not something you're likely to change, especially since they see 'no problems'.

Someone else may have more insight, but I think in the end you will just have to read the web versions.

You gave it your best shot. Thank you very much for your efforts on my behalf.

You might suggest to the IT folks who support your "Support Mozilla" site here that they allow something more than just images to be provided for attachment (a PDF would have worked) as it would have been potentially more useful for you (or someone) to look at the actual code in the newsletter email to see if something might have jumped out as the problem.

In any case, thank you for your time and attention, it's greatly appreciated... Peter