From metatracker at psf.upfronthosting.co.za  Thu Sep  3 16:55:55 2015
From: metatracker at psf.upfronthosting.co.za (Tim Tisdall)
Date: Thu, 03 Sep 2015 14:55:55 +0000
Subject: [Tracker-discuss] [issue554] Add special mark to Rietvelds emails
In-Reply-To: <1413143480.64.0.313151672251.issue554@psf.upfronthosting.co.za>
Message-ID: <1441292155.64.0.376360757263.issue554@psf.upfronthosting.co.za>


Tim Tisdall added the comment:

Here's some headers from a recent email sent to me:

Received-SPF: neutral (google.com: 2a01:4f8:131:2480::3 is neither permitted nor denied by best guess record for domain of roundup-admin at psf.upfronthosting.co.za) client-ip=2a01:4f8:131:2480::3;
Authentication-Results: mx.google.com;
       spf=neutral (google.com: 2a01:4f8:131:2480::3 is neither permitted nor denied by best guess record for domain of roundup-admin at psf.upfronthosting.co.za) smtp.mailfrom=roundup-admin at psf.upfronthosting.co.za;
       dmarc=fail (p=NONE dis=NONE) header.from=python.org

As you can see, "dmarc=fail". (though, I can't seem to see a DMARC policy on any of the pertinent dns records)

Another email from the tracker that was in my spam box said:

"Why is this message in Spam? It's in violation of Google's recommended email sender guidelines."  And linked to https://support.google.com/mail/answer/81126?hl=en-GB#authentication

A DMARC policy should really be added and DKIM signing should also be added.  Lately, major email providers have been clamping down to try to prevent spam by nearly requiring those things.

----------
nosy: +Tim.Tisdall

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue554>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Sep  3 18:44:17 2015
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 03 Sep 2015 16:44:17 +0000
Subject: [Tracker-discuss] [issue554] Add special mark to Rietvelds emails
In-Reply-To: <1413143480.64.0.313151672251.issue554@psf.upfronthosting.co.za>
Message-ID: <1441298657.42.0.461035236795.issue554@psf.upfronthosting.co.za>


R David Murray added the comment:

That has nothing to do with this issue.  Nor do we do anything currently with dmarc.  There are other issues about roundup mail getting marked as spam, you could repost your observations on one of those if you like.

----------
nosy: +r.david.murray

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue554>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Sep  3 19:00:03 2015
From: metatracker at psf.upfronthosting.co.za (Tim Tisdall)
Date: Thu, 03 Sep 2015 17:00:03 +0000
Subject: [Tracker-discuss] [issue562] Gmail (google) marks registration
	email as spam
In-Reply-To: <1422157456.62.0.726959967661.issue562@psf.upfronthosting.co.za>
Message-ID: <1441299603.2.0.934629711908.issue562@psf.upfronthosting.co.za>


Tim Tisdall added the comment:

Here's some headers from a recent email sent to me:

Received-SPF: neutral (google.com: 2a01:4f8:131:2480::3 is neither permitted nor denied by best guess record for domain of roundup-admin at psf.upfronthosting.co.za) client-ip=2a01:4f8:131:2480::3;
Authentication-Results: mx.google.com;
       spf=neutral (google.com: 2a01:4f8:131:2480::3 is neither permitted nor denied by best guess record for domain of roundup-admin at psf.upfronthosting.co.za) smtp.mailfrom=roundup-admin at psf.upfronthosting.co.za;
       dmarc=fail (p=NONE dis=NONE) header.from=python.org

As you can see, "dmarc=fail". (though, I can't seem to see a DMARC policy on any of the pertinent dns records)

Another email from the tracker that was in my spam box said:

"Why is this message in Spam? It's in violation of Google's recommended email sender guidelines."  And linked to https://support.google.com/mail/answer/81126?hl=en-GB#authentication

A DMARC policy should really be added and DKIM signing should also be added.  Lately, major email providers have been clamping down to try to prevent spam by nearly requiring those things.

----------
nosy: +Tim.Tisdall

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue562>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Sep  3 19:01:01 2015
From: metatracker at psf.upfronthosting.co.za (Tim Tisdall)
Date: Thu, 03 Sep 2015 17:01:01 +0000
Subject: [Tracker-discuss] [issue554] Add special mark to Rietvelds emails
In-Reply-To: <1413143480.64.0.313151672251.issue554@psf.upfronthosting.co.za>
Message-ID: <1441299661.03.0.0613285065789.issue554@psf.upfronthosting.co.za>


Tim Tisdall added the comment:

oops.. sorry.  I did a search for "dmarc" and this was the only thing I found.  I moved my comment to #562.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue554>
_______________________________________________________

From roundup-admin at psf.upfronthosting.co.za  Thu Sep 10 04:47:13 2015
From: roundup-admin at psf.upfronthosting.co.za (Python tracker)
Date: Thu, 10 Sep 2015 02:47:13 +0000
Subject: [Tracker-discuss] Failed issue tracker submission
Message-ID: <20150910024713.EB6EF5691E@psf.upfronthosting.co.za>


An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.
-------------- next part --------------
Return-Path: <bounce+27be32.9b1c6-report=bugs.python.org at psf.io>
X-Original-To: report at bugs.python.org
Delivered-To: roundup+tracker at psf.upfronthosting.co.za
Received: from rs232.mailgun.us (rs232.mailgun.us [209.61.151.232])
	by psf.upfronthosting.co.za (Postfix) with ESMTP id CE4C856918
	for <report at bugs.python.org>; Thu, 10 Sep 2015 04:47:11 +0200 (CEST)
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=psf.io; q=dns/txt; s=pic;
 t=1441853230; h=Subject: To: From: Content-Transfer-Encoding:
 Content-Type: MIME-Version: Message-Id: Date: Sender;
 bh=f6h3PMDAIWus2jVt2rJSAXjlwVPcMyxClZ3e85ToNyA=; b=DjWBSYlaSFnfeIsCAWhSedmpfjmi2JboqIJiGImJ2SsDKyzMsfztPqe461DuqJEywFRA+hS5
 rKaJqfRbW0EVCVM02bqPf5ayy/I99kN42HxNKYOLNri8qwYndYuw+t57XCi03IS5JcZDKUnT
 K1edH12FMkTjcVof/yWKTm9UMrM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=psf.io; s=pic; q=dns;
 h=Sender: Date: Message-Id: MIME-Version: Content-Type:
 Content-Transfer-Encoding: From: To: Subject;
 b=SpqrVrYa9K29PBgh6BZuBIG1TxlMche8LFHy90N1WvJtI8jjO0Z//E1oQLpVIhUkIIDCVZ
 LaSCElAQNJk+VI/7bOsw1sSPayGNzbrXokHFE6YEjuucrbFn9Y0CqNROZJ3ri+NQ5fEsdeP1
 jphhKbjWfTZlaWJZg0l9J/rlcJSEQ=
Sender: tracker-discuss=python.org at psf.io
Date: Thu, 10 Sep 2015 02:47:10 +0000
X-Mailgun-Sid: WyIzZGMxOSIsICJyZXBvcnRAYnVncy5weXRob24ub3JnIiwgIjliMWM2Il0=
Message-Id: <20150910024710.27689.24443 at psf.io>
Received: from hg.iad1.psf.io (hg.psf.io [23.253.158.192])
 by mxa.mailgun.org with ESMTP id 55f0ef2e.7f9ac03c66f8-in2;
 Thu, 10 Sep 2015 02:47:10 -0000 (UTC)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
From: tracker-discuss at python.org
To: report at bugs.python.org
Subject: [issue22464]

TmV3IGNoYW5nZXNldCA2YzhlMmM2ZTNhOTkgYnkgWXVyeSBTZWxpdmFub3YgaW4gYnJhbmNoICcz
LjUnOgp3aGF0c25ldy8zLjU6IE1lbnRpb24gaXNzdWUgMjI0NjQKaHR0cHM6Ly9oZy5weXRob24u
b3JnL2NweXRob24vcmV2LzZjOGUyYzZlM2E5OQo=