On Wed, 7 Jun 2017 22:33:33 +0800 Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote: > On 06/07/17 22:07, stan wrote: > > I use claws mail and had no problem seeing this message. I think > > Bob didn't see it because claws doesn't allow html messages unless > > asked to. There is an option to render them as text, which I have > > set, and is probably why I saw it. Also, it is possible to click > > the bottom icon on the right of the message, and if you have the > > html plugin for claws installed, it will display the html message. > > Well, except that the "empty" messages from Samuel Sieb are tagged > as... > > Content-Type: text/plain; charset="utf-8"; format="flowed" > Content-Transfer-Encoding: base64 But the message that shows up as the empty dots in Samuel's message is from Walter and has the following encoding. Content-Type: multipart/mixed; boundary="===============7498209977189103805==" > So, I don't think the issue is related to html I agree with you. I was looking for a way to explain how the same mail client could have very different user display outcomes. i.e. it worked for me, but not for Bob. I think I'll drop this now. :-) _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
