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:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=ctFuM5eIjSuPzVo1IBkRfe87T1dwT
	dt1yt7WmF7rnTPDCnlc6Q/KiQfEq/x6UH4bf74P16ERHWX3+nWrhG9IzVgamtRPF
	GSR9v+rsAXAMGcX981OxB9Y6x9isYx+nWz9ZUINgtBsxn9s4igDaEz20+vv5S/lx
	dtRCOGkkjvsNjo=
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:mime-version:date:message-id:subject:from:to
	:content-type; s=default; bh=pRodPAoEvwWatt2rikXQkBw5spA=; b=tWs
	HdgW6E9G9VofHfzfVBhEu5VJyRr65z5ucfwo5F0JTyFHjKPt3wgI7srmBmetgTmO
	HUrTkzo+wTzE8Nhs63IiycZezT/+a223Qh2qSVcIAP22t02MK1u570t0X+5qV0nO
	iuwiQrr9OZ1aAOqa6BV5hvw0fRV5gHUXUFFahvqs=
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.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-yh0-f44.google.com
MIME-Version:	1.0
X-Received:	by 10.170.174.194 with SMTP id q185mr1613837ykd.75.1434474638674; Tue, 16 Jun 2015 10:10:38 -0700 (PDT)
Date:	Tue, 16 Jun 2015 11:10:38 -0600
Message-ID:	<CAG4rVi4NywSBQpETDrQR30ZF-qaYO8gA0+45+QUd2w9FkH7uFA@mail.gmail.com>
Subject:	Spamassassin blocking mails
From:	David Frascone <dave AT frascone DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

This is likely affecting more than just me.

-Dave


---------- Forwarded message ----------
From: Tiger Technologies <support AT tigertech DOT net>
Date: Tue, Jun 16, 2015 at 10:57 AM
Subject: Re: ezmlm warning [TT#: 1685493]
To: David Frascone <dave AT frascone DOT com>
Cc: cygwin-help AT cygwin DOT com


David Frascone <dave AT frascone DOT com> wrote:

>It looks like your mail server is being flagged by spam assassin -- that is
>probably affecting all of your users who use blacklists, not just me.
>
>I'm cc-ing my ISP to see if they have any suggestions.

Thank you for writing!

We've looked at why that message was rejected, and it's not because of a
problem with the cygwin.com server. Rather, it's because of the server
that sent the message to cygwin.com, "mail3.ks.pochta.ru".

The original message had these headers (among others):

 Received: from mail3.ks.pochta.ru (HELO mail3.ks.pochta.ru)
(185.79.118.173) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a)
with (AES256-SHA encrypted) ESMTPS; Thu, 04 Jun 2015 09:52:10 +0000
 From: Mikhail Usenko <mikeus AT nm DOT ru>
 To: cygwin AT cygwin DOT com
 X-RSpam-Report: This message is probably spam.

The mail3.ks.pochta.ru server at 185.79.118.173 is on many blacklists:

 http://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a185.79.118.173&run=toolpage

So it's likely that many (most?) ISPs treated this individual message as
spam. (Even the cygwin.com server seems to have flagged it as "This
message is probably spam".) The sender, mikeus AT nm DOT ru, is almost
certainly aware that many people aren't getting his messages.

However, this shouldn't affect other cygwin.com list messages. If we're
understanding correctly, the warning that dave AT frascone DOT com received
from the cygwin.com server was just about that individual message. Our
logs show that all other messages from cygwin.com to dave AT frascone DOT com
over the last 30 days have been delivered normally.

This re-conjures the age-old debate about whether list servers should
accept and forward mail that they think is probably spam (and whether
they should notify subscribers about bounces of those messages if they
do). There's no right answer to that, unfortunately.

Our customers can avoid this particular problem by adding the list
server's "Return-Path" domain name to their e-mail whitelist settings
(<https://support.tigertech.net/bypass-filter>), which we've done for
messages from cygwin.com to frascone.com -- they won't be scanned by
SpamAssassin anymore.

We hope that helps. Please let us know if not, or if there is anything
else we can do. Thank you again!

--
Robert Mathews, Tiger Technologies

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