Como bloquear / colocar na lista negra um servidor de spam através do registro SPF

1

Eu tenho um registro SPF:

v=spf1 include:_spf.google.com ip4:70.xx.xx.xx -all

Eu tinha o padrão do Google de

v=spf1 include:_spf.google.com ~all

Eu tenho me afastado desse padrão em um esforço para usar o SPF para evitar que alguns spammers no Irã continuem a enviar mensagens que, quando eles acessam um endereço falso, retornam para mim com mensagens como:

Received-SPF: neutral (google.com: 2.191.xx.xx is neither permitted nor denied by best guess record for domain of [[email protected]]) client-ip=2.191.xx.xx;

Essa mensagem implica que há uma maneira de negar o IP do spammer, mas eu não consegui encontrá-lo, então estou inseguro.

Alguma dica? Eu gostaria que este spammer fosse negado pelo meu SPF direta ou indiretamente.

Atualização: mensagem completa e inalterada adicionada à qual estou tentando reagir (abaixo)

Delivered-To: [email protected]
Received: by 10.28.62.13 with SMTP id l13csp432424wma;
        Sat, 22 Oct 2016 05:10:20 -0700 (PDT)
X-Received: by 10.99.104.196 with SMTP id d187mr9004304pgc.26.1477158220522;
        Sat, 22 Oct 2016 05:10:20 -0700 (PDT)
Return-Path: <>
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com. [2607:f8b0:400e:c00::241])
        by mx.google.com with ESMTPS id hf1si1759156pac.263.2016.10.22.05.10.20
        for <[email protected]>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Sat, 22 Oct 2016 05:10:20 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of [email protected] designates 2607:f8b0:400e:c00::241 as permitted sender) client-ip=2607:f8b0:400e:c00::241;
Authentication-Results: mx.google.com;
       dkim=pass [email protected];
       spf=pass (google.com: best guess record for domain of [email protected] designates 2607:f8b0:400e:c00::241 as permitted sender) smtp.helo=mail-pf0-x241.google.com;
       dmarc=pass (p=QUARANTINE dis=NONE) header.from=googlemail.com
Received: by mail-pf0-x241.google.com with SMTP id r16so11229439pfg.3
        for <[email protected]>; Sat, 22 Oct 2016 05:10:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=mime-version:from:to:subject:message-id:date;
        bh=hC195D3nA0Uzbsy/ut7vMIZ53a6ExjkByblQBH/81WQ=;
        b=AJOIjSrQPo4+I5fbjmy+4QU7BBVFtRorLh4NYVEZv0zMY5dYn9OMh4pVRRiQoSN4JE
         k0JZJbBzkvPNGXD0ImqQ+cRPD6/Q9yN+QjbRJksR91dJvO2ZeM36OLsY7erIbOYgq1rz
         H80waLIVDDJSRZv2r4zvFnX9K6hE6fZDbDG7x3jKRkGnIzQk2Z1aQ/TGPTz8parrQJrT
         hryzTMSw7T5DKioVYElBpH/wlS8HMaoL2g023KzBtpwLrfkbFE3zeTv0GTryhEeunONH
         +UPEvLr+th5IKpG4VZlrGu17Vz4MKgJgB30g+KGu/Ljbzi/ffLSpSFkN7hZvs2mmBpY+
         PoRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:from:to:subject:message-id:date;
        bh=hC195C3nA0Uzbsy/ut7vMKZ43a6ExjjByblQBH/81WQ=;
        b=HTTQdb/I0eBlF6Q3o0z/wf24aSyu2lvlvIkpoC4Ov+l7c+ruXRnzT5mkUMWiDFCr/w
         LuDQcy7SluQrrnWsCm1k87F4gsUz320Zvb9lCEBqB4FnN37e521tP/C++4tzv6tA09Sd
         W5Wpsk38bHYj5jesKABb0k0Nj4tmS39j7h18BqTY0fnCHjb03pLJNGA1hmACX84Clf27
         bhsCyMhb5z6L7t5UOYTwQ95e2Vlx6jQH2P/h9iKyI+UnpoMOCe9grbvblSkdDiWTTMXR
         5G9KhdrTUmIBfrj+VlhZQoPRXjEjENeD4XEAZ1E4e3lBJfgGbg9Jg6N6PwpxFbnlGReW
         gwHA==
