Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gmail, Yahoo announce new 2024 authentication requirements for bulk senders

blog.google

Post reply on HN
Print view View original

121–130 of 420 posts

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

#121

Post by foobazgt »

tornato7 wrote: post #59
teruakohatu wrote: post #3

Most of the spam I get in gmail apparently comes from other gmail accounts. Presumably google already filtered out senders pretending to be gmail, so I am not sure what a big improvement this will be for the average user.

I receive a lot of scam emails from Google Docs - ie random users 'sharing' Google Docs with me that are either ads or viruses or both.

I got one of these once. Google does run spam classifiers for docs and you can report them as spam: https://support.google.com/drive/answer/13305033

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

#122

Post by evangow »

albertgoeswoof wrote: post #62
pirsquare wrote: post #51

Earlier quoted context omitted.

Why would you allow users to unsub from transactional emails?

Because (according to this announcement) if you don't, Google will put you in the spam folder. Edit: I suppose it does say "unsubscribe from commercial email in one click". But it's hard to say exactly what they mean. They also don't define Bulk Senders - is that the domain or the sending SMTP server?

They defined bulk senders in the 3rd paragraph: "bulk senders — those who send more than 5,000 messages to Gmail addresses in one day"

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

#123

Post by iamacyborg »

pirsquare wrote: post #51
albertgoeswoof wrote: post #26

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?

You wouldn’t, if they’re true transactional messages instead of poorly veiled marketing ones.

Think of it the same way Canada’s anti spam law (CASL) works. https://emailkarma.net/2016/09/qa-transactional-emails-unsub...

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

#125

Post by dmitrygr »

pirsquare wrote: post #51
albertgoeswoof wrote: post #26

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?

Perhaps I do not care to receive them? Why does a store allow me to say "no receipt please", but you think your transactional spam needs to reach me?

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

#126

Post by killthebuddha »

If I wanted to learn everything there is to know about email and SMS spam/abuse policies, technical best practices, important standards, etc, what would be a good strategy? It feels like a super important but ridiculously intractable subject.

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

#128

Post by albertgoeswoof »

WirelessGigabit wrote: post #120
albertgoeswoof wrote: post #26

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…

Side-note: for list-unsubscribe, do you determine the subscriber's identity that needs to be unsubscribed based on the sender or the receiver (like @unsubscribe.service.com)? Reason I'm asking is Unsubscribe rarely works for me due to my catch-all not SENDING emails from the address it was received on. It sends it from my actual address. Very annoying.

The RFC https://www.ietf.org/rfc/rfc2369.txt Section 3.2 is not specific on this - but the examples only show the To address, and no unique identifier beyond that, so it might not work out well for you for mailto list-unsubscribes. It also prefers mailto over https.

If we build this as a mandatory feature at MailPace, we'll use an HTTPS webhook with a unique identifier for the email, so if you unsubscribe from a list sent via us, it will work for you.

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

#129

Post by legitster »

overstay8930 wrote: post #17

Doesn't matter to me, if an email doesn't have a one click unsubscribe I just mark it as spam. Messes with their email reputation so they hopefully get kicked off of reputable email services.

Unfortunately for us, the Privacy team at our org has determined that a one-click unsubscribe link in the body of the email is unacceptable (passing an identifier into the URL of the link). So we accept either the client unsubscribe link, or users who click the unsubscribe link in the email have to provide their email address on the unsubscribe page.

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

#130

Post by albertgoeswoof »

evangow wrote: post #122
albertgoeswoof wrote: post #62

Earlier quoted context omitted.

Because (according to this announcement) if you don't, Google will put you in the spam folder. Edit: I suppose it does say "unsubscribe from commercial email in one click". But it's hard to say exactly what they mean. They also don't define Bulk Senders - is that the domain or the sending SMTP server?

They defined bulk senders in the 3rd paragraph: "bulk senders — those who send more than 5,000 messages to Gmail addresses in one day"

> is that the domain or the sending SMTP server?
Post reply on HN