www.delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Date: | Wed, 19 Jul 2006 19:37:50 -0700 (PDT) |
From: | Mark Geisert <mark AT maxrnd DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Suggestion for Cygwin mailing list handling |
Message-ID: | <Pine.BSF.4.63.0607191921540.62064@m0.truegem.net> |
MIME-Version: | 1.0 |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
O powers that be, Would it be possible to have the mailing list software reject emails containing appended (i.e., not attached) cygcheck output? And/or bounce such emails back to their senders? Another theoretical option would be to automatically convert appended cygcheck output to an attachment. It would seem that a test for the existence of the two strings "Cygwin Configuration Diagnostics" and "Use -h to see help about each section", when each starts a line of the email, would identify such emails. Just some ideas humbly offered in lieu of actual PTC. ..mark -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |