From owner-freebsd-questions@FreeBSD.ORG Tue Aug 10 21:58:01 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B015D16A4CE for ; Tue, 10 Aug 2004 21:58:01 +0000 (GMT) Received: from pursued-with.net (adsl-66-125-9-244.dsl.sndg02.pacbell.net [66.125.9.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60F7943D2F for ; Tue, 10 Aug 2004 21:58:01 +0000 (GMT) (envelope-from freebsd@pursued-with.net) Received: from babelfish.pursued-with.net (babelfish.pursued-with.net [10.0.0.42]) by pursued-with.net (Postfix) with ESMTP id A080D21E3EE; Tue, 10 Aug 2004 14:58:02 -0700 (PDT) Date: Tue, 10 Aug 2004 14:58:02 -0700 (PDT) From: Kevin Stevens To: JJB In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "freebsd-questions@FreeBSD. ORG" Subject: Re: Top posting solution X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd@pursued-with.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 21:58:01 -0000 On Tue, 10 Aug 2004, JJB wrote: > The fact of life is all the Unix mail clients adhere to the Unix > email format of posting the reply to the bottom of the email while > indenting with a quote character. Not true. Pine doesn't, for example. It begins a reply with the cursor at the very top of the message body. > Top posting came along when MS/Windows came on the market with their > own email clients: Outlook express which is the email client built > into Internet explorer and the MS/Office Outlook email client. Not true. See above. > There is a little known fix for MS/Outlook express and MS/Office > Outlook email clients that change the behavior of these MS/Windows > email clients so they adhere to the Unix email format of posting the > reply to the bottom of the email while indenting with a quote > character. "Fix" is a loaded term which presumes that something is broken. > To all you Unix hard liners, Please instead of complaining to the > top posters, it would be so much nicer if you just informed the It would actually be much nicer if they'd just quit trying to enforce their preferences on others. > MS/Windows top poster of the above links so they know about the > solution to fix their email clients to adhere to the Unix email > format used on this list. Please provide a cite/ref to the "Unix email format" as something more concrete than your personal definition. And more concrete than RFC 1855, whose second sentence reads: "This memo does not specify an Internet standard of any kind." KeS