Hello Thomas, I am not a developer and as a distributor and support for czech users, I know user's point of view in such cases. But when is message broken (regardless page author or authoring SW) and opening it in browser produces same result, this is understandable behaviour.
Maybe Ritlabs could display warning when opening such faulty messages and allow user to select, what to do - even user understand nor MIME nor HTML META TAG. I do not agree with with your statements in rest of message, security can be toy or serious tool and TB is second one. Yes, it conforms RFC and allows workarounds for implementation issues if possible, yes, it does not allow to bypass self's security for attachs like man-in-the-middle, yes, it does not allow to use outdated insecure protocols even users requires it optional, because they know nothing about security and will disable any secure feature immediately when will be limited by it. -- Bye Marek Mikus Czech support of The Bat! http://www.thebat.cz Using the best The Bat! 5.0.0.145 BETA under Windows 7 6.1 Build 7600 with MyMacros,XMP,AnotherMacros, AntispamSniper v 3.2.6.4 Notebook Thinkpad, Core2 Duo 2.40 GHz, 4 GB RAM ________________________________________________________ Current beta is 5.0.0.145 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
