search

python / psf-infra-meta

Meta-repository for PSF backed or managed systems. Created mainly for the issue tracker :)
11 stars 7 forks source link

b.p.o emails classified as spam #16

Open pitrou opened 5 years ago

pitrou commented 5 years ago

Recently many bpo notification emails started being classified as spam in my inbox. I'm not sure what could be the cause, but it seems like it could be correlated to the recent migration (some SPF setting perhaps?).

Here are the headers of one such email, as received:

Return-Path: bounce+d85e67.33af56-pitrou=free.fr@roundup.psfhosted.org
Received: from zimbra10-e2.priv.proxad.net (LHLO
 zimbra10-e2.priv.proxad.net) (172.20.243.160) by
 zimbra10-e2.priv.proxad.net with LMTP; Thu, 27 Dec 2018 06:32:31 +0100
 (CET)
Received: from mail-s84.mailgun.info (mx26-g26.priv.proxad.net [172.20.243.96])
    by zimbra10-e2.priv.proxad.net (Postfix) with ESMTP id 2EE768230F0
    for <pitrou@free.fr>; Thu, 27 Dec 2018 06:32:31 +0100 (CET)
Received: from mail-s84.mailgun.info ([184.173.153.212])
    by mx1-g20.free.fr (MXproxy) for pitrou@free.fr;
    Thu, 27 Dec 2018 06:32:31 +0100 (CET)
X-ProXaD-SC: state=SPAM score=190
X-ProXaD-Cause: (null)
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=roundup.psfhosted.org;
 q=dns/txt; s=mx; t=1545888750; h=Date: From: To: Subject:
 Content-Transfer-Encoding: In-Reply-To: Message-Id: Reply-To:
 Content-Type: MIME-Version: Sender;
 bh=Y5wGYXto0x2bJ06nhNpPJwQkALA8z7SB4wsB8s+PQnE=; b=qfX/03A35J3MRqph6phYN+9di+bhFei/eDzSQ70i/fvUX5eZWimFrLY+/IuAsQSNT0vDbifB
 6JqcPTTirJ9e82WrBKvMi+ziLPI7dNkWs7JxBVBdxu+ncMy87NkjOyG2QQUC78/Y5zkzbk8h
 aUBAAVLYkXnVTBZEEIi5+VcBTOQ=
X-Mailgun-Sending-Ip: 184.173.153.212
X-Mailgun-Sid: WyI0MDEyMCIsICJwaXRyb3VAZnJlZS5mciIsICIzM2FmNTYiXQ==
Sender: report=bugs.python.org@roundup.psfhosted.org
Received: from bugs.ams1.psf.io (bugs.ams1.psf.io [188.166.48.69])
 by mxa.mailgun.org with ESMTP id 5c2463ed.7fdf7b91dea0-smtp-out-n03;
 Thu, 27 Dec 2018 05:32:29 -0000 (UTC)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Reply-To: Python tracker <report@bugs.python.org>
Message-Id: <1545888743.19.0.101962596573.issue35559@roundup.psfhosted.org>
In-Reply-To: <1545463748.16.0.98272194251.issue35559@roundup.psfhosted.org>
X-Roundup-issue-status: closed
X-Roundup-issue-type: performance
X-Roundup-issue-keywords: patch
X-Roundup-issue-stage: resolved
X-Roundup-issue-severity: normal
X-Roundup-issue-versions: Python 3.8
X-Roundup-issue-resolution: rejected
X-Roundup-issue-priority: normal
X-Roundup-issue-components: Library (Lib)
Content-Transfer-Encoding: quoted-printable
Subject: [issue35559] Optimize base64.b16decode to use compiled regex
To: pitrou@free.fr
From: Karthikeyan Singaravelan <report@bugs.python.org>
Date: Thu, 27 Dec 2018 05:32:27 +0000
Precedence: bulk
X-Roundup-Name: Python tracker
X-Roundup-Loop: hello
X-Roundup-Version: 1.5.1
pitrou commented 5 years ago

This still happens on a regular basis here. The headers typically contain the following line:

X-ProXaD-SC: state=SPAM score=190