I’ve grown quite fond of my EAS MD utility, and it’s also been great fun sharing the code powering it for the past weeks/months. When I originally started out coding it I was fueled by what I felt were shortcomings in the official diagnostic utility provided by Microsoft; http://testexchangeconnectivity.com. It only supported Exchange 2003 protocol level, had no means of dealing with security policies, and in general didn’t provide a whole lot of options. It worked OK, but not for the scenarios I wanted to test.
When you’re a programmer at heart this means there might come a moment when you get a feeling of “why not build what I want myself instead of accepting the tools available as is”. Not to mention that other people aren’t going to accept your “whining” either and will eventually challenge you to do better. (I wasn’t pressured by anyone else than myself when it came to this issue though.)
(…)
Today I have come full circle, returning to where we started, and present a web version of EAS MD to you

