Tone's Notes

This article was most helpful for configuring the Exchange Intelligent Message Filter. It also describes how to enable the Custom Weighting Feature. The key steps are:

• regsvr32 C:\Program Files\Exchsrvr\bin\MSCFV2\MSExchange.UceContentFilter.dll

·        Use Notepad to create/edit (in Unicode format) the file: C:\Program Files\Exchsrvr\bin\MSCFV2\MSExchange.UceContentFilter.xml

Caution: The MSDN & TechNet documentation hasn’t been updated to indicate what version it refers to. Specifically, the interface for enabling IMF features for a SMTP virtual server was changed between version 1 and version 2. This page, for example, describes the IMF V1 interface.

The filter drops blocked e-mail into the C:\Program Files\Exchsrvr\Mailroot\vsi 1\UceArchive folder. Double clicking on a file with a .EML extension opens it with Outlook Express. Delete the real spam and drop the real mail into the pickup folder.

If you do end up mistakenly installing IMF V1 on top of Exchange SP2, it will appear to succeed with no complaints but will probably not work. You can remove it on the Add/Remove Programs control panel. Then reinstall Exchange SP2. Configuration changes appear to be preserved through all this.

A few hours wasted learning this detail, maybe it will help someone out there…

When configuring WDS to work between two LinkSys WRT54G routers with Sveasoft’s Talisman/Basic 1.1 firmware, don’t assume that any row in the WDS table will do, always use the first row.

I have two wired “base-station” WRT54G’s and one that wants to roam around wirelessly. I initially configured the WDS table on the roaming router to have two rows populated to make it easy to switch between enabling (LAN mode) one or the other, depending on the current location of the roaming router. The link worked consistently and flawlessly with the router listed in the first row, but never with the router listed in the second.

Finally I eliminated enough other possibilities to suspect the table row, moved the first row data to the third row and disabled it for record keeping, and copied the second row to the first row and enabled it there (second row disabled). Surprise, surprise, now it works…

There’s apparently more magic going on in the WDS table than I can make out from the documentation or copious amounts of configuration discussion threads out there…

For reference, here are the link I used for basic setup info:

How-To: WDS as a Transparent Wireless Bridge  

Great link for diagnosing problem with Windows Remote Desktop connections.

telnet smtp.myserver.com 25

helo

mail from: whoever_can_be_quoted

rcpt to: recipient_e-mail

data

Message…..

.

quit