date:20180801

Re: [mailop] Gmail change DMARC Policy?

2018-08-01 Thread Bill Cole


On 1 Aug 2018, at 10:34 (-0400), Emanuel Gonzalez wrote:


Hello, thanks for the reply. I never had problems until today.


Here the mailchimp header:


[...]

ARC-Authentication-Results: i=1; mx.google.com;
   dkim=pass header.i=@mail213.atl171.mcdlv.net header.s=k1 
header.b=eLWpUpKv;
   dkim=pass header.i=@gmail.mcsv.net header.s=k1 
header.b=Tv6+avr7;
   spf=pass (google.com: domain of 
bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net 
designates 198.2.138.213 as permitted sender) 
smtp.mailfrom="bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net";
   dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) 
header.from=gmail.com


That's a DMARC fail because your "From:" is not aligned to any DKIM 
signature.


[...]

Authentication-Results: mx.google.com;
   dkim=pass header.i=@mail213.atl171.mcdlv.net header.s=k1 
header.b=eLWpUpKv;
   dkim=pass header.i=@gmail.mcsv.net header.s=k1 
header.b=Tv6+avr7;
   spf=pass (google.com: domain of 
bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net 
designates 198.2.138.213 as permitted sender) 
smtp.mailfrom="bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net";
   dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) 
header.from=gmail.com


That's a DMARC fail because your "From:" is not aligned to any DKIM 
signature.


DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=k1; 
d=mail213.atl171.mcdlv.net;

[...]
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=k1; 
d=gmail.mcsv.net;

[...]

Those signatures (both done by MailChimp) will only align to a From 
header address in one of those 'd=' domains.


[...]

From: Emanuel 


That does not align to any signature, so DMARC fails.


But wait! There's MORE!


Sender: Emanuel 


If that address had been in the From header, the message might have 
passed DMARC, because it aligns with a signature.


If you want DMARC to work for your mail, use a From header for which you 
(or your ESP) can legitimately create a DKIM signature.
If you want undefined and inscrutably random behavior by receivers based 
on your DKIM signatures, make sure they don't align to your From header 
and so cannot pass DMARC.


--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Currently Seeking Steadier Work: https://linkedin.com/in/billcole

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Return Path FBL not working?

2018-08-01 Thread Sara Roper via mailop

Hey Marc - will reach to you off list to see if I can help or find help for
you.

On Wed, Aug 1, 2018 at 12:38 PM Marc Goldman via mailop 
wrote:

> Is anyone else having problems receiving confirmation emails/password
> resets from Return Paths FBL service?
>
> I have requested multiple times from multiple addresses and not received
> anything.
>
>
>
> Marc Goldman
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>

-- 
*Sara Roper, CISSP, GLEG*
Sr Director, Data Services Operations | *Return Path*
w | 3039993155
m | 3036531484
sara.ro...@returnpath.com
LinkedIn | Sara Roper 

© 2018 Return Path, Inc. All Rights Reserved. Confidential and Proprietary
Information of Return Path. Return Path, and the Return Path logo are
registered trademarks of Return Path, Inc. These materials may not be
reproduced or distributed in any way without the written permission of
Return Path, Inc. These materials are provided AS-IS, without any warranty,
express or implied. These materials are not intended and should not be
interpreted as advice, legal or otherwise, of any kind. Return Path, Inc.
does not accept any liability to you or any third party for any content or
information in these materials.

[image: Powered by Sigstr]

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

[mailop] Return Path FBL not working?

2018-08-01 Thread Marc Goldman via mailop

Is anyone else having problems receiving confirmation emails/password resets 
from Return Paths FBL service?

I have requested multiple times from multiple addresses and not received 
anything.



Marc Goldman___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Gmail change DMARC Policy?

2018-08-01 Thread Laura Atkins

I’m not actually seeing a problem here or understanding what your issue is. 

In terms of the forgery message. I expect that Gmail is special casing some 
ESPs (like mailchimp, and I expect there are others). So they’re allowing 
customers of those ESPs to use @gmail.com addresses in the From: line and are 
not treating that as a forgery. It makes sense, as Mailchimp (like other ESPs), 
actually confirms address ownership before allowing it to be used as a From: 
address. Because the ESPs act responsibly, Gmail doesn’t need to warn that the 
mail might be a forgery. It’s not, the ESP has assured that. 

