Live data from Hacker News

Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

blog.google

71–80 of 420 posts

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#71
post #24

Earlier quoted context omitted.

Perhaps, but it's hard to say. False positives are much more harmful than false negatives. I have peronally had Gmail flag a number of legit emails as spam, and those are just the ones I know about! It's almost certain that I have lost valuable messages because I didn't check the spam folder in time. These aren't transactional emails either, I'm talking about messages from real people that I know personally. I would…

I'd take the false positives, personally. If someone really needs to reach me and doesn't get to me on the first try, they usually just email or text back and go "Hey, did you get my email?". Or, just quickly skim through the spam folder once a week.

Unless they always get filtered. Which has happened to me before where people wondered why I was ghosting them.

I now skim my spam filter regularly because of this, but not everyone realizes they should do this.

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#72

This might be good news, but as it comes from Google and involves email centralisation, I’m sceptical. At MailPace we already enforce DKIM, it’s pretty basic stuff. But list-unsubscribe is optional for our senders. We can make this a requirement and manage lists for senders who don’t / can’t implement a webhook to handle it (we already default to blocking resends to emails that hard bounce). However I am curious how…

Why would you allow users to unsub from transactional emails?

Because its better than me just sending it to the spam box. Or worse, not interacting with your service.

At this point something as simple as ordering something online means I get 4-7 emails and then some growling "please rate us" shit. And if I am stupid enough to do so, but only rate it 4 our of 5, another "we are sorry, please tell us what we did wrong" email.

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#73
post #8

> "Gmail’s AI-powered defenses stop more than 99.9% of spam, phishing and malware from reaching inboxes and block nearly 15 billion unwanted emails every day." This will be a pain for legit use cases but will net to a better place for the ecosystem. Much like strong KYB/KYC for bulk text messaging.

You joking right? The amount of text messages spam I receive now on Verizon, and some 8 months ago before on T-mobile is staggering.

They're cracking down with "10DLC." Mass SMS senders must identify themselves, pay a fee, and register each campaign including its content.

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#74

Earlier quoted context omitted.

You may not have to comply with CAN SPAM legally, but I absolutely hate when orgs do this. Please try to make the world a better place instead of doing the legal minimum.

What else should I do? The list is double opt-in, every message includes a one-click unsubscribe link, full contact info for the organization is included, and I send text-only.

My reading is that in your comment they replied to, you said you require confirmation for unsubscription.

One click unsubscription is presumably what they want.

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#75

Hijacking the thread: I do some "bulk" sending for a 501(c)3 I volunteer for. I include unsubscribe links that go to a form with a submit button (because I want the unsubscribe to be a POST request). Each link has a random opaque identifier in the query string. Something like: hxxp://example.com/unsubscribe?id=abcd1234 A couple years ago I noticed that MSFT IPs hitting my unsubscribe links with invalid identifiers on…

If you are sending out HTML emails, cant you just make the unsubscribe button a submit button in the form?

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#76
post #75

Hijacking the thread: I do some "bulk" sending for a 501(c)3 I volunteer for. I include unsubscribe links that go to a form with a submit button (because I want the unsubscribe to be a POST request). Each link has a random opaque identifier in the query string. Something like: hxxp://example.com/unsubscribe?id=abcd1234 A couple years ago I noticed that MSFT IPs hitting my unsubscribe links with invalid identifiers on…

If you are sending out HTML emails, cant you just make the unsubscribe button a submit button in the form?

I am sending text-only messages. (I hate HTML email, personally.)

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#77
You mean Yahoo isn't the rotting carcass of the company it once was? I see nothing but decay: their abuse addresses don't work, nor do any of the addresses they have in WHOIS, either for their domains or their networks, that haven't been switched to oath.com. Their SOA isn't real. They've basically stopped accepting abuse complaints.

Is Marcel Becker, supposedly the "Sr. Dir. Product at Yahoo", according to this article, the only person working at Yahoo handling email these days? I'm only half joking - Yahoo is incredibly unresponsive when it comes to abuse.

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#78

Earlier quoted context omitted.

Ironically, most of my breakthrough spam seems to come from @gmail.com addresses...

Same, but that's because all the other hundreds of pages of spam got filtered away already. I wouldn't be surprised if Gmail spam is higher-effort (like those individual SMS spam apps that politicians use) but higher-breakthrough.

I read years ago a hijacked Gmail account was worth $10 on a black market while a Yahoo! Email account was worth $0.10.

Re: Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

#80

Earlier quoted context omitted.

What else should I do? The list is double opt-in, every message includes a one-click unsubscribe link, full contact info for the organization is included, and I send text-only.

My reading is that in your comment they replied to, you said you require confirmation for unsubscription. One click unsubscription is presumably what they want.

I require a button to be clicked to confirm. No entry, no JavaScript, nothing else. Just something to make a POST request because I receive GET requests for almost every URL I send out.

My experience is that every unsubscribe goes to a form w/ a submit button. Shitty ones make you type your email address. (Mine doesn't.)

Post reply on HN