ORF and 64-bit Support

Every once in a while, somebody asks me if ORF will work under Exchange 12. My regular response is something (admittedly) obscure like “There are technical challenges that have to be solved first. Current versions of ORF surely will not run work with Exchange 12.”. It is obscure because I am not sure what is the best way to work around those “technical challenges”. Let me explain why.

Exchange 12 will run on 64-bit Windows only. 64-bit is good. 64 is twice as much as 32 and Microsoft knows this :) Alas, even though ORF agrees, it does not run on 64-bit Windows.

As you might know, ORF integrates with the IIS SMTP Server to perform filtering. This integration is done using a Microsoft-provided thing called Protocol Event Sinks, which allows third-party developers to hook specific events of the mail delivery and run their own code. (By the way, Exchange does the same).

Now the trick here is that IIS on 64-bit Windows is a native 64-bit application. This is great, because it can take advantage of the 64-bit power. On the other hand, it is pretty bad, because native 64-bit applications cannot load native 32-bit DLLs. Guess what—ORF is still 32-bit. And it will remain so for a long time.

Why can’t we just recompile ORF to 64-bit? That is an easy one. ORF was written in Borland Delphi, which, as of writing this, lacks of 64-bit compilation support. As much as I can predict the future, 64-bit support is not going to be added soon. Or ever. Borland is trying to sell their IDE business and I have this feeling that there are not very many companies knocking on the door. If you feel that translates to Delphi is dying, well, uhm, I keep my fingers crossed.

So what can we do? We need to interface with the IIS SMTP somehow. Now the only part of ORF which directly talks with the IIS SMTP is the SMTP Module and actually it is enough if we can get that part work. And we have multiple options!

  • A) My initial thought was to turn the SMTP Module from an in-process COM server into an out-of-process server (~from DLL to an EXE). This would have a little performance penalty, but could work anyway. In theory. Alas, Microsoft’s documentation states that it will not work and this my experience confirmed this. Even though, I talked with a fellow professional who said he could get an out-of-process event sink work and I have no reason to doubt that.
  • B) Rewrite the SMTP Module in C++, which supports 64-bit compilation. This would be a clean solution, but nobody here speaks C++ well. The result would be ridiculous at best. Not because any decent C++ developer would laugh his ass off while looking at our code, but because it would take enormous amount of time and would be hard to maintain.
    We could hire a contractor to do the job, but we believe that our core competencies like code and design must not be outsourced. We can also hire someone full-time who speaks C++, but it is hard to justify the cost.
  • C) Rewrite the SMTP Module in C#, which supports 64-bit compilation. We speak C# and Microsoft recently made protocol event sinks available in the managed world. However, mixing languages just does not sound good and the fellow professional I mentioned above described his experience with managed event sinks using less than enthusiastic words (yes, that’s a gross understatement). I got the same impression when I tried getting a C# event sink work.

So we have a multitude of bad options, but Exchange 12 (now Exchange 2007) is coming soon, so we have to come up with something. Stay tuned :)

Reporting Tool Sneak Preview

The focus is now on the Reporting Tool of ORF 3.0. We already got the tool backbone, most supporting code and now reports are being designed. See below how it looks so far.

The GUI misses lots of functionality, from report generation (the above report has real data from a real client, but it was generated outside of the Reporting Tool) to navigation or printing, but we are closer to the 3.0 release than ever :)

This is the one of the most fun parts of software development. Small cog-wheels like PowerLogs, log preprocessing and reporting code get integrated and the engine slowly starts working. It is noisy, emissions are high, fuel leaks, but it finally works! :)

Guy Kawasaki’s Art of Customer Service

The Art of Customer Service is a recently published piece of Guy Kawasaki’s excellent “Art of…” series. In his article, he emphasizes the importance of having a great customer service and points out that…

[…]customer service has as much to do with a company’s reputation as sales, marketing, engineering, and finance.[…]

I cannot agree more. Maybe I would even call it an understatement.

Customer service can make or break a company, if the company is not in some kind of monopoly position. My previous ISP, the manufacturer of my previous MP3 player and a couple of other companies lost me for their ignorant and bureaucratic customer
service. I would not hesitate a second to switch my cable TV or telephone provider if there were alternatives, thanks to their poor customer service. On the other hand, I cannot stop recommending products of companies which gave me great customer service experience (well, provided the product works). Surprisingly, a few companies still have not realized that it is always the service sold, even though the product itself is an MP3 player or a software tool.

We’re growing…

Planting…spices, at last :) Here at the Vamsoft HQ we have a nice backyard, an ideal place for a sunny mini spice garden. During the long winter (starving for fresh summer basil and tomatoes), I decided to finally utilize the backyard and plant a few of my favorite spices and herbs. The ORF Tech Support guy, Krisztian also liked the idea, so last Thursday we took the seeds, the flower pots, some soil and made our little garden with thyme, origano, basil and rocket/rucola.

Krisztian working hard :)

I was a bit concerned about planting too early, but this morning I was suprised to see that only in five days the rocket started growing! That means pesto di rucola with fresh gnocchi within 2 weeks! :) No wonder why English calls rucola “rocket”.

Meanwhile, we have relased the 4th development release of ORF, with minor adjustments to the PowerLog format. The PowerLog report preprocessor is nearly complete, it is going to be integrated with the ORF Service in the next few days. The technology research with the embedded Internet Explorer control was successful, so now it is pretty sure that we will use embedded HTML for displaying and printing reports. Also, the decision has been made about the report resolution: it is going be 1 day, which means that the shortest period of time that reporting will handle is one day.

Roadmap Update

Well, this had to come. When we compiled the feature set for ORF 3.0, my estimation for Reporting was 35-49 days—making it the biggest single feature we ever added to ORF. This estimation assumed that reports will be generated from the current logs, but later several problems were identified with this concept. We faced with a decision: either we will generate reports that A) are useful, or just generate B) some eye-candy summary. We decided to go with the option A), which required a new logging medium and lots of related work, doubling the resources needed. This is reflected in development: we are about to reach the 49 days limit and Reporting is about halfway to be completed.

It became obvious that Reporting will predate other planned features of ORF 3.0. We have updated the ORF Development Roadmap according to this.

We apologize for this feature creep, I know many of you expected these features much. We will do our best to get them into ORF as soon as possible.