If you’re sending from a different place, one with unknown policies, then Gmail 
doesn’t know anything about that, so it offers the warning. 

All in all, quite a sensible implementation from Gmail.

What’s the problem you’re trying to solve?

laura 

> On Aug 1, 2018, at 8:52 AM, Emanuel Gonzalez  
> wrote:
> 
> Hello, thanks for the help and reply.
> 
> The problem not solved.
> 
> any ideas?
> 
> Regards.
> De: Stefano Bagnara mailto:mai...@bago.org>>
> Enviado: miércoles, 1 de agosto de 2018 12:18:41
> Para: mailop
> Cc: emanuel_gonza...@live.com.ar
> Asunto: Re: [mailop] Gmail change DMARC Policy?
>  
> On Wed, 1 Aug 2018 at 15:26, Emanuel Gonzalez
>  wrote:
> > I have a problem with Gmail, i see a change in the dmarc header:
> > [...]
> > the emails sent arrive to the promotions folder but with a forgery alert 
> > (fake identity), when I send mails from mailchimp it does not return any 
> > warning haha because?
> >
> > header from my email marketing provider:
> >
> > Delivered-To: emaw...@gmail.com
> > [...]
> > From: GmailEnviando 
> > Reply-To: GmailEnviando 
> >
> > any ideas?
> 
> That's because sender and recipient are the same address. Try sending
> to another gmail address and let us know if you see the same alert.
> 
> -- 
> Stefano Bagnara
> Apache James/jDKIM/jSPF
> VOXmail/Mosaico.io/VoidLabs
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

-- 
Having an Email Crisis?  We can help! 800 823-9674 

Laura Atkins
Word to the Wise
la...@wordtothewise.com
(650) 437-0741  

Email Delivery Blog: https://wordtothewise.com/blog 

___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Gmail change DMARC Policy?

2018-08-01 Thread Emanuel Gonzalez

Hello, thanks for the help and reply.

The problem not solved.

any ideas?

Regards.

De: Stefano Bagnara 
Enviado: miércoles, 1 de agosto de 2018 12:18:41
Para: mailop
Cc: emanuel_gonza...@live.com.ar
Asunto: Re: [mailop] Gmail change DMARC Policy?

On Wed, 1 Aug 2018 at 15:26, Emanuel Gonzalez
 wrote:
> I have a problem with Gmail, i see a change in the dmarc header:
> [...]
> the emails sent arrive to the promotions folder but with a forgery alert 
> (fake identity), when I send mails from mailchimp it does not return any 
> warning haha because?
>
> header from my email marketing provider:
>
> Delivered-To: emaw...@gmail.com
> [...]
> From: GmailEnviando 
> Reply-To: GmailEnviando 
>
> any ideas?

That's because sender and recipient are the same address. Try sending
to another gmail address and let us know if you see the same alert.

--
Stefano Bagnara
Apache James/jDKIM/jSPF
VOXmail/Mosaico.io/VoidLabs
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Gmail change DMARC Policy?

2018-08-01 Thread Emanuel Gonzalez

Hello, thanks for the reply. I never had problems until today.


Here the mailchimp header:


Delivered-To: emaw...@gmail.com
Received: by 2002:a1c:e046:0:0:0:0:0 with SMTP id x67-v6csp618596wmg;
Wed, 1 Aug 2018 03:43:00 -0700 (PDT)
X-Google-Smtp-Source: 
AAOMgpd32+ojoMsyr28GQXTFMwZ4mifsPAFm8Xg/YsjNGrS2/nP19iALwijyTQyrkITRMHicrt4a
X-Received: by 2002:a5b:601:: with SMTP id d1-v6mr13207440ybq.295.1533120179983;
Wed, 01 Aug 2018 03:42:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1533120179; cv=none;
d=google.com; s=arc-20160816;
b=aiAloEPH+hFOebvVwO6V8Z8muwF2Tq5mbGAqzZ/EGblphcWyqZ86H20Gdp1ra5g1lI
 y6LW2rGimmmj71lsmH4ZadjCdEDWW62njxdP6Gds/PJeSp1/us35BzNRL2K7T4QmF+7r
 PXOAao242vJviyOZAzw7qSaDxLdS04BG0pbQ1sylBvYrgfjPeEtkXMlIzmW7XUpXCW3+
 VrT6ZLi2zRMdhcv8K1WuYa4V/tZsExJqMx4dCcP0K7uClKLl2WdnkefwadkgE0RM+G4i
 oyguITL772RN/JDwXfgRWCa5WUDZkg0PRpHGX8/WtYR0VoaFMT0XeCTtfceCIWV/7SBT
 p6Yw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 
