From owner-freebsd-isp Tue Nov 25 06:01:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13749 for isp-outgoing; Tue, 25 Nov 1997 06:01:53 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA13743 for ; Tue, 25 Nov 1997 06:01:45 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.8.7/8.8.3) id JAA05706; Tue, 25 Nov 1997 09:01:15 -0500 (EST) Message-ID: <19971125090114.25104@emu.sourcee.com> Date: Tue, 25 Nov 1997 09:01:14 -0500 From: "Norman C. Rice" To: Greg Lehey Cc: isp@FreeBSD.ORG Subject: Re: Web Page Restrictions References: <01bcf97d$4a946a40$49588a0a@wujie.bj.ciet.cn.net> <19971125191436.37494@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Description: email message X-Mailer: Mutt 0.88 In-Reply-To: <19971125191436.37494@lemis.com>; from Greg Lehey on Tue, Nov 25, 1997 at 07:14:36PM +1030 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg, I appreciate your voluntary contributions and understand your requirements. I believe the format problems stem from "word processor mentality." Every keyboard has a mechanism for inserting a delimiter at the end of the line; and AFAIK, it is not disabled in any mailer. IMHO, if you're willing to volunteer your time and knowledge, it is reasonable that respondents use the appropriate format. Rick, I also appreciate your efforts, but (IMHO) the flames and profanity are not constructive. -- Regards, Norman C. Rice, Jr. On Tue, Nov 25, 1997 at 07:14:36PM +1030, Greg Lehey wrote: > On Tue, Nov 25, 1997 at 04:36:57PM +0800, Wu Jie wrote: > > Hi, Greg, > > > > Unfortunately, you are wrong again. You know why you saw some odd characters > > last time in my email? You shouldn't have made any conclusion before careful > > investigation. Pulling your hair and biting your nail you can't guess why. > > It's not because the **broken configuration** of my **broken mailer**, it's > > only because the default character set of my OutLook Express is not English. > > Although I prefer FreeBSD and don't like Micro$oft, but OutLook Express is > > ok, why not use it? Don't be so biased and cranky. > > Sorry, Wujie, but that's not correct. We see the same problems in > purely US versions of Microsoft Outlook. > > > Oh, you list so many mailers: "Microsoft Mail", Microsoft Outlook, Mozilla > > (Netscape), exmh. Why don't you call Netscape to stop developing its > > mailer? > > Do you think they'd listen to me? They know it's broken, and they're > leaving it that way because they're in competition with Microsoft. > > > It's the world of web now, people get used to hypertext non-line-break > > style, what makes you deep immersed in the old command-line-break world? > > I thought I was on the Internet, not on a private Microsoft network. > I will certainly work to keep it that way. On the Internet, the RFCs > define what is correct, and these mailers contravene the > specifications by reformatting both on sending and on reception. > > > Greg, I am not, I think Rick Morel is also not, willing to raise an > > argument. > > You could have fooled me. > > > We just want to say, it's the Internet, the "Blue Ribbon" "free > > speech" cyberspace, people have their rights to use whatever style in their > > email. > > OK. Let's accept that. > > > Please don't send the impolite "i tell you, you should add line > > breaks" sentences anymore even if you'd not like to offer help to > > the people asking questions. > > Well, the fact is that I *do* answer a lot of questions. But I'm not > doing it any more for people who can't send out a legible mail > message. And many of them understand the problem, but don't know that > their mailer is broken. In fact, the guy I sent today's message to > thanked me for telling him. > > As for impoliteness, I think you should re-read the message, then > re-read yours and Rick's. > > Greg >