@sir

Resistant only in a very narrow sense. Try delivering to more than about a dozen addresses. More than half will be on gmail (ugh), and you will not reach them. Or if you do once, then maybe not next time. You'll never know why.

Google has done a great job re-centralizing the email architecture. You and I care, but a shockingly large number of people who should know better--don't.

@vandys I don't know why people always talk shit about gmail for deliverability

I haven't had issues delivering to gmail accounts across 5 different mail servers in the past 5 years

@sir @vandys Not all people have their own physical server colocated in a datacenter with probably an individual ip range...

Those of us who are on the standard vps ranges may already get a penalty just because it's a vps provider's range.

At least I certainly know that stuff from my server gets put into spam for some gmail users even after having communicated with them directly before for no particular reason. SPF / dkim etc all setup, not on any blocklist etc

@reto @vandys several of those servers have been on VPSes. Almost every IP on the internet has a bad reputation, but blocklists have automated and easy ways to get unlisted.

@reto
I work with SMTP and spam filtering (among other things) for a multinational corporation. I also run my own email infrastructure.
If your email ends upon the spam folder then the usual reason is that the email you send is impossible to distinguish from spam. I know that sounds like I'm blaming you but that's not what I meant.
Sometimes we accidentally write stuff that in composition looks like a known spam message.
@sir @vandys
@qrsbrwn @sir @vandys yeah. No.

it was an answer to a patch, citing portions of code with no links inside and no html part.

No spam looks like that
@reto
Hahahaha you clearly don't work much with spam. So yeah, looks like spam and/or malicious email to most spam filters.

@sir @vandys

@sir My comments come from my own, personal experience. Flaky for personal delivery, and absolutely useless for bulk delivery. Thus mailchimp and friends.

@sir In case sourcehut gets a DMCA, does it remove only the git repository, or also disable the mailing list?

@sir
> but it’s entirely possible that we wouldn’t even have to shut off the mailing list when dealing with this situation.

I guess that's not known yet whether it's necessary.

@tomleb it would depend on the scope of the DMCA request. We'd only disable what was explicitly mentioned in the request

@sir Really enjoyed the video at the end there too, going to try the email workflow.

@sir Mailing lists are an improvement over Github's PRs but they aren't so easy to replicate as git repos (does sr.ht have import from mbox/Maildir?).

As far as I know sr.ht's bugtracker has the same exact problem like Github's one - it's centralized unlike mailing lists.

@Musectimptur @sir aren't bug trackers like sticky notes? The advantage being that if you throw them away you don't have to do it until it's written down again?

@sir oh nice, an awesome blogpost. Time to give it a read.
Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!