Re: [mailop] Recent "banned sending IP" errors when sending to Microsoft

2018-06-25 Thread John Possidente
That looks like the standard Office365 "you got listed" message. Even
legitimate B2B bulk mail will now and then generate these. Just follow the
instructions; delisting is straightforward. If it recurs, of course, you
might have a troublesome mailer on your hands.

John


On Mon, Jun 25, 2018 at 12:24 PM, Josh Campbell 
wrote:

> Has anyone else noticed these errors? We hadn't really seen them
> previously. They look like this:
>
> smtp;550 5.7.606 Access denied, banned sending IP [xxx.xxx.xxx.xxx]. To
> request removal from this list please visit https://sender.office.com/
> and follow the directions. For more information please go to
> http://go.microsoft.com/fwlink/?LinkID=526655 (AS16012609) [
> AM5EUR03FT031.eop-EUR03.prod.protection.outlook.com]
>
> We've only started seeing them in the past month and only a small amount
> of IPs have been affected at any one time.
>
> The interesting thing is all of these IPs are in the same IP range (out of
> the three major ranges we have).
>
> I'm wondering if this is a new phenomenon for anyone else and why it only
> appears to affect one of my IP ranges. (Also, if anyone from Microsoft
> cares to get in touch, I'd love to hear from you.)
>
> Josh Campbell, Deliverability Engineer
> MailChimp
>
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>
>
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] Comcast contact? bounce.care.comcast.com

2018-06-25 Thread Al Iverson via mailop
Hey Carl, I think this refers to emails originating within the
Salesforce Marketing Cloud (ExactTarget) platform, but the SPF missing
IP and DKIM failure touch on something that I think is happening to
the mail after it leaves our system. I've spun up a support case to
reach out to the client and ask them if they'd like us to update the
SPF record as indicated and suggesting that they review the potential
DKIM configuration issue.

If a Comcast person sees this and wants to coordinate, feel free to
reach out to me.

Thanks for the heads up.

Cheers,
Al Iverson
On Mon, Jun 25, 2018 at 12:12 PM Carl Byington  wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> bounce.care.comcast.com has
>
> "v=spf1 include:cust-spf.exacttarget.com ip4:76.96.68.101
> ip4:76.96.68.102 ip4:76.96.68.103 ip4:69.252.76.7 ip4:69.252.76.8
> ip4:69.252.76.9 -all"
>
> Note the -all, but at least some mail is arriving here via resqmta-po-
> 04v.sys.comcast.net == 96.114.154.163 not listed in the above spf
> record. You might want to fix that.
>
> Also, the DKIM signature from mdp.comcast.net is broken -
> reason="signature verification failed".
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEAREKAAYFAlsxE2YACgkQL6j7milTFsHZlQCfQ7i8CCsnP+Jy5R1lrFjw7A//
> VyQAn3yFmOu5o/0HTCDnMUWHyH78DS48
> =XKZW
> -END PGP SIGNATURE-
>
>
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop



-- 
al iverson // 312-725-0130 // miami
http://www.aliverson.com
http://www.spamresource.com

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


[mailop] Recent "banned sending IP" errors when sending to Microsoft

2018-06-25 Thread Josh Campbell
Has anyone else noticed these errors? We hadn't really seen them
previously. They look like this:

smtp;550 5.7.606 Access denied, banned sending IP [xxx.xxx.xxx.xxx]. To
request removal from this list please visit https://sender.office.com/ and
follow the directions. For more information please go to
http://go.microsoft.com/fwlink/?LinkID=526655 (AS16012609) [
AM5EUR03FT031.eop-EUR03.prod.protection.outlook.com]

We've only started seeing them in the past month and only a small amount of
IPs have been affected at any one time.

The interesting thing is all of these IPs are in the same IP range (out of
the three major ranges we have).

I'm wondering if this is a new phenomenon for anyone else and why it only
appears to affect one of my IP ranges. (Also, if anyone from Microsoft
cares to get in touch, I'd love to hear from you.)

Josh Campbell, Deliverability Engineer
MailChimp
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] [EXTERNAL] Comcast contact? bounce.care.comcast.com

2018-06-25 Thread Brotman, Alexander
Carl,

You can contact me off-list with specific details if you have more information.

--
Alex Brotman
Sr. Engineer, Anti-Abuse
Comcast


-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Carl Byington
Sent: Monday, June 25, 2018 12:09 PM
To: mailop@mailop.org
Subject: [EXTERNAL] [mailop] Comcast contact? bounce.care.comcast.com

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

bounce.care.comcast.com has

"v=spf1 include:cust-spf.exacttarget.com ip4:76.96.68.101
ip4:76.96.68.102 ip4:76.96.68.103 ip4:69.252.76.7 ip4:69.252.76.8
ip4:69.252.76.9 -all"

Note the -all, but at least some mail is arriving here via resqmta-po- 
04v.sys.comcast.net == 96.114.154.163 not listed in the above spf record. You 
might want to fix that.

Also, the DKIM signature from mdp.comcast.net is broken - reason="signature 
verification failed".


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAlsxE2YACgkQL6j7milTFsHZlQCfQ7i8CCsnP+Jy5R1lrFjw7A//
VyQAn3yFmOu5o/0HTCDnMUWHyH78DS48
=XKZW
-END PGP SIGNATURE-



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


[mailop] Comcast contact? bounce.care.comcast.com

2018-06-25 Thread Carl Byington
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

bounce.care.comcast.com has

"v=spf1 include:cust-spf.exacttarget.com ip4:76.96.68.101
ip4:76.96.68.102 ip4:76.96.68.103 ip4:69.252.76.7 ip4:69.252.76.8
ip4:69.252.76.9 -all"

Note the -all, but at least some mail is arriving here via resqmta-po-
04v.sys.comcast.net == 96.114.154.163 not listed in the above spf
record. You might want to fix that.

Also, the DKIM signature from mdp.comcast.net is broken -
reason="signature verification failed".


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEAREKAAYFAlsxE2YACgkQL6j7milTFsHZlQCfQ7i8CCsnP+Jy5R1lrFjw7A//
VyQAn3yFmOu5o/0HTCDnMUWHyH78DS48
=XKZW
-END PGP SIGNATURE-



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