s=arc-20160816;
h=mime-version:sender:list-unsubscribe-post:list-unsubscribe:list-id
 :feedback-id:message-id:date:to:reply-to:from:subject:dkim-signature
 :dkim-signature:arc-authentication-results;
bh=KwIMxi4IzcZU/hly+oTHKG9YjAO5k9RmkhFxzyquH2M=;
b=UL9rXXzcnc0hJWZnZx5VkPCsZym2TUHd9j+TozsXWFR6vkjcMuqXFBzrnTX3dCIPm3
 09WJsf5yXPFqoFNhzY1GwyT8ndBfzNOYypsAtu3bcl0Iympgi5V7Z23swSTf9ZlxKRJw
 aoTyKHM02xTMqVUhTAZq0AKJ4Ph21c63rDEUpUis8+PnptdgnHG9srVsS4vyW7TjIWgz
 IJujgbPqRX6Ghub9QRKnuHaQ5twwaVWYKxPAu583inrz4JMGS1vZ7DGXVi5Y4jhuFxY4
 Rde/HIszNrYMXZHoC2Jk9RVGDap6pKze8LYd147P1YWZtI23iFH26epJlxVhjUCRxJiA
 YuWg==
ARC-Authentication-Results: i=1; mx.google.com;
   dkim=pass header.i=@mail213.atl171.mcdlv.net header.s=k1 
header.b=eLWpUpKv;
   dkim=pass header.i=@gmail.mcsv.net header.s=k1 header.b=Tv6+avr7;
   spf=pass (google.com: domain of 
bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net 
designates 198.2.138.213 as permitted sender) 
smtp.mailfrom="bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net";
   dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
Return-Path: 

Received: from mail213.atl171.mcdlv.net (mail213.atl171.mcdlv.net. 
[198.2.138.213])
by mx.google.com with ESMTPS id 
d133-v6si3886653ywb.195.2018.08.01.03.42.59
for 
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 01 Aug 2018 03:42:59 -0700 (PDT)
Received-SPF: pass (google.com: domain of 
bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net 
designates 198.2.138.213 as permitted sender) client-ip=198.2.138.213;
Authentication-Results: mx.google.com;
   dkim=pass header.i=@mail213.atl171.mcdlv.net header.s=k1 
header.b=eLWpUpKv;
   dkim=pass header.i=@gmail.mcsv.net header.s=k1 header.b=Tv6+avr7;
   spf=pass (google.com: domain of 
bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net 
designates 198.2.138.213 as permitted sender) 
smtp.mailfrom="bounce-mc.us15_75091638.537013-emawata=gmail@mail213.atl171.mcdlv.net";
   dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=k1; 
d=mail213.atl171.mcdlv.net; 
h=Subject:From:Reply-To:To:Date:Message-ID:List-ID:List-Unsubscribe:Sender: 
Content-Type:MIME-Version; i=emawata=3dgmail@mail213.atl171.mcdlv.net; 
bh=KwIMxi4IzcZU/hly+oTHKG9YjAO5k9RmkhFxzyquH2M=; 
b=eLWpUpKvDQYakRVOA/Bpc0lacOQL/Mw7rVniaZx96fK3dsL7aVkq4pikk8gh9kRkT3O6A9D7DeBn
   RKJQvUOupk8BKNB/rbA4qHdpe1PSu00QNPOi2z5ptY9nmhwOn2BatX1CbdRuAZaaEt4QAJVYrfzs
   rRdZBIelctCK9jdfyKs=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=k1; d=gmail.mcsv.net; 
