Date: Fri, 8 Oct 2010 11:41:11 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: trouble posting to cygwin-apps
Message-ID: <20101008154111.GB23848@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1286518842 DOT 1832 DOT 42 DOT camel AT OG3>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1286518842.1832.42.camel@OG3>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Fri, Oct 08, 2010 at 08:20:42AM +0200, SZAB? Gergely wrote:
>The mailing list does not accept html email, that's fair enough.
>
>The real problem is, it also bounces every email with a company
>disclaimer about intentions and original addressees.

>Well, the original addressee is cygwin at cygwin dot com, which is a public
>mailing list, readable even from Alpha Centauri (with 4 years delay).
>
>This policy is OK for most FOSS projects, but Cygwin should be an
>exception. I think Cygwin is used most by 3PPs within big companies
>where everybody _must_ use Windows and those disclaimers are always attached to
>outgoing mail. If you are a free and sane person, attracted to unixy stuff,
>you'd probably use Linux.
>
>Yes, I've read the posting instructions, and I know I should convince my
>employer to remove the disclaimers. What chance do you think I have to
>convince a 20000-employee company, where central IT is not even in my
>country? They also restrict access to private email from the office. 
>
>I know, I should leave them and/or buy a smartphone for emailing. :-)
>
>But my point is: the mailing list is cut off from its most important
>audience.

As I think you understand, the cygwin-apps list, like every other list
at sourceware.org/gcc.gnu.org does not allow company disclaimers.  That
is not going to change.  We block the disclaimers because they are
intended to be legally binding directives and as such we do not want to
be encumbered.  This is a site-wide policy.  It is not malleable due to
the need of the people who want to send email.

Since the cygwin mailing list is always in the top two for site traffic
I think it's safe to say that we aren't suffering too much from this
restriction but, even if it was, I don't really ascribe to the notion
that we're suffering from lack of contributors to the project because we
block disclaimers.  As Eric Blake points out, there are plenty of ways
to get a message posted here without going through the corporate
firewall.  But, even if none of those are acceptable, it isn't really up
to the administrators at this site to accommodate your needs.

cgf

--
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