Need a book? Engineering books recommendations...

Return to index: [Subject] [Thread] [Date] [Author]

RE: Email Standards

[Subject Prev][Subject Next][Thread Prev][Thread Next]
In the responses I received from subscibers who are "lurking" I have
received some very useful information. Those who receive their email on some
Unix servers can not decode the HTML or Mime formatted text.
I see that there is great desention regarding Formatted text and suggest we
restrict the Listservice to Plain Text Ascii format and leave the formated
text to specialty lists or private email.


Dennis S. Wish PE

-----Original Message-----
From: Bill Allen, S.E. [mailto:ballense(--nospam--at)pacbell.net]
Sent: Tuesday, March 10, 1998 6:33 AM
To: seaoc(--nospam--at)seaoc.org
Subject: Re: Email Standards


I had no idea you were THAT interested in what I had to say, Roger :o) ! At
your request, I have changed my e-mail settings so that I send both formats.
Although this will bloat the transmissions slightly, it is the only way I
know of to get the best of both worlds. While I apreciate the intellectual
efforts of the minimalists (those trying to get the most from the least), it
shouldn't be a "ball and chain".
Regards,
Bill Allen
Roger Turk wrote:
Glad that you said it Stan!
I, too, have not been able to read a number of Bill Allen's posts.
Normally,
his posts have the ASCII as the Part I, and the HTML attached as the Part II
of the message.  I have an "HTML Stripper" that will strip the embedded HTML
comments from a message, however, the problem that I have is that all binary
files are downloaded into a separate directory with the name, MAIL###.BIN,
so
finding the files is the first chore, then stripping the HTML out to be able
to read it cleanly is another chore, and, finally, having posts from this
list in two different directories, let alone two different files is another
problem.
Bill, turn off that "HTML Only" switch, <please>!
Now, speaking as an old navy man, the fastest speed of a convoy is the
maximum speed of the slowest ship.  This should also apply to interchange of
information.
A. Roger Turk, P.E.(Structural)
Tucson, Arizona