Re: [mailop] [EXTERNAL] Re: BIMI

[Brotman, Alexander via mailop]

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

> -Original Message-
> From: mailop  On Behalf Of John R Levine via
> mailop
> Sent: Tuesday, December 10, 2019 8:32 PM
> To: Brandon Long 
> Cc: mailop 
> Subject: [EXTERNAL] Re: [mailop] BIMI
>
>
> I sadly realize that I am the last person in the world using Alpine.
>

I still use Alpine, though alongside other webmail platforms.  Maybe we can 
start a movement :)


>
> ___
> mailop mailing list
> mailop@mailop.org
> https://urldefense.com/v3/__https://chilli.nosignal.org/cgi-
> bin/mailman/listinfo/mailop__;!!CQl3mcHX2A!SukSJncW_zxJ6rP2RRtkvZx4vMB5
> nmTdIAVxCxr_3Y1nxdUZAMnKnxHxIgSptQSIlJxLi6U$
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] [EXTERNAL] Re: BIMI

[Brotman, Alexander via mailop]

> -Original Message-
> From: mailop  On Behalf Of Patrick Ben
> Koetter via mailop
> Sent: Friday, December 6, 2019 5:02 AM
> To: mailop@mailop.org
> Subject: [EXTERNAL] Re: [mailop] BIMI
>
>
> - It brings more advertising to your inbox.
>
> - It establishes a payment mechanism for receivers, which they can exert on
>   email marketing companies and their customers. "We will not display your
>   company logo in the (web)mail client unless you pay us money."
>
[Brotman, Alexander]

None of the Mail Box Providers involved (thus far) have suggested either of the 
two last items above as a driver.

>
> p@rick
>
> --
> [*] sys4 AG
>
> https://urldefense.com/v3/__https://sys4.de__;!rx_L75ITgOQ!VOKTQy9lMAe
> hO RIQBGmWBwiHvcSNnF70f-o-XzDoyDukxKMAMS1fRbICKxrzInVyitGbBAs$ , +49
> (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München
>
> Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
> Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
> Aufsichtsratsvorsitzender: Florian Kirstein
>
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://urldefense.com/v3/__https://chilli.nosignal.org/cgi-
> bin/mailman/listinfo/mailop__;!rx_L75ITgOQ!VOKTQy9lMAehORIQBGmWBwiH
> vcSNnF70f-o-XzDoyDukxKMAMS1fRbICKxrzInVy_oGVXLo$
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] [EXTERNAL] Comcast.net contact ? Unusually high amount of email being deferred.

[Brotman, Alexander via mailop]

All,  generally speaking, you can reach us at 
delivery-supp...@cable.comcast.com 
That goes to a number of engineers, some operational folks, and I think a 
manager or two.  It has pretty good visibility.

I've already reached out to Ryan off-list.


--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Ryan Prihoda via mailop
Sent: Monday, December 2, 2019 11:01 AM
To: mailop@mailop.org
Subject: [EXTERNAL] [mailop] Comcast.net contact ? Unusually high amount of 
email being deferred.

Hello all,

I have a problem with one of my email servers sending to comcast.net. Every day 
the mail queue backs up for comcast.net to the point where I have around 1700 
emails in the queue build up over the course of the day then eventually get 
flushed after close to 8 hours in queue. What can I do to help ensure prompt 
delivery ? DKIM and DMARC are already in place as well as being signed up for 
the return path FBL. The reputation for this IP is great. I do not know what 
else I could do so hopefully someone on the list can help me out.

Thanks,

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

Re: [mailop] [EXTERNAL] Comcast postmaster for throttling

[Brotman, Alexander via mailop]

Jan-Philipp,

I’ll respond again off-list.  Generally, folks can use 
delivery-supp...@cable.comcast.com 
for issues with “comcast.net” (the .com is a different group, but we can help 
reach out if needed).

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Jan-Philipp Benecke via 
mailop
Sent: Monday, November 4, 2019 5:37 AM
To: mailop@mailop.org
Subject: [EXTERNAL] [mailop] Comcast postmaster for throttling


Hey there,

hoping there is someone from comcast on list with whom we can talk about 
throttling.
We tried to reach out to them at postmaster@.

Can someone may contact me off-list to talk about throttling ?
Or does somebody knows someone who can help ?

