X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=3.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT X-Spam-Check-By: sourceware.org Date: Tue, 11 Oct 2011 16:06:47 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <1394134519.20111011160647@mtu-net.ru> To: Kaz Kylheku , cygwin@cygwin.com Subject: Re: stdio.h: broken standard compliance. In-Reply-To: <82593b31494b784ab45fc7915f0e3435@127.0.0.1> References: <82593b31494b784ab45fc7915f0e3435@127.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Greetings, Kaz Kylheku! > I see now from the archives that this list is configured > to generate the unfortunate Reply-to header, which by many > is considered a mailing list misconfiguration. First time I hear this bullshit. Mailing lists intended for public conversation. > RFC 2822: > ``When the "Reply-To:" field is present, it indicates the mailbox(es) > to which the author of the message suggests that replies be sent.'' > [ 3.6.2 Originator fields ] > Note that the Cygwin mailing list is not the author of this message; > herefore, it is abusing the Reply-To: header in violation of the > RFC which governs e-mail communication. It is author of message. If not, your message would have never reached the list. -- WBR, Andrey Repin (anrdaemon@freemail.ru) 11.10.2011, <16:03> Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple