Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

    - Original message -From: Rob McEwen Sent by: "mailop" To: mailop@mailop.orgCc:Subject: Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...Date: Fri, Nov 30, 2018 4:32 PM  On 11/30/2018 11:06 AM, Kurt Andersen (b) wr

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

On Sat, 1 Dec 2018 at 01:49, Michael Wise via mailop wrote: > > > /grr… > > Why are all my replies only going to the original author of late? > > > I believe it's the way the mailing list software handles submissions from DMARC enabled domains - it moves the sender address to Reply-To: then puts

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

On Sat, 1 Dec 2018 01:41:24 +, Michael Wise via mailop wrote: > >/grr… >Why are all my replies only going to the original author of late? Given >Reply-To: Michael Wise in the headers, I would classify this as "the expected behaviour". mdr -- Sometimes half-ass is exactly the right

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

8275> ? From: Michael Wise Sent: Friday, November 30, 2018 5:40 PM To: 'Jim Popovitch' Subject: RE: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge... I don't think screaming at that person (or persons) would do much good at this point. And it's not like people have

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

On December 1, 2018 12:22:21 AM UTC, "Kurt Andersen (b)" wrote: >One of about 5 hyphenated *marriott* domains that I have received mail >from over the last year :-P > It's the not unique to Marriott, Prudential does the same..same exact format. I wonder if all these companies were

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

One of about 5 hyphenated *marriott* domains that I have received mail from over the last year :-P --Kurt On Fri, Nov 30, 2018 at 4:03 PM Matt Vernhout wrote: > Email-Marriott.com is their normal sending domain. It has been for years. > > ~ > Matt > > > On Nov 30, 2018, at 17:26, John Levine

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

Email-Marriott.com is their normal sending domain. It has been for years. ~ Matt > On Nov 30, 2018, at 17:26, John Levine wrote: > > In article <903fdf82-15d7-a854-f72f-c780b7fb6...@invaluement.com> you write: >> Anyone with half a brain should be able to figure out that >> "marriott.com"

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

In article <903fdf82-15d7-a854-f72f-c780b7fb6...@invaluement.com> you write: >Anyone with half a brain should be able to figure out that >"marriott.com" has order of magnitudes more "good reputation" than >"email-marriott.com" - so this is just not wise. I get the impression that they are

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

Yeah, watch for all the new domain registrations for look-alike domains, eg emailus-marriott.com, with 'Links back to our Site' , world needs to make it easier for the one-time use email addresses when registering information on line for the general public, eg the -dash notation. But what is

Re: [mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

On 11/30/2018 11:06 AM, Kurt Andersen (b) wrote: Sadly, they are using a cousin domain for the mailing starwoodhot...@email-marriott.com I'll add to this -  that from the perspective of someone who manages an anti-spam blacklist - use of

[mailop] Fwd: Looks like we'll be seeing a big breach notification surge...

https://news.marriott.com/2018/11/marriott-announces-starwood-guest-reservation-database-security-incident/ Sadly, they are using a cousin domain for the mailing (according to their FAQ "How will I know that the email notification I receive is from Marriott?"): We want you to be confident that