X-Gm-Message-State: ABUngvdfy0M/HHPXzmBpM3vEavjKEG5m35WPLvqH5SEh5U6PEOqEaJ7yK/eqjzO7jzkY1v9GbShSkKocgRqx1k3N1bmPLGh0
X-Received: by 10.99.110.142 with SMTP id j136mr8866332pgc.132.1477138220162;
        Sat, 22 Oct 2016 05:10:20 -0700 (PDT)
MIME-Version: 1.0
Return-Path: <>
Received: by 10.99.110.142 with SMTP id j136mr8914431pgc.132; Sat, 22 Oct 2016 05:10:20 -0700 (PDT)
From: Mail Delivery Subsystem <[email protected]>
To: [email protected]
Subject: Delivery Status Notification (Delay)
Message-ID: <[email protected]>
Date: Sat, 22 Oct 2016 12:10:20 +0000
Content-Type: text/plain; charset=UTF-8

This is an automatically generated Delivery Status Notification

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipient has been delayed:

     [email protected]

Message will be retried for 4 more day(s)

Technical details of temporary failure: 
The recipient server did not accept our requests to connect. Learn more at https://support.google.com/mail/answer/7720 
[210.5.32.9 210.5.32.9: generic::failed_precondition: connect error (0): error]

----- Original message -----

X-Gm-Message-State: ABUngvdKe24Xp8DT1rP2gApcFad5/HjrNajRrB9UWHnLxPY9Cmcnd7WyG1oLjYpJrvk4WmDa+0noZVd+uXaMy0PzgG1WVtzkSWXlgEFBYAOKWZTeGeIEOnQJPFBFZJuzwxnkd+KVKcW5
X-Received: by 10.99.110.142 with SMTP id j136mr16455830pgc.132.1476957867242;
        Thu, 20 Oct 2016 03:04:27 -0700 (PDT)
X-Received: by 10.99.110.142 with SMTP id j136mr16455815pgc.132.1476957867120;
        Thu, 20 Oct 2016 03:04:27 -0700 (PDT)
Return-Path: <[email protected]>
Received: from [2.191.29.134] ([2.191.29.134])
        by mx.google.com with ESMTP id z80si44284204pfj.251.2016.10.20.03.04.25
        for <[email protected]>;
        Thu, 20 Oct 2016 03:04:26 -0700 (PDT)
Received-SPF: neutral (google.com: 2.191.29.134 is neither permitted nor denied by best guess record for domain of [email protected]) client-ip=2.191.29.134;
Authentication-Results: mx.google.com;
       spf=neutral (google.com: 2.191.29.134 is neither permitted nor denied by best guess record for domain of [email protected]) [email protected]
Message-ID: <233E36AEEE2BA6766B63FBEB0EF3233E@6C2L74D>
From: <[email protected]>
To: <[email protected]>
Subject: Re: Salary [$1500 /week]
Date: 20 Oct 2016 15:04:13 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
    boundary="----=_NextPart_000_0027_01D22AD6.01109020"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3505.912
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912

Dear samantha.bowmer,

We are looking for employees working remotely.

My name is Thanh, I am the personnel manager of a large International company.
Most of the work you can do from home, that is, at a distance.

Salary is $2900-$5100.

If you are interested in this offer, please visit 
Our Site

Have a nice day!
    
por James T Snell 29.10.2016 / 18:08

1 resposta

2

SPF não significa não entregar o email, é apenas um sinalizador que diz para "Hard Fail" (-all) a mensagem, que pode fazê-lo parar na pasta de spam, que é baseada no ESP.

Se você ativar o DMARC com uma Política de rejeição, 100% fará com que a mensagem seja rejeitada e não entregue àqueles ESP que respeitem uma Política DMARC. O GMAIL é um desses lugares.

Ativar um registro DMARC é tão simples quanto adicionar um registro SPF, é baseado completamente em uma entrada de DNS como o SPF.

No seu caso, seu registro DMARC será bastante simples.

_dmarc.somedomain.ca. IN TXT "v=DMARC1; p=reject; sp=none; rf=afrf; pct=100; ri=86400"

Se você quiser os relatórios, basta adicionar as informações do RUA e RUF ao registro acima. Você pode Geradores DMARC gerar o registro para você.

    
por 29.10.2016 / 22:02