Adding text using imsext.dll

[Howard Steinberg]

Has anyone had experience troubleshooting the oubound append feature? We run Exchange 5.5 sp3.

1. I copied and registered the imsext.dll file successfully.
2. Added the value NonRoutingExtensionDll under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesM SExchangeIMCParameters, and set the file for the path to the imsext.dl
3. Added the key Extension under Parameters, then added the value Outbound Append with one line of text.
4. Stopped and Started the IMS

When I sent myself a test message, I don't get the text? DOes anyone know the best way to troubleshoot?

[Bob Mitchell]

Been there, got the tee shirt and the cap and the headache. !
imsext.dll is a very "clunky" way to do this but the fact is that you MUST enter pure RTF directly into the Registry entry. Why you just cannot point to a file location I don't know and Microsoft aren't saying. You CAN paste RTF into the registry entry, but, and I mean but, ONLY ONE LINE at a time. Yes, I know but I don't know why. Write your disclaimer in WordPad, save it in RTF then open it in Notepad and you can see all the formatting. Now copy/paste a line at a time into the registry.
Best of luck and don't try it after a liquid lunch !!
Cheers.

------------
Howard Steinberg at 12/15/00 10:25:00 AM

Has anyone had experience troubleshooting the oubound append feature? We run Exchange 5.5 sp3.

1. I copied and registered the imsext.dll file successfully.
2. Added the value NonRoutingExtensionDll under HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesM SExchangeIMCParameters, and set the file for the path to the imsext.dl
3. Added the key Extension under Parameters, then added the value Outbound Append with one line of text.
4. Stopped and Started the IMS

When I sent myself a test message, I don't get the text? DOes anyone know the best way to troubleshoot?