h=Subject:From:Reply-To:To:Date:Message-ID:Feedback-ID:List-ID: 
List-Unsubscribe:Sender:Content-Type:MIME-Version; 
bh=KwIMxi4IzcZU/hly+oTHKG9YjAO5k9RmkhFxzyquH2M=; 
b=Tv6+avr7ZWDhZQaLo7QShvu5XNXB0z2Y2EjbH59u7BceWeEQfWilv3bgU01txxMIxEkYQbUqkHld
   La6YAHcLg6aa/m6t3SSZaEblI45n/n4J5JD9Wh5pcxHg41dxa63k9zb4+yqG/KKCkme4K6wIG76q
   WIidIiRZRUtUowbCVeU=
Received: from (127.0.0.1) by mail213.atl171.mcdlv.net id hc67b62ddl42 for 
; Wed, 1 Aug 2018 10:42:56 + (envelope-from 
)
Subject: Probando el filtro
From: Emanuel 
Reply-To: 
To: 
Date: Wed, 1 Aug 2018 10:42:56 +
Message-ID: 
<40c8ed8b20f446618ea65d6dc.77c14f64f9.20180801104246.8e09cee022.e4b42...@mail213.atl171.mcdlv.net>
X-Mailer: MailChimp Mailer - **CID8e09cee02277c14f64f9**
X-Campaign: mailchimp40c8ed8b20f446618ea65d6dc.8e09cee022
X-campaignid: mailchimp40c8ed8b20f446618ea65d6dc.8e09cee022
X-Report-Abuse: Please report abuse for this campaign here: 
http://www.mailchimp.com/abuse/abuse.phtml?u=40c8ed8b20f446618ea65d6dc=8e09cee022=77c14f64f9
X-MC-User: 40c8ed8b20f446618ea65d6dc
Feedback-ID: 75091638:75091638.537013:us15:mc
List-ID: 40c8ed8b20f446618ea65d6dcmc list

Re: [mailop] Gmail change DMARC Policy?

2018-08-01 Thread Ken O'Driscoll via mailop

On Wed, 2018-08-01 at 13:23 +, Emanuel Gonzalez wrote:
> header.from=gmail.com

DMARC fails in both cases because you are spoofing the From address as
being from gmail.com when it is not.

They haven't changed their DMARC policy (it's still p=none) but that does
not affect the fact that message fails a DMARC test.

As to why one forged message is classified differently to another, that's
likely down to many data points, DMARC just being one of them.

Sending newsletters / bulk emails from a forged gmail.com (or other
freemail address) is going to cause problems in general.

Ken.

-- 
Ken O'Driscoll / We Monitor Email
t: +353 1 254 9400 | w: www.wemonitoremail.com

Need to understand deliverability? Now there's a book:
www.wemonitoremail.com/book


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

[mailop] Gmail change DMARC Policy?

2018-08-01 Thread Emanuel Gonzalez

Hello.!!!


I have a problem with Gmail, i see a change in the dmarc header:

ARC-Authentication-Results: i=1; mx.google.com;
   dkim=pass header.i=@94983.senders.tstes.net header.s=esdkim 
header.b=IplGe1Oe;
   dkim=pass header.i=@gmail.tstes.net header.s=dkim header.b=FQWgkG0I;
   spf=pass (google.com: domain of 
bounces-emawata=gmail@94983.returnpath.tstes.net designates 200.58.118.64 
as permitted sender) 
smtp.mailfrom="bounces-emawata=gmail@94983.returnpath.tstes.net";
   dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com

the emails sent arrive to the promotions folder but with a forgery alert (fake 
identity), when I send mails from mailchimp it does not return any warning haha 
because?

header from my email marketing provider:

Delivered-To: emaw...@gmail.com
Received: by 2002:a1c:e046:0:0:0:0:0 with SMTP id x67-v6csp629260wmg;
Wed, 1 Aug 2018 03:56:10 -0700 (PDT)
X-Google-Smtp-Source: 
AAOMgpfyYYSrzx+kZi+JHyKNMIHdqm4zPxgTli5PCbvj9x9fdvZ0IPrxHrw6eOGmb/KpOyxl2/MO
X-Received: by 2002:a37:69c3:: with SMTP id 
e186-v6mr24336280qkc.396.1533120970612;
Wed, 01 Aug 2018 03:56:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1533120970; cv=none;
d=google.com; s=arc-20160816;
b=xHS7fgzrUf9jtBZJY4Ac5SAgtJCss6O5ZPFPt9Xvu7z8sBojSmt5PpEiFPZ9+8ljhu
 2P7MkvvzTou9Q8ozZOl4u5QCPYQypLZ6UOqqYE8eoWNW0InjAskFI/G9icpfxb7SYgsa
 BZHJP/yIVuefsl1d0PQ8peJIGjkQJIAMCXwlbzze1syem8ROJLyBmki2I2H4owW0j3/1
 Gao8PyoGEVVqKCmCixJGoRWLRrE2AIRFs8nyFmvzJfdEjYpYbTnHW1iucGohCqeF3HSl
 z26+BtfawxmboqW4vqpKG4hidWV9+o0sm61hXMfLMNsVYmFWTUKTiBOV2paSK6qEYCY/
 mUNQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 
