Hello Marek, On Tue, 1 Mar 2011 14:17:06 +0100 GMT (01/Mar/11, 20:17 PM +0700 GMT), Marek Mikus wrote:
MM> I see it correctly in Outlook, because it probably uses MIME definition MM> instead META tag, which is disputable. From my 13 years experience, many MM> website or mailserver admins and app developers are lazy enough, they are MM> coding such things not according to RFC, but according to popular clients MM> or web-based services, where are developers, who ignores many RFC or MM> security risks... Raymund and Vilus already replied to you, and as opposed to me, they seem to know something about this. I am a mere user, and I read you like this: 1. You have 13 years experience and know that people don't always follow the RFCs. 2. You don't care about the users and that they need to see the message, which they can with another pragmatic software, but you throw the book at the TB! customers and tell us that we shouldn't able to see the message because some god said it should have been formatted differently. (I received such a message from a trusted source two or three days ago, and I fail to see how they would have sent me malware.) MM> Example 1 : message has different META tag than chars encoding, but Outlook MM> displays this correctly, than there is no need to fix this. Not in Outlook, but in TB! there is indeed a need to fix it. You did not get the point: I cannot read the message just because I am using TB!, and that is bad. MM> Example 2 : server forces to use SSL, but has outdated and buggy version MM> 3.0, which has security flaws, but why should they update it, if most MM> popular clients accepts this? This is a different issue, nothing to do with the one at hand. And yes, I want the option to accept an unsecure or expired certificate. MM> Example 3 : server forces to use SSL, but certificate hostname does not MM> match with mailserver hostname - again, this is security flaw, but popular MM> clients accepts this, so who cares? I don't really get your point but yes, I do want to read my mail. I care about that. I think you get my point: I am talking about usability and being pragmatic. If you have security concerns, make it optional. But you are not going to change the world by forbidding TB! users to read misformatted mails. You will only drive the users to use another email client instead. -- Cheers, Thomas. http://thomas.fernandez.hat-gar-keine-homepage.de/ Message reply created with The Bat! 4.2.36.4 under Windows XP 5.1 Build 2600 Service Pack 3 ________________________________________________________ Current beta is 5.0.0.145 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
