DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=vCKpBM1efJa+RI8yhpCHgywhit91ov6taUVq3ZHElnVgrTSOmvfxR
	4KdrEC5Y11z7Z3g/O5IwnQjBTIaqiPTEq0HOfrzR9YC5ykpYpDwY+aWJBABmATcM
	sRPo5OPtG8qX2ZBEX7YjnAx4ahfMlqdWxQjsOZoK/Oxa/XzBndTLAs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sun, 10 Nov 2013 14:23:45 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: upset messages
Message-ID: <20131110192345.GA2074@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20131109103606.25923.qmail@sourceware.org> <20131109104542.GJ16306@calimero.vinschen.de> <527E36AB.9040206@gmail.com> <20131109165134.GL16306@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131109165134.GL16306@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Sat, Nov 09, 2013 at 05:51:34PM +0100, Corinna Vinschen wrote:
>My reply a couple of hours ago was just catched by this #$%@ raw email
>address filter.  I'd really appreciate if we could go along without this
>aggressive email blocking.  It's getting more annoying than helpful,
>lately.

The raw email filter was working effectively in this case.  You would
have sent a raw cygwin mailing list address if you hadn't been blocked.

So, without the filter, you would have exposed the cygwin mailing list
address and potentially had people tell you PCYMTNQREAIYR (something
which you, yourself, do fairly often).  Sparing the list that traffic
and not adding one more place for spammers is pretty helpful.

But even with that aside, the fact is that you have no way of knowing
how helpful the block is because you only see a bounce when it affects
your sending of email.  I, on the other hand, see the people trying to
send email with corinna-cygwin or lh-cygwin in the body.  It doesn't get
through and, so, often, people decide to send email to the cygwin list
instead, as we require.  I also see the messages which include
cygwin-owner and cygwin in their body, of course.

I know that some of the above could actually be considered a false
positive since neither corinna-cygwin nor lh-cygwin are not what the
block was theoretically supposed to catch but since they fall under
PCYMTNQREAIYR, I have never tried to tighten the filter up.

Finally, "upset messages" discussions are off-topic for this list
anyway.  I understand why they ended up here since I have done the same
thing myself.  I think I've fixed that problem.  I've made modifications
to upset to set the Reply-To to the list of maintainers so replying to
the upset mail (which comes from the cygwin account on sourceware)
should no longer cause email to be sent here.

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