Thanks a lot.

Have a nice day,
Jan-Philipp
--



Jan-Philipp Benecke
Deliverability Team

Fon: +49 4402 97390-00
E-Mail: j...@cleverreach.com

[Image removed by sender. 
Xing] [Image removed 
by sender. LinkedIn] 

CleverReach GmbH & Co. KG
HRA 4020 Oldenburg (Oldb.)
cleverreach.de

[Image removed by sender. CleverReach®]


Vertreten durch: CleverReach Verwaltungs GmbH, HRB 210079 Oldenburg (Oldb.)
//CRASH Building | Schafjückenweg 2 | 26180 Rastede | Germany
Geschäftsführung: Jens Klibingat & Sebastian Schwarz
Aufsichtsrat: Rolf Hilchner & Heinz-Wilhelm Bogena

[Image removed by sender. PUSH///] [Image 
removed by sender. CleverReach®]   [Image 
removed by sender. CleverReach @Instagram] 
  [Image removed by sender. 
https://twitter.com/cleverreach]   [Image 
removed by sender. CleverReach @YouTube] 


[Image removed by sender. Aktuell können Sie einige Informationen nicht 
   sehen.Bitte aktivieren Sie externe Inhalte, um die   
 Mail vollständig angezeigt zu bekommen oder klickenSie 
hier.]

[Image removed by sender.]
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

[mailop] Comcast - MTA-STS Outbound

[Brotman, Alexander via mailop]

As of this morning, we've completed the deployment of MTA-STS on our outbound 
systems.  If you believe this is impacting delivery to your systems, please let 
me know.  We'll incorporate the resulting data into our TLSRPT reports shortly 
(along with the already existing DANE-related information).

If I get some time in the near future, I'll see if I can create a readout of 
DANE/MTA-STS and how/where it's benefiting delivery (if that would be of 
interest to folks).

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast


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

Re: [mailop] Resolving issues for several yahoo domains?

[Brotman, Alexander via mailop]

That’s changed over the years, and depends on using IPv4/IPv6 and a few other 
details.  There are also a few layers of control to make things more 
complicated.  I would imagine most ISPs are like this, hence it seems like it 
would be easier to try to manage the number of messages per session than the 
number of sessions.  Obviously I’m not on the ESP side so maybe I just don’t 
understand all the craziness other ISPs impose on senders that makes this a 
difficult thing to configure.

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: Howard F. Cunningham 
Sent: Thursday, September 5, 2019 11:52 AM
To: Brotman, Alexander 
Cc: mailop@mailop.org
Subject: [EXTERNAL] RE: [mailop] Resolving issues for several yahoo domains?

Alex

How many connections does Comcast allow from a single source before Comcast 
either starts limiting connections or outright blocks all connections from that 
IP address?

hc


Howard Cunningham, MCP
howa...@macrollc.com<mailto:howa...@macrollc.com> - personal
For technical support, send an email to 
serv...@macrollc.com<mailto:serv...@macrollc.com> or call 703-359-9211 (24/7)

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Brotman, Alexander 
via mailop
Sent: Thursday, September 05, 2019 11:31 AM
To: '(mailop@mailop.org<mailto:mailop@mailop.org>)'
Subject: Re: [mailop] Resolving issues for several yahoo domains?

One of the interesting things I’ve learned while interacting with ESPs is that 
some of them will artificially restrict the number of messages per session, in 
lieu of opening more sessions. Some of them have told me the values are in the 
low single digits. I’ve kind of wondered the rationale for that might be. Is it 
the idea that you want to get your messages through as quickly as possible?

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop mailto:mailop-boun...@mailop.org>> On 
Behalf Of Benjamin BILLON via mailop
Sent: Thursday, September 5, 2019 10:08 AM
To: mailop@mailop.org<mailto:mailop@mailop.org>
Subject: [EXTERNAL] Re: [mailop] Resolving issues for several yahoo domains?

> Hate to imagine how much mail is currently trying to get into Yahoo and AOL
Same. Hate also to imagine the day (and night?) of the folks working on fixing 
that.

--
Benjamin

