That random “J” at the end of the messages brings me back to mail circa 2010. As I recall, iOS also didn’t render Outlook’s smileys right, leaving a bunch of Js in mail from my Mom. (For the ones who ‘missed’ it: https://devblogs.microsoft.com/oldnewthing/20060523-10/?p=31... )
Rim/Blackberry tales – reply all
11–20 of 83 posts
Re: Rim/Blackberry tales – reply all
#12Earlier quoted context omitted.
I used to think the same but I caved when I started using web interface email clients. Let’s face it, the world has moved on, new generations are online, and we are the wrong ones now.
I don't understand why this isn't configurable. Why can't the basic data structures (of one email after another in serial) be displayed in either order depending on mail client settings? Admittedly I haven't looked into it because I'm perfectly fine with top posted emails. But I routinely sort files in my directory. Why not emails in a displayed thread?
The ability to semantically parse text to determine what order paragraphs should be displayed in to suit the tastes of the individual reader is a very recent development. Or, rather, will be soon. Maybe not very soon.
Re: Rim/Blackberry tales – reply all
#13Re: Rim/Blackberry tales – reply all
#14Re: Rim/Blackberry tales – reply all
#15And every story seems to end with admins having to improvise. Am curious: (why) isn’t there a “kill reply-all chain” button as a feature?
(The article explains that this didn’t work for RIM because of BB’s architecture, but for Exchange?)
Re: Rim/Blackberry tales – reply all
#16This happens often enough (even MS itself broke their internal Exchange servers). And every story seems to end with admins having to improvise. Am curious: (why) isn’t there a “kill reply-all chain” button as a feature? (The article explains that this didn’t work for RIM because of BB’s architecture, but for Exchange?)
Re: Rim/Blackberry tales – reply all
#17Re: Rim/Blackberry tales – reply all
#18Re: Rim/Blackberry tales – reply all
#19Re: Rim/Blackberry tales – reply all
#20Earlier quoted context omitted.
I used to think the same but I caved when I started using web interface email clients. Let’s face it, the world has moved on, new generations are online, and we are the wrong ones now.
I don't understand why this isn't configurable. Why can't the basic data structures (of one email after another in serial) be displayed in either order depending on mail client settings? Admittedly I haven't looked into it because I'm perfectly fine with top posted emails. But I routinely sort files in my directory. Why not emails in a displayed thread?
- parsing the unstructured email body and looking for quote levels, html formatting and printed email heads
- parsing certain headers like message-id, in-reply-to, dkim sig
- looking for sections of the message body in the inbox
This is done because there is nothing in the protocol to cleanly accomplish what you want. Even if there was, you could not rely on it at all. Doing anything with email is a gigantic PITA, you sometimes get emails where the msg-encoding header doesnt match the body's encoding, html in the plaintext section and other fun things.
Since nobody really cares about the RFC and just does their own thing, there is no chance at improvement.