Live data from Hacker News

Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

mailgun.com

21–30 of 279 posts

Re: Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

#21

Earlier quoted context omitted.

Wouldn't it be based on send volume from your domain, and not send volume via your sending IP / smarthost?

Usually when talking about spam filtering it's based on sending IP and not domain names (domains are still important, but IP addresses are usually the first thing that is being evaluated), although admittedly Google is vague on what constitutes "5,000 mails per day".

The linked article points to blog.google which points to this support article https://support.google.com/mail/answer/81126 which then finally points to this article: https://support.google.com/a/answer/14229414

> What is a bulk sender?

> A bulk sender is any email sender that sends close to 5,000 or more messages to personal Gmail accounts within a 24-hour period. Messages sent from the same primary domain count toward the 5,000 limit.

> Sending domains: When we calculate the 5,000-message limit, we count all messages sent from the same primary domain. For example, every day you send 2,500 messages from solarmora.com and 2,500 messages from promotions.solarmora.com to personal Gmail accounts. You’re considered a bulk sender because all 5,000 messages were sent from the same primary domain: solarmora.com. Learn about domain name basics.

> Senders who meet the above criteria at least once are permanently considered bulk senders.

IMO this is better since they have to handle all of the personal domains and small communities that send from a SMTP service like Sendgrid or Amazon SES. Relying on IPv4s to not be shared wouldn't work universally.

Re: Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

#22
post #15

Earlier quoted context omitted.

Indeed, self-hosted email is commonly rejected despite doing all these things. Google et al have successfully turned email into the domain of a few SaaS, and at half of them blatant spammers can message millions with no record of consent with the most obvious scams and have it delivered into the inbox. Hell, most spam these days I get from hacked Gmail accounts. The game is rigged, as they say.

I often see this repeated, but in my experience self-hosted email works just fine as long as your IP has a good reputation, and isn't on some crappy bulk VPS.

[deleted]

Re: Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

#24
A fairly big deal is being made of this, but dmarc has been a signal for a long time and there's a good chance half your mail has been randomly landing in junk folders if you don't have it setup right. This may actually help people by making them realise that.

Re: Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

#25
DKIM, SPF, and DMARC are old hat and implemented by anyone serious for years. What's buried in this article is the required https://datatracker.ietf.org/doc/html/rfc8058 support for one-click unsubscribe posts. I don't see many messages in my inbox yet with that.

Re: Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

#26

DKIM, SPF, and DMARC are old hat and implemented by anyone serious for years. What's buried in this article is the required https://datatracker.ietf.org/doc/html/rfc8058 support for one-click unsubscribe posts. I don't see many messages in my inbox yet with that.

That's very odd to me. Where are you located? I'm in the United States and virtually all my newsletter/marketing emails have one-click unsubscribe these days. The only ones which don't are from foreign companies, e.g. I bought a day planner from Hobonichi and found they put their unsubscribe behind a login, to my irritation.

Re: Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

#27

DKIM, SPF, and DMARC are old hat and implemented by anyone serious for years. What's buried in this article is the required https://datatracker.ietf.org/doc/html/rfc8058 support for one-click unsubscribe posts. I don't see many messages in my inbox yet with that.

I understand that the request happens in the background by the MUA at the user's express consent, and the unsubscribe is not allowed to send back any ui/html/whatever to present to the user, but the RFC is missing any information about how a response ought to be handled, HTTP Status code wise? Retry if 400/500? Give user any affirmative or negative response that it succeeded or failed?

Re: Gmail and Yahoo’s 2024 inbox protections and what they mean for email programs

#30

DKIM, SPF, and DMARC are old hat and implemented by anyone serious for years. What's buried in this article is the required https://datatracker.ietf.org/doc/html/rfc8058 support for one-click unsubscribe posts. I don't see many messages in my inbox yet with that.

That's very odd to me. Where are you located? I'm in the United States and virtually all my newsletter/marketing emails have one-click unsubscribe these days. The only ones which don't are from foreign companies, e.g. I bought a day planner from Hobonichi and found they put their unsubscribe behind a login, to my irritation.

Same. Basically everything that comes from a legitimate mailing list/subscription has it. Even stuff I would personally consider spam like political mailing lists have it.

It’s only the worst spam stuff that doesn’t. The obvious scam stuff sent to any email address they can find, containing every language I don’t speak, with lots of bad obfuscation to stop keyword scanners from 2002.

Post reply on HN