X-Recipient:	archive-cygwin AT delorie DOT com
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=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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; s=default;
	bh=MagRj7nVNqXVcgC8HHphGHaDml0=; b=ipHxfp3e/fOu9X154fRQvnoB0N6R
	TsRxZOyMw1nWlyYyQYxr4aD2ZeZVGdLn3FBZEG3caDtP1+0AxPoT6dOciFCLLWsz
	BhshctYThY30GFS85apiZUyYJWo4ajHse2zp4i2m6w8z3O+7afLYWm9Cvt9GGOnK
	PvG2b9mIOyRskrA=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.1 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.3.2
X-HELO:	mho-02-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX19g8u+WoE4JG4vLYs2UV8eW
Date:	Sun, 10 Nov 2013 14:23:45 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: upset messages
Message-ID:	<20131110192345.GA2074@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20131109103606 DOT 25923 DOT qmail AT sourceware DOT org> <20131109104542 DOT GJ16306 AT calimero DOT vinschen DOT de> <527E36AB DOT 9040206 AT gmail DOT com> <20131109165134 DOT GL16306 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
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

- Raw text -