On Thu, 2015-08-20 at 10:24 -0400, Anton Aylward wrote:
Is there anybody that could have the explication to this strange behavior? many mailers are not very good and send non-conformant messages Others are nov ery good and don't do things like "text-flowed"
On 08/20/2015 09:44 AM, Marco Calistri wrote: 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.
Nobody cares anymore what the RFCs say [and Google is an offender - but anything they do is 'right' according the their legion of fanboys, so... sigh].
Some don't honour that.
"Some"? The truth is "Many", and trending towards "Most".
The 'strange behaviour' is non-conformance or playing loose-and-free with poorly written parts of the specification.
Any modern MUA should know how to work-around the many most common ways messages can be 'broken'.
RFC 3676 obsoleted 2646 and clarified the issue of plain text vs
I wouldn't hold my breath on compliance.
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.
+1 Going to the message source to see the structure of a message is always a place to start when looking at wonky-message issues.
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.
Yes, I would be very concerned about that. Backup NOW! -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org