Well, dear mr. new - please consider that you dont even know what you are talking about.


  has been using exchange 2003 for lyk forever


That would be "like" not "lyk", AND... Exchange 2003 is NOT A MAIL SERVER. What you try to do is like replacing a car with a spare engine. Exchange (2003 is outdated and seriously must be upgrades like yesterday) is a LOT more than a mere email system.

Unless your company does not use any of the othe features (like shared calendard, integration with phones in a push fasion) and has no interest in using some of the new featuers an upgrade would bring (voice control of calendar, integration with a SIP phone system as integrated mailbox with text to speech and speech to text) you basically are on the way to make a moronic bad decision. The type that may turn your system administration career with immediate termination for gross neglect and demosntrated incompetence.

So, sit down and think of what your company uses Exchange for. Then sit down and try tofind a product that can replace it in it's entierety. Then sit down and consider an ugparde (2010 is a LOT better than 2003). Then sit down and consider the assoiated costs for moving to linus in your company (which may include thigns like integrating backups, changing procesdures, adding more staff that has in depth linux knowledge etc.). Then make an educated decision. Right now you look like - sorry tobe blund - an ignorant linux zealot who does not even bother to check the software he wants to replace for the functionaltiy it offers.

MOST companies would really get angry with some junior wannabe system admin replacing their integrated staff coordination platform with a mere email system.

Linux Mail servers over Windows Mail servers
Using JSON.stringify and JSON.parse to serialize and deserialize objects has subtle problems such as date objects being serialized as strings and then coming out on the other side as strings rather than date objects. I've tried using postMessage instead which has the benefit of producing 1:1 results, but I'm worried about other handlers eaves dropping on the messages. I've considered writing my own serializer/deserializer, but would prefer native browser capabilities.

Is there a way to use postMessage like a serializer, without having to worry about eavesdropping?

NOTE: I don't care about eavesdropping using dev tools. My app is loading plugin like modules and I want to make sure those aren't able to eavesdrop on messages that are for other modules.
