Gmail is a huge source of spam February 25, 2021 on Drew DeVault's blog

5× as many spam registrations on sourcehut are from gmail than from the second-largest offender.

  SPLIT_PART(email, '@', 2) as domain, count(*) as count
  FROM "user"
  WHERE user_type = 'suspended'
  GROUP BY domain
  ORDER BY count DESC;
          domain           | count
---------------------------+-------                 |   119                    |    26                   |    17            |    10               |     6                   |     6                 |     6
[...more omitted...]

This is just the ones which got through: most spam registrations are detected and ignored before they make it to the database.

A huge number of spam emails I recieve in my personal inbox originate from, and often they arrive in my inbox unscathed (as opposed to going to Junk) because Gmail is considered a reputable mail provider. My colleague estimates that between 15% and 25% of the spam emails sent to a mailing list he administrates comes from Gmail.

One might argue that, because Gmail is the world’s largest email provider, it’s natural to expect that they would have the largest volume of spam simply because they have proportionally more users who might use it for spam. I would argue that this instead tells us that they have the largest responsibility to curtail spam on their platform.

I’ve forwarded many, many reports to, but they’ve never followed up and the problem has not become any better. I have had half a mind to block Gmail registrations on sourcehut outright, but about 41% of all registrations use Gmail.

It bears repeating that anyone with any level of technical expertise ought to know better than to use Gmail. I usually recommend Migadu1, but there are many options to choose from. If you’re worried about mail deliverability issues, don’t be — it’s more or less a myth in $CURRENTYEAR. If you set up DKIM properly and unlist your IP address from the DNSBLs (a simple process), then your mails will get through.

In case you’re wondering, the dis-award for second-worst goes to Amazon SES. They don’t register on sourcehut (it’s outgoing only, so that makes sense), but I see them often in my personal inbox. However, SES only appears at a rate of about a tenth of the gmail spam, and they appear to actually listen to my abuse reports, so I can more or less forgive them for it.

  1. Full disclosure: sourcehut has a business relationship with Migadu, though I’ve recommended them since long before we met. ↩︎

Have a comment on one of my posts? Start a discussion in my public inbox by sending an email to ~sircmpwn/ [mailing list etiquette]

Articles from blogs I read Generated by openring

Share your feedback about developing with Go

Help shape the future of Go by sharing your thoughts via the Go Developer Survey

via The Go Blog January 18, 2023

Status update, January 2023

Hi all! This month’s status update will be lighter than usual: I’ve been on leave for a while at the end of December. To make up for this, I have some big news: we’ve released Sway 1.8! This brings a whole lot of improvements from wlroots 0.16, as well as som…

via emersion January 16, 2023

SourceHut will (not) blacklist the Go module mirror

Update 2023-01-31: Russ Cox of the Go team reached out to us to address this problem. After some discussion, an acceptable plan was worked out. The Go team is working on deploying an update to the “go” tool to add a -reuse flag, which should substantially re…

via Blogs on Sourcehut January 9, 2023