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 Date: Mon, 3 Mar 2003 13:55:24 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Advocacy Message-ID: <20030303185524.GC23972@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <7D6AD971A503D311BBB100805FA75F9F06E6DA15 AT ns0107 DOT uk DOT nomura DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Mon, Mar 03, 2003 at 09:42:16AM -0800, Peter A. Castro wrote: >> At my place of work, access to free e-mail websites is blocked, so the only >> e-mail I can send is via my official account. This adds the disclaimer you >> see at the bottom. I can't prevent that. You can ignore it very easily, and >> delete this message if the disclaimer offends you. No, I don't mention you >> by name but yes, you are an intended recipient of the message. > >I feel that you should review their responses to you, determine if they >are truely striking out at you because of your companies policies, and >respond back. Yes, email them back! Make them put their money where >their mouths are and justify their complaints. Anyone who really >participates on this list will tell you that they back up every word with >something stronger than just fist waving. If they can't or won't, then >just ignore them. As someone who publicly commented on this ludicrous disclaimer, let me just note that I fully understand that people who post to the list have no control over the disclaimers. However, if you take them at face value you could easily come to the conclusion that the sender could be in violation of company policy or, worse, could be assuming that you are implicitly accepting their policies. I am sorry for suggesting that people should contact this company to talk about the disclaimer. I thought that maybe if enough people contacted the proper authorities they might be able to help institute a change. I wasn't suggesting that anyone contact the original sender to complain since it is clear that they have no power over this. I've previously floated the idea of filtering out these disclaimers on the overseers at sources dot redhat.com mailing list and no one thought it was a very good idea. So my threat to do so was just an idle one. cgf -- 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/