I finally got around to moving the OWA 2003 proxy at work to Apache 2 (from Apache 1.3). It was ridiculous how much easier it was to get working in Apache 2. I should have done this months ago.

Expect a HOWTO coming soon.

Also... I'm currently trying to get Exchange 2003 RPC over HTTP to work through Apache 2. It's ugly. I'm either missing something very obvious or this is going to be quite difficult. A friend suggested we set up an ISA server (as it has an RPC over HTTP proxy built in). I know... I should've strangled him (yeah... you Shawn! ;-) ).

Getting RPC over HTTP working through Apache may require a special plug-in. That could be fun (OR NOT!).


UPDATE: Oooohhhh! I found a nasty bug in my Apache 2 version of the OWA front-end proxy. Apparently, the Apache proxy doesn't like it when percent signs (%) are used in the URI. You see... Microsoft thought it would be a good idea to call up each email by using the subject line as the key (as opposed to... oh... THE TRULY UNIQUE IDENTIFIER every Exchange message has). Because of this, we get all sorts of interesting characters in the URIs (like spaces and percent signs and other things one should never use). I made a small kludge that seems to work well. I'll include that in the forthcoming HOWTO.

UPDATE (Thu Jun 23 11:10:46 JST 2005): I've put this off for too long. I'll see if I can get this done today.

UPDATE (Thu Jun 23 22:16:11 JST 2005): The HOWTO is posted. You can find it at

• http://3cx.org/item/46

I love Gmail. I can't imagine my email any other way. I was invited to join quite a while ago, so many of the features it has today were not available and access at times could be hit and miss. Today, it is one of the most stable web apps you can find on the internet (IMHO of course).

As much as I love Gmail, it has always bothered me that I must compose and read my emails using a variable-width font. I guess I'm just an old crusty Unix guy, but emails should be text-only and that text should be displayed in a fixed-width font. I get a lot of system stat and summary emails from the various Unix systems I administer. They're text-only and rely on tabs and spacing to be easily read. The default varibale-width font creates no end of havoc on the format of these emails. Until now, I had always viewed the email source (More options -> Show original) to get the proper formatting. Now I don't have to.

In firefox, you can override any stylesheet with a custom setting in the firefox config. The file where these overrides are specified can be found under your firefox profile. Spcifically at <your profile>/chrome/userContent.css. Create or edit this file with the following content.

div.msg div.mb {     font-family: monospace !important;     font-size: 12px !important; } textarea.tb {     font-family: monospace !important;     font-size: 12px !important; } td.ct {     font-family: monospace !important;     font-size: 12px !important; }

This will override the specific stylesheet classes that Gmail uses. It will not affect html email, but will allow text-only email to be displayed with a fixed-width font. You'll also be able to compose your emails with a fixed-width font.

I ran across the first override (div.msg div.mb) on the net somewhere. If I can find that site again, I'll quote the source. The second override I found by using the "View Selection Source" function in firefox (quite handy BTW).

As far as I can tell, these overrides interfere with nothing else in Gmail. I use these settings both on my Linux machines and my one Windows laptop.

Enjoy.

UPDATE (Mon 18 Apr 22:54:13 JST 2005): I found the site where I discovered the first CSS override.

• http://milov.nl/2608

UPDATE (Wed May 18 15:54:17 JST 2005): I just printed something with Gmail (obviously I don't print that much). The fixed-font overrides do not work with the "printable" stylesheet. When I get a few minutes, I'll see if I can figure this one out.

UPDATE (Wed May 18 16:32:54 JST 2005): I figured it out. I've updated the shaded list of CSS overrides to include one for the "printable" page (td.ct). I've not extensively tested this, but it doesn't appear to affect anything else.