s=arc-20160816;
h=message-id:date:to:mime-version:subject:list-unsubscribe
 :feedback-id:list-id:sender:reply-to:from:precedence:dkim-signature
 :dkim-signature:arc-authentication-results;
bh=WlV74hnf502NFLfJVcfDuTEraxlb+UX5FtcE7aN1Ljk=;
b=WDqnbFLtjwOitNwOIuyCEgCY5HjvbUyqbR1FcH1lTL/LyUcIMuKS1QnkpmwF0utsu8
 +mYp2/9BnK0M8h5soOBAgjh6mzZW6hdxLiu/hIB6iVC1fJTNv3q08Og0CGHau2rMyFuC
 P3xXS/K6uQWuepYdI46KH4zOvAYG7NomnbDkxNqtr681OtI0wCAyu1YbXtzTg8/h3hfU
 fPU/crrsDmsKK0blcKmsqLNuuzb+ykbpMtnma89OTALqBEB189VVdtTEmegNXe3ML0qA
 Fs6pzbT1tLUqTMbtyf12OJwWw5gNUAortE4fiMx5cGC1rXFRKkohPA8sgD8f3lSa0M7D
 Ab5g==
ARC-Authentication-Results: i=1; mx.google.com;
   dkim=pass header.i=@94983.senders.tstes.net header.s=esdkim 
header.b=IplGe1Oe;
   dkim=pass header.i=@gmail.tstes.net header.s=dkim header.b=FQWgkG0I;
   spf=pass (google.com: domain of 
bounces-emawata=gmail@94983.returnpath.tstes.net designates 200.58.118.64 
as permitted sender) 
smtp.mailfrom="bounces-emawata=gmail@94983.returnpath.tstes.net";
   dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
Return-Path: 
Received: from mta118.64.tstes.net (mta118.64.tstes.net. [200.58.118.64])
by mx.google.com with ESMTPS id 
x52-v6si334753qvh.260.2018.08.01.03.56.08
for 
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 01 Aug 2018 03:56:10 -0700 (PDT)
Received-SPF: pass (google.com: domain of 
bounces-emawata=gmail@94983.returnpath.tstes.net designates 200.58.118.64 
as permitted sender) client-ip=200.58.118.64;
Authentication-Results: mx.google.com;
   dkim=pass header.i=@94983.senders.tstes.net header.s=esdkim 
header.b=IplGe1Oe;
   dkim=pass header.i=@gmail.tstes.net header.s=dkim header.b=FQWgkG0I;
   spf=pass (google.com: domain of 
bounces-emawata=gmail@94983.returnpath.tstes.net designates 200.58.118.64 
as permitted sender) 
smtp.mailfrom="bounces-emawata=gmail@94983.returnpath.tstes.net";
   dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=esdkim; 
d=94983.senders.tstes.net; 
h=From:Reply-To:Sender:List-ID:List-Unsubscribe:Subject:Content-Type:MIME-Version:To:Date:Message-ID;
 i=emawata=3dgmail@94983.senders.tstes.net; 
bh=WlV74hnf502NFLfJVcfDuTEraxlb+UX5FtcE7aN1Ljk=; 
b=IplGe1OeZMF4tC2eASRGff4gJB19X6JKtli/k1qk9I5APSELeOHHYM7tGPU1CJnyRS18iN7C2PkO
   v5QCCSK5arr8FNXHkBhPQ7aGkDsaJXZywC0LIXZPYMYyTHMSsRLI85k7WYg9SQJkiu/KdqiBO3Az
   0ypBojLX6LrpI6yaOAI=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; 
