ANST - Re: Abreviations: was protocol

[Decker, Terry D.]

> Welcome to Microsoft Outlook.
> 
> It will make your life hell and you'll never know what else to do.
> 
> It's worse when in its native environment and connected to a Microsoft
> Exchange server.
> 
> The problem is typically that the person has either used special
> formatting in the message (ie. colors, bold, flashing, etc) or they are
> connected to a MS Exchange server. (We have never been successful in
> totally getting rid of the damn MS-TNEF when connected to the Exchange
> Server. Believe me; we tried for a good month solid.) MS-TNEF is an
> exchange format to keep formatting information when sending between
> Outlook/Exchange. Unfortunately no one else reads it.
> 
> 
> Btw, 'wolf is sending his out as RTF from Pegasus Mail.
> 
> Ciao,
> 
> -- 
> Phelim "Pug" Gervase  |  "The problem's plain to see
> 
If you are using Exchange Server, I recommend getting to 5.0.  Use the
Exchange Server Client 4.0 rather than Outlook as the transport mechanism
(Outlook can front-end it).  Use the native message editor rather than Word
for editting messages.  Vanilla is good.

So far, our Exchange system works reasonably well.  The big problem comes
when someone loads Office 97 without taking into account the
Outlook/Exchange interface.  BTW, when I loaded up Office 97 on this box,
Outlook did not come along.  I didn't want to waste my time customizing it
when what I have works fine.

Bear  
============================================================================
Go to http://www.ansteorra.org/lists.html to perform mailing list tasks.