From: Dave Holmes 
https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:d...@instiller.co.uk>>
Sent: jeudi 5 septembre 2019 15:57
To: Benjamin BILLON 
https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:bbil...@splio.com>>
Cc: 
mailop@mailop.org<https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:mailop@mailop.org>
Subject: Re: [mailop] Resolving issues for several yahoo domains?

Not the quickest or easiest to do as a lot of senders will have different 
limits on different IP pools depending on reputation / previous throughput.

I've dropped in a platform wide rule to back off the mail queues when the 
response is encountered - should do the Job.

Hate to imagine how much mail is currently trying to get into Yahoo and AOL

On Thu, 5 Sep 2019 at 14:39, Benjamin BILLON via mailop 
https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:mailop@mailop.org>>
 wrote:
Yes, everyone.
Some, very few, emails are accepted. I believe their servers are overloaded. I 
suggest everyone to back off a bit, for instance by limiting the number of 
concurrent connections per outbound IP to ... 1. Until it gets better.
Forcing our way through is not gonna work, or help.

The DNS issue seems solved now.

--
Benjamin

From: mailop 
https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:mailop-boun...@mailop.org>>
 On Behalf Of Dave Holmes via mailop
Sent: jeudi 5 septembre 2019 15:21
To: Ewald Kessler | Webpower 
https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:ewald.kess...@webpower.nl>>
Cc: mailop 
https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:mailop@mailop.org>>
Subject: Re: [mailop] Resolving issues for several yahoo domains?

Were seeing large mail queues forming on our side but I think this extends 
beyond the DNS I've not come across this message from Yahoo before.

Error: "421 Service not available, closing transmission channel tnmpmscs"

So whilst we have the DNS resolution (possibly cached) they are dropping 
connections all over the place, same goes for all of their other domains.

Anyone else with issues delivering after DNS resolves


On Thu, 5 Sep 2019 at 10:31, Ewald Kessler | Webpower via mailop 
https://r.xdref.com/?id=x85Facni004272=mailop-boun...@mailop.org=howa...@macrollc.com=mailto:mailop@mailop.org>>
 wrote:
Yes, Oath (a.o. Yahoo, AOL) is having serious issue

Re: [mailop] Resolving issues for several yahoo domains?

[Brotman, Alexander via mailop]

One of the interesting things I’ve learned while interacting with ESPs is that 
some of them will artificially restrict the number of messages per session, in 
lieu of opening more sessions. Some of them have told me the values are in the 
low single digits. I’ve kind of wondered the rationale for that might be. Is it 
the idea that you want to get your messages through as quickly as possible?

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Benjamin BILLON via mailop
Sent: Thursday, September 5, 2019 10:08 AM
To: mailop@mailop.org
Subject: [EXTERNAL] Re: [mailop] Resolving issues for several yahoo domains?

> Hate to imagine how much mail is currently trying to get into Yahoo and AOL
Same. Hate also to imagine the day (and night?) of the folks working on fixing 
that.

--
Benjamin

From: Dave Holmes mailto:d...@instiller.co.uk>>
Sent: jeudi 5 septembre 2019 15:57
To: Benjamin BILLON mailto:bbil...@splio.com>>
Cc: mailop@mailop.org
Subject: Re: [mailop] Resolving issues for several yahoo domains?

Not the quickest or easiest to do as a lot of senders will have different 
limits on different IP pools depending on reputation / previous throughput.

I've dropped in a platform wide rule to back off the mail queues when the 
response is encountered - should do the Job.

Hate to imagine how much mail is currently trying to get into Yahoo and AOL

On Thu, 5 Sep 2019 at 14:39, Benjamin BILLON via mailop 
mailto:mailop@mailop.org>> wrote:
Yes, everyone.
Some, very few, emails are accepted. I believe their servers are overloaded. I 
suggest everyone to back off a bit, for instance by limiting the number of 
concurrent connections per outbound IP to ... 1. Until it gets better.
Forcing our way through is not gonna work, or help.

The DNS issue seems solved now.

--
Benjamin

From: mailop mailto:mailop-boun...@mailop.org>> On 
Behalf Of Dave Holmes via mailop
Sent: jeudi 5 septembre 2019 15:21
To: Ewald Kessler | Webpower 
mailto:ewald.kess...@webpower.nl>>
Cc: mailop mailto:mailop@mailop.org>>
Subject: Re: [mailop] Resolving issues for several yahoo domains?