d=gmail.tstes.net; 
h=From:Reply-To:Sender:List-ID:Feedback-ID:List-Unsubscribe:Subject:Content-Type:MIME-Version:To:Date:Message-ID;
 bh=WlV74hnf502NFLfJVcfDuTEraxlb+UX5FtcE7aN1Ljk=; 
b=FQWgkG0IX0gh6SVi+1qBmOZ0gr0UchSmj+pXt4Z5VXLJCZtqEQMcG7jDp+fW5vfwK5VPX9ib6jJy
   FWIdddcBqphjGhC7c0evBIUGxsNZ2+Ku3q05An9Dr4M41H42nWntHCkaVIYZmtIK4Kr7D9FPr+pC
   JafGanE/68nqkQYWLqc=
Precedence: bulk
X-DM-SENDER: MAILTX
From: GmailEnviando 
Reply-To: GmailEnviando 
X-DM-Tracking-Domain: 1
X-DM-Priority: 10
X-Report-Abuse: Please report abuse for this campaign here:
http://envialosimple.com/abuse/

Re: [mailop] mailop Digest, Vol 130, Issue 1

2018-08-01 Thread Andy Onofrei via mailop

HI, 

An update ..its not a bug or anything , its expected behavior .. after you add 
the feed  then it will disappear for some time and re-appear .
All the newly created feeds are now being displayed correctly.

Regards
Andy

-Original Message-
From: mailop  On Behalf Of mailop-requ...@mailop.org
Sent: Wednesday, August 1, 2018 1:00 PM
To: mailop@mailop.org
Subject: mailop Digest, Vol 130, Issue 1

Send mailop mailing list submissions to
mailop@mailop.org

To subscribe or unsubscribe via the World Wide Web, visit

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchilli.nosignal.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmailopdata=02%7C01%7Candrei.onofrei%40microsoft.com%7C6ce31a04ea424bd6eb2908d5f79e161d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636687180711788266sdata=AotAxd%2BXInB9xDShRp5urrH4Yn0NHEluVM5hcLeJsY0%3Dreserved=0
or, via email, send a message with subject or body 'help' to
mailop-requ...@mailop.org

You can reach the person managing the list at
mailop-ow...@mailop.org

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of mailop digest..."


Today's Topics:

   1. Microsoft SNDS issue (Andy Onofrei)


--

Message: 1
Date: Tue, 31 Jul 2018 13:57:19 +
From: Andy Onofrei 
To: "mailop@mailop.org" 
Subject: [mailop] Microsoft SNDS issue
Message-ID:



Content-Type: text/plain; charset="iso-8859-2"

Hi,

I currently have 3 feeds in our SNDS dashboard. I want to add new ones as we 
add new sender domains.

When I add any feeds I receive a success message that the feed was added 
successfully , I can see it in the dashboard , however after some time ( 10-20 
min) that feed is disappearing .
I tried multiple one making sure to add the ips in the correct format , 
everytime it disappears.

Did anyone experienced this kind of behavior ? Or any possible causes for this 
issue?


Regards,
Andrei Onofrei
Dynamics 365 Email Deliverability Engineer 
andrei.onof...@microsoft.com | +420 720 
359 205 BBC Delta Building, Vyskočilova 1561/4a, 140 00 Prague, The Czech 
Republic [cid:image001.jpg@01CE6679.2CA88280]

-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1563 bytes
Desc: image001.jpg
URL: 


--

Subject: Digest Footer

___
mailop mailing list
mailop@mailop.org
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchilli.nosignal.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmailopdata=02%7C01%7Candrei.onofrei%40microsoft.com%7C6ce31a04ea424bd6eb2908d5f79e161d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636687180711788266sdata=AotAxd%2BXInB9xDShRp5urrH4Yn0NHEluVM5hcLeJsY0%3Dreserved=0


--

End of mailop Digest, Vol 130, Issue 1
**
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] Gmail change DMARC Policy?

Re: [mailop] Return Path FBL not working?

[mailop] Return Path FBL not working?

Re: [mailop] Gmail change DMARC Policy?

Re: [mailop] Gmail change DMARC Policy?

Re: [mailop] Gmail change DMARC Policy?

Re: [mailop] Gmail change DMARC Policy?

[mailop] Gmail change DMARC Policy?

Re: [mailop] mailop Digest, Vol 130, Issue 1

9 matches

Site Navigation

Mail list logo

Footer information