Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <20020910150122.97271.qmail@web21002.mail.yahoo.com> Date: Tue, 10 Sep 2002 08:01:22 -0700 (PDT) From: Nicholas Wourms Subject: RE: re. problem report: gawk 3.1.1 To: "Zieg, Mark" , "'cygwin AT cygwin DOT com'" In-Reply-To: <7424935D9B6CD311B72800508B108FD20D176775@emss03m08.orl.lmco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- "Zieg, Mark" wrote: > > From: Nicholas Wourms [mailto:nwourms AT yahoo DOT com] > > > > > Also, sending mail to mailing lists in HTML format is generally > > > > considered impolite. > > > > I completely agree! It is totally unacceptable to send messages > with > > animated crap in it to the list. > > Fortunately, receiver-side solutions exist for those who prefer not > to > receive such things (man procmail). I think it's generally > preferable to > let people choose what they wish to read, rather than restrict what > others > are allowed to write. > > #=========================== > # convert HTML-only messages > #=========================== > :0 fbw > * ^Content-Type: text/html > | /usr/local/bin/lynx --force-html --dump /dev/stdin > > :0 fhw > * ^Content-Type: text/html > | formail -i "Content-type: text/plain" > Well that's great if you can *use* procmail, but as you can see I use yahoo mail. So unless I fork out $29/yr, I have to read my mail through their web interface. I think the point needs to be reiterated that sending HTML/M$MimeOLE encoded mail to a public list is just downright RUDE. Not only that, but as the previous poster stated, it screws up Mozilla. Cheers, Nicholas __________________________________________________ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/