HP3000-L Archives

May 1996, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Geiser, Joseph" <[log in to unmask]>
Reply To:
Geiser, Joseph
Date:
Fri, 17 May 1996 08:15:45 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
----------
From:   Tom Emerson[SMTP:[log in to unmask]]
Sent:   Thursday, May 16, 1996 1:54 PM
To:     Multiple recipients of list HP3000-L
Subject:        Exchange, gateways, the internet, and so
 
 
<snip>
 
Depending on how and where the address gets imported, there MAY be a
check-box labeled "always send to this recipient in Microsoft Exchange
rich text format" and defaults to true.  (I found some addresses where
this option didn't show up at all, kind of hard to set or un-set
something if the option isn't given :) )  For this message, I've
un-checked the option in the address book, therefore this should not
attempt to send the message in "rich text" (which is what I presume the
base-64 encoded block of data was that followed the original portion of
my message)
 
        Assumption is correct on RTF - it is base-64 encoded, and virtually
        unreadible by anything other than another mailer (or exported to an app
        such as MS Word) which supports RTF.  When using Exchange with
        Internet Mail - always ensure that this option is unchecked...
 
        (Found that the hard way)
 
The unfortunate thing about the internet and e-mail is that the more
advanced it gets, the less legible everything becomes.  While this
provides an appearent opportunity to bash Unix, the truth of the matter
is that the original MAIL program is perfectly suited to what it does,
but nobody seems to want to use a "plain" e-mail package.  While I might
be happy using Robelle's Xpress program (only slightly fancier than MAIL,
and in fact the interfacing between Xpress and the Internet is trivial),
I like the organizational abilities of Exchange much more than Xpress,
despite the hoops I have to jump through to get an Exchange message to
look good to everyone else.  Given enough time, energy, and resources to
"check out" every e-mail package, I'm sure I'll find one that exceeds
Exchange's abilities by as much as Exchange exceeds Xpress
[tongue-twister intended not].
 
        One thing about Exchange is that MS seemed to want to set a
        standard here - but it could not - evidenced by the fact that for a short
        while, they had a "mail and news" beta client on their web site for
        free download.  It's since been removed, I believe.  Too bad - it was
        pretty good - it's only flaw was that it was imcompatible with Exchange's
        mail and address book files.
 
Joe Geiser

ATOM RSS1 RSS2