Were seeing large mail queues forming on our side but I think this extends 
beyond the DNS I've not come across this message from Yahoo before.

Error: "421 Service not available, closing transmission channel tnmpmscs"

So whilst we have the DNS resolution (possibly cached) they are dropping 
connections all over the place, same goes for all of their other domains.

Anyone else with issues delivering after DNS resolves


On Thu, 5 Sep 2019 at 10:31, Ewald Kessler | Webpower via mailop 
mailto:mailop@mailop.org>> wrote:
Yes, Oath (a.o. Yahoo, AOL) is having serious issues. Their engineers are 
working to resolve the issues.

Regards,
Ewald

On Thu, 5 Sep 2019 at 10:35, tobisworld--- via mailop 
mailto:mailop@mailop.org>> wrote:
We're currently seeing several yahoo domains (ex yahoo.de) 
cannot be
resolved any more in DNS. All the responsable nameservers for that
domain do not reply anymore. Only ns4.yahoo.com replies 
from time to
time for yahoo.de but according to glue record 
ns4.yahoo.com is not in
charge for yahoo.de anymore.

anyone else seeing such problems with yahoo?

--
Cheers

tobi

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


--
Deliverability & Abuse Management, 
www.webpower-group.com
ewald.kess...@webpower.nl
t: +31 342 423 262
li: www.linkedin.com/in/ewaldkessler
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


--


[Image removed by sender. Instiller Logo]



Dave Holmes

Technical Director



d...@instiller.co.uk

T 0333 939 0013  |  M 07966 013 309

1 Park Farm Barns | Packington Lane | Stonebridge | CV7 7TL







Instiller is a trademark of Instiller Limited, registered in England 5053657.



This email contains proprietary information, some of which may be legally 
privileged. It is for the intended recipient only.
If an addressing or transmission in error has misdirected this email, please 
notify the author by replying to this email.
If you are not the intended recipient, you must not use, disclose, distribute, 
copy, print or rely on this email.



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


--


[Image removed by sender. Instiller Logo]



Dave Holmes

Technical Director

Re: [mailop] [EXTERNAL] Comcast contact?

[Brotman, Alexander via mailop]

Brett, I can take a look at this.  Is that the only IP?

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Brett Schenker via mailop
Sent: Tuesday, August 13, 2019 12:18 PM
To: Aaron C. de Bruyn via mailop 
Subject: [EXTERNAL] [mailop] Comcast contact?

We're warming up some IPs and one we're getting the response below but there's 
no Zen listing (which is what the error code indicates). So was hoping to chat 
with someone to figure out what may be the cause of this and get it resolved.


1565711881@BD/30-27744-70ED25D5@BD/30-27744-70ED25D5@66/AA-27744-25D5@p...@comcast.net@0@mailoutgroup009@mailout933@12@0@1.00@68.87.20.5@554
 resimta-ch2-05v.sys.comcast.net 
resimta-ch2-05v.sys.comcast.net 
192.133.16.43 found on one or more DNSBLs, see 
http://postmaster.comcast.net/smtp-error-codes.php#BL01

[root@ASV11MTAM001 ~]# date -d@1565711881

Tue Aug 13 11:58:01 EDT 2019

--
Brett Schenker
Man of Many Things, Including
5B Consulting - 
http://www.5bconsulting.com
Graphic Policy - 
http://www.graphicpolicy.com

Twitter - http://twitter.com/bhschenker
LinkedIn - http://www.linkedin.com/in/brettschenker
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

[mailop] NameCheap Contact

[Brotman, Alexander via mailop]

Anyone have a contact at NameCheap that they'd be willing to share?  Thank you

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast


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

[mailop] ConvertKit

[Brotman, Alexander]

Does anyone have a contact at this ESP that they'd be willing to share? (beyond 
support@)  

Thank you

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast


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

Re: [mailop] [EXTERNAL] Re: charter.net contact

[Brotman, Alexander]

I had already forwarded this to folks at Charter, and they said they'd been 
able to contact Marc.  Sorry, should have confirmed back here.

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

