Date: Tue, 26 Jan 1999 14:55:08 +1030 From: Greg Lehey <grog@lemis.com> To: "Larry S. Marso" <larry@marso.com> Cc: freebsd-questions@FreeBSD.ORG Subject: HTML mail (was: Polite Advocacy on -questions WAS: learning UNIX) Message-ID: <19990126145508.H66239@freebie.lemis.com> In-Reply-To: <19990125225933.C6464@marso.com>; from Larry S. Marso on Mon, Jan 25, 1999 at 10:59:33PM -0500 References: <Pine.BSF.3.91.990125131442.9317A-100000@dsinw.com> <Pine.BSF.4.05.9901252143530.276-100000@s8-37-26.student.washington.edu> <19990125225933.C6464@marso.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 25 January 1999 at 22:59:33 -0500, Larry S. Marso wrote:
> On Mon, Jan 25, 1999 at 09:56:27PM +0000, Jason C. Wells wrote:
>>> First thing you need to learn about UNIX, HTML is NOT a valid way
>>> to send E-mail. Other then that, jump right in.
>
> Thinking about this, I wonder ...
>
> Why not write a procmail script that pipes html e-mail to:
>
> netscape -remote 'openURL('$1',new-window)'
Well, off the top of my head,
1. This requires procmail. Not everybody wants to install procmail.
2. It means that you're interrupted by the message when it arrives
rather than when you want to look at it.
3. It could be an incredible resource hog. What happens if 40 such
messages arrive in the course of a night? You could run out of
swap before the morning.
4. How do you reply?
There's no good reason to send HTML mail. Most people do it out of
ignorance, because their software is set up to do it. I *can* read
HTML mail with mutt, but in every time I've done so, it was almost
illegible.
Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990126145508.H66239>