On 08/20/2015 09:44 AM, Marco Calistri wrote:
Is there anybody that could have the explication to this strange behavior?
I *sigh* see a not unrelated phenomena. When I do I use "ctl-u" to see "under the hood" at the raw message. many mailers are not very good and send non-conformant messages Others are nov ery good and don't do things like "text-flowed" properly, causing parts of the message to vanish. The RFCs say that a in a multi-part message there should be an 'alternative' pure text component. Some don't honour that. Heck, you can automate batch mail (aka large scale unsolicited or perhaps group mailing list blasts) with Linux tools and omit any part you want! Or not. look what you can do with 'metasend', for example. I have a couple of not-technical correspondents who use what I consider to be broken mailers that send html-mail, and piss poor html mail at that, with no text part. For the most part I view mail text only, so yes i quite often see mail that has no text art, that is all a graphic image, that is all html mail. I have to use View->Body_Message_As->HTML-Original, once I've verified using ctrl-u. but its not always that simple. Sometimes the ctrl-u shows Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 which is unreadble by mere humans. Perhaps you have a base64 decoder to hand to check this out of band. The 'strange behaviour' is non-conformance or playing loose-and-free with poorly written parts of the specification. RFC 3676 obsoleted 2646 and clarified the issue of plain text vs enhanced, but not everyone, least of all Gmail, follows this. <quote> Interoperability problems have been observed with erroneous labelling of paragraph text as Text/Plain, and with various forms of "embarrassing line wrap". (See Section 3.) Attempts to deploy new media types, such as Text/Enriched [Rich] and Text/HTML [HTML] have suffered from a lack of backwards compatibility and an often hostile user reaction at the receiving end. </quote> Thunderbird is a very capable MUI, but it has a host of configuration options and there is a lot of stuff on the Net Of A Billion Lies that refers to out of date versions. The key thing, I would recommend, is to use "ctrl-u" to find out what is there and whether it makes sense for the display mode you are using. But that too is predicated on issues like access control, indexing and more. When I run 'find' on my /home/anton tree I usually get error messages about unreadable files, which puzzles me. They are unreadable by root as well, so i wonder if I have corrupt directories. Damn BtrFS for introducing uncertainty. And perhaps the Windows/linux disparity is a configuration option - check the "about:" -- which is extensive. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org