> -Original Message-
> From: mailop  On Behalf Of Anne P. Mitchell,
> Esq.
> Sent: Saturday, March 16, 2019 12:01 AM
> To: Marc Bradshaw ; Marc Bradshaw via mailop
> 
> Subject: [EXTERNAL] Re: [mailop] charter.net contact
> 
> Hi Marc,
> 
> We can probably help you with that if you haven't already found a contact.
> 
> Anne
> 
> Anne P. Mitchell,
> Attorney at Law
> CEO/President,
> SuretyMail Email Reputation Certification and Inbox Delivery Assistance GDPR,
> CCPA (CA) & CCDPA (CO) Compliance Consulting http://www.SuretyMail.com/
> https://protect2.fireeye.com/url?k=df8fbaadd26bc0ae.df8f9d19-
> 5f53d0fb0abc21a1=http://www.SuretyMail.eu/
> 
> Attorney at Law / Legislative Consultant
> Author: Section 6 of the CAN-SPAM Act of 2003 (the Federal anti-spam law)
> Author: The Email Deliverability Handbook Board Member, Board of Directors,
> Denver Internet Exchange Board Member, Board of Directors, Asilomar
> Microcomputer Workshop Legal Counsel: The CyberGreen Institute Legal
> Counsel: The Earth Law Center Ret. Professor of Law, Lincoln Law School of San
> Jose
> 
> 
> > On Mar 14, 2019, at 6:33 PM, Marc Bradshaw via mailop
>  wrote:
> >
> > Hi,
> >
> > I'm looking for a contact at charter.net to talk about a deliverability 
> > issue we
> are having with forwarded mail.
> > If you are such a person (or know of one) could you please contact me off 
> > list
> via the fastmailteam.com address in my signature.
> > Thanks.
> >
> > --
> >
> >   Marc Bradshaw - Deliverability/Abuse at FastMail
> >   m...@fastmailteam.com | @marcbradshaw
> >
> >
> > ___
> > 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 mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] CenturyLink Contact

[Brotman, Alexander]

I forwarded this to a contact at CenturyLink who has gotten in contact with 
Michael.

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Michael E. Weisel
Sent: Monday, February 4, 2019 5:35 PM
To: mailop@mailop.org
Subject: [EXTERNAL] [mailop] CenturyLink Contact

Anyone on the Mailop list work for or with CenturyLink?  If so, please message 
me off list.


Thanks,

Michael

Michael E. Weisel
CTO / Deliverability Lead
Gold Lasso
25 Chestnut Street, Suite B
Gaithersburg, MD 20877
(301) 990-9857 Corporate
(240) 252-5267 Direct Dial

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

Re: [mailop] [EXTERNAL] Re: Comcast Contact

[Brotman, Alexander]

Rob,

The distro Anthony provided should be fine for comcast.net recipients.  I’ll 
respond once it gets there.

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: mailop  On Behalf Of Anthony Chiulli
Sent: Wednesday, January 30, 2019 4:14 PM
To: Rob Heilman 
Cc: Mailop List 
Subject: [EXTERNAL] Re: [mailop] Comcast Contact

delivery-supp...@cable.comcast.com, 
monitored by postmaster team

- Anthony Chiulli



On Wed, Jan 30, 2019 at 2:12 PM Rob Heilman via mailop 
mailto:mailop@mailop.org>> wrote:
Is anyone from Comcast on this list or does anyone have a good contact for 
email admins there?  Looking to troubleshoot end users messages that are being 
delivered to their MTAs but never arrive in the recipients’ mailboxes.

-Rob Heilman




___
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] Business justification for DNSSEC?

[Brotman, Alexander]

OPENPGPKEY and SMIME/A also use DNSSEC, if you're interested in those 
protections for your users.

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


> -Original Message-
> From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Jesse
> Thompson via mailop
> Sent: Monday, October 15, 2018 6:18 PM
> To: mailop@mailop.org
> Subject: [EXTERNAL] [mailop] Business justification for DNSSEC?
> 
> Is there a good summary of current and emerging email technologies that
> depend on DNSSEC that can be referenced for building a business
> justification for prioritizing DNSSEC within an organization?
> 
> From my knowledge/understanding (Disclaimer: I might be wrong) the list is:
> 1) SMTP Security via Opportunistic DANE TLS
> 2) Require TLS Option
> 3) Inter-domain SMTP with TLSA - MX lookup checks, SMTP server checks
> 
> Technologies that are explicitly working around the lack of DNSSEC:
> 4) MTA-STS
> 5) STARTTLS Everywhere
> 
> Thanks,
> Jesse Thompson
> University of Wisconsin-Madison
> ___
> 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] [EXTERNAL] Comcast contact? bounce.care.comcast.com

[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

Re: [mailop] [EXTERNAL] Re: Disabling TLS1.0 for SMTP

[Brotman, Alexander]

If someone is interested, we could potentially ask Binu if he has newer data 
available.  He had done a presentation on the same data at M3AAWG a few years 
ago.

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


-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Rohan Sheth
Sent: Tuesday, May 22, 2018 11:06 AM
To: mailop@mailop.org
Subject: [EXTERNAL] Re: [mailop] Disabling TLS1.0 for SMTP

On Tue, May 22, 2018, at 7:47 AM, Al Iverson wrote:
> Are folks disabling TLS1.0 support in SMTP? Our security team has 
> asked, but I'm a bit concerned about potential failure cases when 
> trying to deliver mail to smaller corporate sites that might be doing 
> stuff like requiring TLS but supporting 1.0 onlyis that really 
> much of a concern?

Admittedly a few years old (March 2016) but Yahoo shared some data about TLS 
versions they see: 
https://yahoo-security.tumblr.com/post/141495385400/measuring-smtp-starttls-deployment-quality

Scrolling down to the TLS Session section, it seems at the time they still saw 
a large volume of TLS 1.0. I would guess that it hasn't changed enough that it 
is OK to blanket disable TLS 1.0 today. 

-Rohan

___
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] Tutanota Contact

[Brotman, Alexander]

Hello,

I'm looking for a contact from Tutanota.  It would be great if they could 
contact me off-list.  Thanks for any leads.

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



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

Re: [mailop] Quick question on Comcast FBL...

[Brotman, Alexander]

So, this isn't truly my part of the platform, but I can tell you that I've 
heard that in some of these cases the things I've heard.  This seems to mostly 
be related to folks switching to a new email client using IMAP.  The new client 
believes it knows better than your last, and begins to reclassify the mail.  We 
once had a guy hooking up his autmobile to read his email, and the email client 
started to reclassify email.  It would only happen when the auto was near his 
home wifi, which made it that much more confusing to troubleshoot.

I believe that they ignore the messages as they are considered too old.  If 
you're still curious, I can double check on that.

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

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Eric Tykwinski
Sent: Monday, February 26, 2018 11:37 AM
To: mailop@mailop.org
Subject: [mailop] Quick question on Comcast FBL...

Just last week I've noticed a sudden uptick on very old spam notifications.  
(Some dated back to 2010...)
Just wondering if anyone else is seeing the same and if Comcast knows about it.
Doesn't seem to be effecting our deliverability, but guessing maybe they did 
some changes.

Sincerely,

Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300

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

Re: [mailop] TLS support

[Brotman, Alexander]

This is a tad dated, but:

https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43962.pdf



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

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Matt Vernhout
Sent: Friday, February 23, 2018 10:53 PM
To: Michael Storz 
Cc: mailop@mailop.org
Subject: Re: [mailop] TLS support

Check out Google’s transparency report

https://transparencyreport.google.com/safer-email/overview


~
Matt

On Feb 22, 2018, at 13:04, Michael Storz 
> wrote:
Am 2018-02-22 16:40, schrieb David Hofstee:

Hi,
A quick question... Does anyone have numbers on:
- the (volume) percentage of emails sent via TLS (capable mail
servers)
- the (volume) percentage of emails sent via TLS where the receiving
mta has a valid certificate
- the (volume) percentage of emails sent via TLS where the receiving
mta uses a valid certificate and supports DANE
Any answer is appreciated. Yours,
David

Hi David,

These are the numbers from the last seven days. Outbound traffic from the 
Munich Scientific Network (several universities). 2/3 of the traffic goes to 
Google, GMX, WEB.DE, Microsoft and Yahoo. GMX and WEB.DE support DANE (TLSA 
records).

TypeMTAs   Connections

Untrusted   3.7752,05 %
No TLS  3.2782,36 %
Anonymous   3.5344,62 %
DANE  157   23,91 %
Trusted14.428   67,04 %
---
  25.172   99,98 %

Michael

___
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] Extreme amounts of SMTP auth from microsoft/outlook IPs

[Brotman, Alexander]

Not sure if I'd call it extreme, but a marked increase beginning Feb 6th.  

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


-Original Message-
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Dan Malm
Sent: Friday, February 09, 2018 3:57 AM
To: mailop@mailop.org
Subject: [mailop] Extreme amounts of SMTP auth from microsoft/outlook IPs

Hi

I'm seeing an extreme amount of SMTP authentications (over 600/s) from the 
microsoft owned 40.101.0.0/16 range on my customer SMTP servers.
It's just auth, with valid credentials, and then it disconnects right after so 
no attempts to send any mails have been done for the vast majority of these 
connections. A small amount of valid mails are being sent from this range 
though. HELO indicates it's from outlook.com. So seems like their system for 
sending with your own domain through external servers has gone a bit haywire...

I've sent ab...@microsoft.com a mail about it, but I'm a bit curious if anyone 
else is seeing the same?

--
BR/Mvh. Dan Malm, Systems Engineer, One.com

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

Re: [mailop] Comcast Feedback Loop emails that look legitimate

[Brotman, Alexander]

Tim,

Yes-ish.  We do treat the action of moving a message to the spam folder the 
same as clicking the "Spam" button.  This is fairly common.  It can make for 
mistakes if someone is dragging a message and accidentally drops the message in 
the wrong place.  We've seen instances where someone attempts a bulk move and 
accidentally files hundreds of messages into Spam, and a few minutes later 
refiles them elsewhere.  Another type of incident we've seen is sometimes a 
user has switched clients and the new client decides that messages previously 
in the Inbox are now spam, and refiles them to the Spam folder.  This could 
also generate a spam report in certain scenarios.

And I'm sure we've all seen that users can (and do) treat the "Spam" button as 
delete.

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

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of 
timrutherf...@c4.net
Sent: Tuesday, November 07, 2017 10:28 AM
To: mailop@mailop.org
Subject: [mailop] Comcast Feedback Loop emails that look legitimate

Hello all,

We are on the Comcast FBL and occasionally get abuse reports from Comcast 
through that service.  It is my understanding that these reports are generated 
automatically when the customer reports an email as spam.

However, we have seen several occasions where the messages are clearly not 
spam.  In some cases they are a reservation confirmations (something the 
customer just purchased), invoices from companies they deal with on a regular 
basis, or even general email correspondences.

I'm wondering if there are any other actions that trigger a spam report and 
consequently a FBL report.   IP reputation, message content, 3rd party 
antivirus actions, etc. ?

The messages come from 
feedbackl...@comcastfbl.senderscore.net,
 which makes me wonder if they have some algorithms in place.

Thanks in advance for any input!
Tim


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

Re: [mailop] Comcast timeouts

[Brotman, Alexander]

There was an issue with some backend systems, which I’ve been told are now 
resolved.  Things are still being cleaned up.

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

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Russell Clemings
Sent: Wednesday, September 20, 2017 2:31 PM
To: mailop@mailop.org
Subject: Re: [mailop] Comcast timeouts

I see nothing but timeouts from those two since 9 a.m. Eastern. Our server is 
in Maryland.



On Wed, Sep 20, 2017 at 11:15 AM, Eric Tykwinski 
> wrote:
I’m seeing a bunch of timeouts on mx1.comcast.net and 
mx2.comcast.net
Tested from office and an OVH server to make sure it’s not regional.
Timeouts are sporadic, so delivery happens after a few tries.

Just want to let someone know if Comcast guys are reading.

Sincerely,

Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300


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



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

[mailop] MySpace Contact

[Brotman, Alexander]

Does anyone have a contact at MySpace?  Attempt to their postmaster address 
resulted in a mail loop bounce.

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



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

[mailop] Southwest Airlines Contact

[Brotman, Alexander]

Anyone have someone at Southwest Airlines that we could contact?This is 
more about transactional than marketing, but I'd be happy to talk to anyone 
within their organization.

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



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

[mailop] Comcast Deliverability Contact (comcast.net)

[Brotman, Alexander]

Hello Folks,

We recently received an escalation to our group via a person that no longer 
works with our group.  This isn't truly a problem, and we understand this may 
happen.  That being said, I wanted to share with others that if you're having 
deliverability issues with "comcast.net" recipients, please use 
delivery-supp...@cable.comcast.com for escalations.  This address will go to 
current group members, as well as our manager.  Thank you.

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



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

Re: [mailop] Anyone experiencing problems sending to Comcast business today?

[Brotman, Alexander]

Tim,

I'll reply offlist and see if I can get some additional information.

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

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of 
timrutherf...@c4.net
Sent: Thursday, December 08, 2016 1:12 PM
To: mailop@mailop.org
Subject: [mailop] Anyone experiencing problems sending to Comcast business 
today?

A test from DNSSTUFF shows intermittent timeouts against mx03.biz.comcast.net / 
mx01.biz.comcast.net (both resolve to same IP : 96.114.157.83)

96.114.157.83 | failed message send with: failed cx open with: failed socket 
connect with: Operation now in progress Note: feature such as sendmail's 
greet_pause can cause the timeout.

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

Re: [mailop] Comcast FBL - Erroneous Reports

[Brotman, Alexander]

Justin,

We’d already seen the issue and the short-term fix has been rolled out.  We’re 
taking a look at longer-term solutions.  Thanks for the heads-up.

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

From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Justin Frechette
Sent: Tuesday, November 29, 2016 11:10 AM
To: mailop@mailop.org
Subject: [mailop] Comcast FBL - Erroneous Reports

Wondering if there is someone from Comcast that can provide assistance or if 
anyone can shed some light on what's going on here.

Our abuse inbox is getting hit with Comcast FBL reports that reference our IPs 
but for mail that is not ours. The mail that is being reported as spam also 
looks very benign and personal, so I'm hesitant to say it's header spoofing. 
We're seeing this with multiple IPs of ours and only with Comcast.

Comcast FBL Email:
This is a Comcast email abuse report for an email message received from IP 
216.27.86.171 on Mon, 28 Nov 2016 14:28:35 +

The IP mentioned above is ours but the message did not originate from us.

The email that is being reported as spam is screenshot here: 
http://screencast.com/t/9r86n18j2

The full headers of the message being reported as spam is pastebin here: 
http://pastebin.com/Hicx0gvM

What is concerning to me is that the IP (216.27.86.171) which has a hostname of 
drone114.ral.icpbounce.com is being reported 
as coming from Comcast. (highlighted below)

Return-Path: >
Delivered-To: et.chialas...@comcast.net
Received: from 
dovdir1-asb-03o.email.comcast.net 
([216.27.86.171]) by
  dovback1-asb-20o.email.comcast.net 
(Dovecot) with LMTP id
  /NuGBBQ/PFjrJgAA2Etxvw for 
>; Mon, 28 Nov 2016
  14:28:36 +
Received: from dovpxy-hob-09o ([216.27.86.171]) by
  dovdir1-asb-03o.email.comcast.net 
(Dovecot) with LMTP id
  e8/zKBM/PFh7RwAApm0j0w ; Mon, 28 Nov 2016 14:28:36 +
Received: from 
resimta-ch2-03v.sys.comcast.net 
([216.27.86.171]) by
  dovpxy-hob-09o (Dovecot) with LMTP id GE1kNhI/PFisfQAAwfAatg ; Mon, 28 Nov
  2016 14:28:35 +
Received: from mail-qt0-x241.google.com 
([IPv6:2607:f8b0:400d:c0d::241]) by
  resimta-ch2-03v.sys.comcast.net with 
SMTP id BMuQc3WdRiOyDBMv1cuFsj; Mon, 28
  Nov 2016 14:28:34 +

We are getting a handful of these reports a day from Comcast and I can't figure 
out what's going on.

Thanks in advance for the help!

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

[mailop] SBA.gov Contact

[Brotman, Alexander]

We're seeing an issue with delivering to sba.gov.  The DNS servers we reference 
from these MTAs are showing SERVFAIL for a PTR lookup on 165.110.5.75.  

http://dnsviz.net/d/75.5.110.165.in-addr.arpa/dnssec/

seems to imply they're having a DNSSEC issue (unless I'm misinterpreting the 
output).  Thanks

--
Alex Brotman
Engineer, Anti-Abuse
Comcast
x5364



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