News for hackers. Stuff that matters.
Re:After self-hosting my email for twenty-three years I have... by zahllos on Sunday September 04, 2022 @02:38PM (#32716255)
I'm on 12 years of self hosting email and counting. Once every so often, I do end up being blocked, usually by Outlook and once by Yahoo. I'm in their 'sender program' and they still don't actually bother to contact postmaster@, but a few emails is usually enough to unblock the block within 24h.

Agree with a sibling comment that many major providers fail to operate the SPF/DKIM/DMARC tools they insist you do.

Each to their own, but ultimately if we don't hold on to the freedom to operate our own mailservers, it will be taken away through inaction. This means doing some things right: DMARC, DKIM, SPF of course, server maintenance, good password policies and of course IP reputation. The best way I can recommend for IP reputation is to use a dedicated provider or VPS provider that disallows things like VPN endpoints, where it is less likely they'll assign an address with a poor reputation. A good provider might also ask you what you intend to host, and you might be able to discuss IP addresses with them.

Re:After self-hosting my email for twenty-three years I have... by PinguTS on Sunday September 04, 2022 @03:26PM (#32716767)
I completly agree with you. While Hetzner is my actual neighbor as their headquarters is right in the neighboring town, I still use a server at very small scale provider. I have no problem with my email server. I receive some spam here and there, mostly from Russia. But I immediatly block the according IP addresses for some time.

For years I avoided to use any external service to decide whether its Spam or not. But about 2 years ago I started to rely on some of the external Blocklists.

Till today I have no problem sending Email. Even as I don't use DKIM or DMARC.

Re:After self-hosting my email for twenty-three years I have... by jimmydorry on Sunday September 04, 2022 @08:24PM (#32719138)
If you are using external blocklists, you are perpetuating the problem here. Small mail operators end up on blocklists through no fault of their own, and it sounds like your server would reject them just like the big servers do.
Re:After self-hosting my email for twenty-three years I have... by EvanAnderson on Sunday September 04, 2022 @10:12PM (#32719772)
You don’t have to use blocklists to block messages.

I use blocklists in my self-hosted setup but only for the purpose of adding header fields that my Bayesian anti-spam filter can use to classify messages. I don’t reject anything out-right, aside from attempted spoofs of the domains my server is authoritative for. Everything is received— it just may end up in an “Unsure” folder if it seems too shady for the filter to put in my inbox.

Re:After self-hosting my email for twenty-three years I have... by jimmydorry on Monday September 05, 2022 @12:15AM (#32720435)
That sounds like a better solution and not at all what I would assume someone means when they say that they use blocklists to filter out spam.
Re:After self-hosting my email for twenty-three years I have... by koheripbal on Sunday September 04, 2022 @10:13PM (#32719777)
Not using block lists will inundate mail servers with spam. It's a necessary evil.
Re:After self-hosting my email for twenty-three years I have... by jjav on Monday September 05, 2022 @12:56AM (#32720688)
I don't use any kind of block list on my mail server, as I find the concept to be fundamentally flawed. I accept all incoming email as long as basic sanity on the connection is met and then apply bayesian filtering after the email has been accepted.

I get just about no spam at all (<10 per month, maybe).

Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Monday September 05, 2022 @04:23AM (#32721805)
I use block lists, fail2ban, gray listing, most of rspamd's widgets, and Bayesian filtering. Still getting 10s of spams a day just to my accounts.
Re:After self-hosting my email for twenty-three years I have... by dvdkon on Monday September 05, 2022 @06:43AM (#32722788)
Any guess on why people's experiences with spam are so diverse? I self-host and get fewer than 10 true spam emails per year (not counting marketing newsletters).
Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Monday September 05, 2022 @10:03AM (#32724397)
> Any guess on why people's experiences with spam are so diverse?

That would be an interesting research project. The domains getting most spams on my servers are the ones that are old (20+ years) which I guess makes sense.

Checking the rspamd logs for the last month gives just shy of 8500 emails with what I'd consider "definitely a spam" score. There's probably another 1000-1500 sneaking under that.

Re:After self-hosting my email for twenty-three years I have... by jjav on Tuesday September 06, 2022 @08:42PM (#32745036)
> > Any guess on why people's experiences with spam are so diverse?

> That would be an interesting research project.

Indeed. When you say get spam, do you mean pre or post-filtering?

Over the last 30 days (I don't keep them longer than that) I've received 43 spam emails which were sent to the spam folder (so I wouldn't ever see these, other than because I went and looked now for the sake of this discussion). In the same time period there was only 1 spam email which was missed by spamprobe and made it into my inbox spool.

There's a fair amount of would-be spam that gets blocked during the SMTP transaction due to things like bogus host in HELO, etc. I don't keep any stats on those, I did at one time but it was too much noise.

My email isn't secret, it should be on every spammer list I'd guess. It has been the same since the mid 90s and is all over usenet, email list archives, websites, etc and I've never made any effort to mask it.

Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Wednesday September 07, 2022 @03:40AM (#32747698)
> Indeed. When you say get spam, do you mean pre or post-filtering?

All my numbers are post-rspamd. There's still sieve after that which does the "is it scored more than X?" to redirect into spam/not-spam.

> There's a fair amount of would-be spam that gets blocked during the SMTP transaction

Yeah, the blocklists and protocol strictness rules definitely cut down a lot before it even gets to rspamd.

Re:After self-hosting my email for twenty-three years I have... by t0k0l0sh on Monday September 05, 2022 @10:49AM (#32724922)
You mentioned receiving 10s of spam per day - are they being classified correctly and put in your spam folder or are you seeing them in your inboxes?

My mx hosted with hetzner also runs rspamd. Of the 32k mails received in the last month, 40% were rejected (postfix DISCARD, so the sender sees the mail as accepted but its sent to /dev/null - this only happens to mails scored very highly as spam, or sent to a spam trap address), 10% were greylisted and 1% were delivered to the spam folder.

So I'm also receiving 10s of spam per day, but they're all delivered to my spam folder with rare errors.

With the exception of an issue delivering to AT&T recently, I haven't had any outbound deliverability problems in a few years, but then again I don't send very much mail at all - perhaps I'd have more trouble if I did but most of my mail is incoming.

Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Tuesday September 06, 2022 @05:31AM (#32734820)
> are they being classified correctly and put in your spam folder

Mostly. There's probably 3-5 spams a day which get into my inbox; also 10-15 a day that wrongly end up in the "maybespam" folder (generally bulk that I'm not worried about seeing 100%.)

Re:After self-hosting my email for twenty-three years I have... by unilynx on Monday September 05, 2022 @11:28AM (#32725363)
> That would be an interesting research project. The domains getting most spams on my servers are the ones that are old (20+ years) which I guess makes sense.

The old lists may be more plausible.

Some spammer once associated 'Robin Bennett' with my email addresses at some point 20 years ago and kept reselling it. Never used that name, didn't even know Bennett was a surname. I assume they linked me up with that name to fill up empty cells in their list and make it look more plausible.

It's a good way to filter spam. The last decade almost all spam calling me 'Bennett' is from some US political group, which mostly reminds me that it will be a long time before anything GDPR-like will pass in the US..

But almost all spam goes to that old 20 year old email address I don't use. My current email addresses are much cleaner even after 10+ year of use

Re:After self-hosting my email for twenty-three years I have... by GoblinSlayer on Tuesday September 06, 2022 @05:32AM (#32734829)
I thought self hosting is for aliases? Shouldn't those fix spam for good unless you publish your address globally?
Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Tuesday September 06, 2022 @07:27AM (#32735598)
> I thought self hosting is for aliases? Shouldn't those fix spam for good

Not quite sure I follow? Unless you mean "only allow emails to specific email addresses you've noted down", in which case, yeah, that works but also means a lot of admin when you want to use a new one (plus there's 10+ other people who use my servers for email, not just me.)

> unless you publish your address globally?

At least one of my email addresses has been published globally since ~1995. Others since ~2000.

Re:After self-hosting my email for twenty-three years I have... by GoblinSlayer on Tuesday September 06, 2022 @11:46AM (#32738730)
By lot of admin you mean that it's not automated? That's sad indeed.
Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Tuesday September 06, 2022 @05:47PM (#32743648)
> By lot of admin you mean that it's not automated? That's sad indeed.

How would I automate "[someone with an account] just entered abc-xyz@domain into a web form to subscribe to something, add that to the valid alias file"?

Re:After self-hosting my email for twenty-three years I have... by GoblinSlayer on Wednesday September 07, 2022 @04:34AM (#32748077)
As I understand, spam filters like postscreen are designed as reverse proxies or relay servers. IIRC spamgourmet supports your scenario.
Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Wednesday September 07, 2022 @09:35AM (#32750393)
> IIRC spamgourmet supports your scenario.

Not really - that's a limited use alias. Doesn't really work for when you want to keep getting email from places. Also if I'm reading that correctly, spammers can just send mail to <randomword>.20.<knownaccount>@spamgourmet.com and you can't protect against those 20 spams.

Re:After self-hosting my email for twenty-three years I have... by GoblinSlayer on Monday September 12, 2022 @03:42AM (#32807210)
They can, but reportedly they don't, see FAQ. Also unlimited emails and locked senders are described in FAQ.
Re:After self-hosting my email for twenty-three years I have... by Avamander on Monday September 05, 2022 @06:44AM (#32722806)
You are not a valuable target to spammers. At some point even storing the spam letters makes no financial sense.
Re:After self-hosting my email for twenty-three years I have... by whiplash451 on Monday September 05, 2022 @03:56AM (#32721659)
One spam every three days is insanely high IMO (compared to what you will get on gmail)
Re:After self-hosting my email for twenty-three years I have... by olau on Monday September 05, 2022 @04:42AM (#32721930)
I get > 1 spam per day on gmail.com.

But I don't find that burdensome at all, in fact I'd prefer that gmail let more stuff through to my spam folder instead of swallowing things that it misclassifies, because I have seen several instances of lost legitimate email, something I still don't understand how is deemed acceptable to the people who wrote it.

But I need to vote with my feet instead of complaining.

Re:After self-hosting my email for twenty-three years I have... by jjav on Tuesday September 06, 2022 @08:33PM (#32744956)
> One spam every three days is insanely high IMO (compared to what you will get on gmail)

That's funny since on gmail I get tons more spam than on any of my self-hosted domain addresses. What's worse, I see emails in gmail misfiled as spam when they are not, which is far worse. I don't ever see that happen in my self-hosted system.

Re:After self-hosting my email for twenty-three years I have... by jimmydorry on Monday September 05, 2022 @12:12AM (#32720421)
And for most people, using a large mail provider is the necessary evil. I don't see much difference between a small mail provider using block lists and a large mail provider using the same block lists + their own proprietary lists and metrics.

Both result in other small mail providers getting blocked for arbitrary reasons with limited recourse.

Re:After self-hosting my email for twenty-three years I have... by friendzis on Monday September 05, 2022 @01:37AM (#32720925)
Using large mail provider is not necessary evil in my book. It is just so much more convenient than self hosting. Today, with ready-made containers and stuff we start having a fighting change, but the moat is possibly too big to fight with email falling out of favor
Re:After self-hosting my email for twenty-three years I have... by GTP on Monday September 05, 2022 @03:48AM (#32721609)
I think that gray listing is a great idea to filter out spam. Here's how it works: the very first time an email server get an email from a new IP it answers with a "temporary unavaiable" error. According to specs, a server should retry to deliver the email after a while, so a legitimate server will retry and it's IP will be put in a "withelist" (here in quotes because you can still do further processing of the emails to determine if it's good or bad). But a spammer will most likely not retry to send it, as their goal is to quickly send a big amount of mails. I didn't try this personally as I'm not hosting my own emails (I tried but gave up soon), but I heard it works very well, no third party blocklist needed.
Re:After self-hosting my email for twenty-three years I have... by iggldiggl on Monday September 05, 2022 @05:36AM (#32722275)
The trade off is that even legitimate mail that you are actively expecting (like an account confirmation or password reset mail) will be delayed by however long the sending server's retry interval is.

You also either need to apply the greylisting to some larger IP range (rspamd e.g. apparently uses /19 by default for IPv4) or otherwise specially handle some of the bigger mail providers, because some of them rotate through their servers between retries, so you could be in for a quite a long wait if you do per-individual-IP greylisting.

The biggest culprit I noticed this with was Amazon SES – a former mail provider of mine used per-individual-IP, non-configurable greylisting, and any mail sent through Amazon (which isn't just Amazon itself – quite a few companies are using Amazon SES for transactional mail and suchlike) would consequently almost always arrive several hours late (however randomly long it would take Amazon to finally re-use an IP during a subsequent retry attempt).

Even more infuriating, my mail provider's support would then claim that it wasn't their fault and they didn't know anything about any supposed greylisting.

Re:After self-hosting my email for twenty-three years I have... by grepfru_it on Monday September 05, 2022 @10:57AM (#32725024)
You just solved a random mystery I was having with mail forwarding from a single particular provider.
Re:After self-hosting my email for twenty-three years I have... by zimpenfish on Monday September 05, 2022 @04:22AM (#32721795)
> I heard [gray listing] works very well

Mostly. But then you get the "click the link in the email within 10 minutes" problem. There's also a non-zero number of "our mail didn't get through first attempt, oh well, give up" people. From running GL on my servers over a couple of years, it mildly cut down spam (on top of blocklists and fail2ban) but I'm now wavering over whether it's worth the hassle.

Re:After self-hosting my email for twenty-three years I have... by necovek on Monday September 05, 2022 @05:37AM (#32722279)
It cut spam tremendeously for me, but that's on an email address I've used and published openly since early 2000s.

Still, I've given up on it since plenty of email senders are not standard-abiding (they fail to retry), and I've kept losing email. I only caved in in the last 12 months after 15+ years of doing graylisting.

Re:After self-hosting my email for twenty-three years I have... by PinguTS on Monday September 05, 2022 @05:51AM (#32722393)
I have greylisting enabled for years. But recently some Russian spamers were able to circumvent those by using compliant SMTP servers. They even support proper SPF, DKIM, DMARC and all that stuff what you can think of.

That is the reason why I switched on some external block lists into the mix.

Re:After self-hosting my email for twenty-three years I have... by unilynx on Monday September 05, 2022 @11:21AM (#32725297)
I wonder if anyone compared the effectiveness of postscreen vs greylisting. Can't find any

Both rely on filtering out non compliant senders, but postscreen's filtering might be less disruptive. Are there spammers out there who cannot pass a graylist but can pass postscreen ?

Re:After self-hosting my email for twenty-three years I have... by jgsaau on Monday September 05, 2022 @10:06PM (#32731852)
What we found 20+ years ago when we started to provide a very poor service to attempted spam delivery was that the spammers realised our servers were very 'slow' and stopped the attempts. We used to get 1000s of new IPV4 tuples / day, now we get < 10. If you put the inbound SMTP sessions to sleep this is wrecking the spammers bus. model, they need to deliver 1,000,000,000+ / day. Don't u fell sorry 4 them. The only time we don't tuck them in 4 a snooze is if they are in a 3rd party BL !!!
Re:After self-hosting my email for twenty-three years I have... by Godel_unicode on Monday September 05, 2022 @12:11AM (#32720420)
This is pure victim-blaming. The problem is that bulletproof hosting exists, not that people are sick of spam.
Re:After self-hosting my email for twenty-three years I have... by jimmydorry on Monday September 05, 2022 @12:14AM (#32720429)
I don't follow. I am pointing out that using the same kinds of lists that the big providers use will result in smaller providers being arbitrarily blocked with little recourse. Do you disagree with that assessment?
Re:After self-hosting my email for twenty-three years I have... by Godel_unicode on Monday September 05, 2022 @02:31AM (#32721189)
First, yes. They (the small providers) have recourse, it’s just annoying. They voluntarily signed up for that annoyance because of their ideology.

But much more importantly, that question is orthogonal to my argument. Using blocklists is a good way to cut down on spam, the fact that it might block some trivial percentage of people who for ideological reasons might or might not be on those lists isn’t the receivers problem.

You want this to not be the case? Contribute meaningfully to solving the problem in a more effective way. Don’t blame the people who just don’t want the spam.

Re:After self-hosting my email for twenty-three years I have... by jimmydorry on Monday September 05, 2022 @09:33AM (#32724118)
The small providers typically don't have recourse if they approach a blocklist maintainer and ask to be taken off a list. That "trivial percentage of people" make up a substantial portion of service providers (for every Google there are many <100 user mail servers), which is what this thread was about.

I pointed out that adopting blocklists just makes it harder to operate a mail server as a small provider, and nobody in this thread appears to disagree with that assessment. They instead seem to take issue with the tone of the message.

Re:After self-hosting my email for twenty-three years I have... by jasode on Monday September 05, 2022 @10:36AM (#32724769)
>The small providers typically don't have recourse if they approach a blocklist maintainer and ask to be taken off a list. [...] I pointed out that adopting blocklists just makes it harder to operate a mail server as a small provider, and nobody in this thread appears to disagree with that assessment. They instead seem to take issue with the tone of the message.

I don't think it's the tone. While the inability for senders to get off blocklists can be true, you're still not addressing why the cost to the sender to not be blocked should have higher priority than the cost to the receiver to avoid blocklists to make email admin more of a burden.

The gp you first replied to (PinguTS) is running a personal mailserver and resorted to using blocklists because reducing spam -- at the cost of some legit people not being able to send email to him -- is a tradeoff he's willing to make. You haven't convinced every user running mailservers that they should increase their spam burden because some small providers can't get off blocklists.

As another example in another communication channel... Here's a similar "blocklist" for cell phones that some users take advantage of: https://about.att.com/pages/cyberaware/ae/cp

Are "legitimate" phone numbers getting caught up in that block filter?!? Of course. But phone owners are trying to stop spam telemarketing calls. Telling them that some phone users are incorrectly on AT&T's list isn't going to convince cell users to quit using the block filter. They're willing to live with a few legit callers getting blocked.

Re:After self-hosting my email for twenty-three years I have... by vinay_ys on Monday September 05, 2022 @03:26AM (#32721494)
> ideological reasons might or might not be on those lists

What's the ideological reasons here?

Re:After self-hosting my email for twenty-three years I have... by 1337shadow on Monday September 05, 2022 @05:13AM (#32722116)
Apparently people who want to self host email instead of paying some big tech
Re:After self-hosting my email for twenty-three years I have... by Aeolun on Sunday September 04, 2022 @07:06PM (#32718625)
> Even as I don't use DKIM or DMARC.

I wouldn’t expect sending email to be the problem. But I’d be surprised if it’s delivered.

Re:After self-hosting my email for twenty-three years I have... by dsr_ on Monday September 05, 2022 @12:25AM (#32720494)
One of SPF or DKIM is pretty much mandatory, and SPF is far easy to maintain.
Re:After self-hosting my email for twenty-three years I have... by bornfreddy on Sunday September 04, 2022 @03:07PM (#32716571)
Agree completely.

To those that still persist, there is a page I found recently that helps you make sure that your outgoing mail is configured correctly: https://appmaildev.com/en/dkim. They generate an e-mail address, you send a mail to them, they do the check and display results (not affiliated, just a happy user).

Re:After self-hosting my email for twenty-three years I have... by Avamander on Sunday September 04, 2022 @03:15PM (#32716658)
EU's MECSA is nice as well https://mecsa.jrc.ec.europa.eu/en/
Re:After self-hosting my email for twenty-three years I have... by yonrg on Monday September 05, 2022 @02:11AM (#32721087)
I used this one: https://www.mail-tester.com/

I will check out your recommendations. Thanks

Re:After self-hosting my email for twenty-three years I have... by flyinghamster on Sunday September 04, 2022 @03:14PM (#32716652)
I've also been self-hosting email for years, and the only deliverability problem I've ever had has been with AT&T. If I try to send something to an AT&T customer, I get an automated "your message has been eaten" notice, and following its directions accomplishes precisely nothing. At this point, I can only guess they're hellbanning the IP block in which my VPS resides, because it does not show up on any public DNSBLs.

Google? No problem. Comcast? No problem. Charter? No problem. AT&T? Problem.

Re:After self-hosting my email for twenty-three years I have... by DanAtC on Sunday September 04, 2022 @03:45PM (#32716971)
At least you get notified. Microsoft/Outlook on the other hand silently drops emails leaving you and the recipient in the dark.
Re:After self-hosting my email for twenty-three years I have... by raxxorraxor on Monday September 05, 2022 @09:36AM (#32724145)
The correct response would be to set them on the blacklist for a time. People would complain and they would quickly change their behavior. Microsoft currently really wants everyone to have a Microsoft account.
Re:After self-hosting my email for twenty-three years I have... by pas on Sunday September 04, 2022 @05:15PM (#32717796)
that seems new, or maybe a different beast from the MS zoo of madness.

gmail on the other hand does what others said, report smtp 250 and silently discard some emails. (mostly those that lack DKIM)

Re:After self-hosting my email for twenty-three years I have... by raxxorraxor on Monday September 05, 2022 @09:33AM (#32724111)
I think we are currently in a phase because of phishing problems. Corporate filters are currently turned up to eleven, but hosting your own server is still very well possible. SPF/DKIM/DMARC helps, but isn't required. You really think the corps that do host their own servers have set that up? It is far more widely spread by enthusiasts that host their own servers.

We also should keep mail for pseudonymous and anonymous user authentication. There are a lot of threats to the free internet right now and user account consolidation is one of it. I agree that people should keep hosting themselves. Someone blocked you? Their loss, let them rant to their internal IT about it. Corporations or institutions that use Google as a provider should be seen with scepticism.

Re:After self-hosting my email for twenty-three years I have... by bullen on Tuesday September 06, 2022 @04:00AM (#32734275)
Everyone that can should host their own HTTP/1.1, DNS and SMTP at home on a battery backed Raspberry 1, 2 or Zero if they have an external IP.

To host anything beyond those protocols and/or on more powerful hardware is often counter productive.

The problem is getting the ports opened, you need to fight for that right even if it makes spam worse in the short term.

Fight for external IP, ports and static IP in that order.

Re:After self-hosting my email for twenty-three years I have... by LMYahooTFY on Monday September 05, 2022 @12:25AM (#32720497)
Would using a VPS with a static IP not work?

Also does it help to use Google/Azure to host with regard to IP reputation with Gmail or Outlook?

Re:After self-hosting my email for twenty-three years I have... by kodah on Monday September 05, 2022 @12:28AM (#32720518)
Yes, as long as the IP doesn't already have some reputation attached to it. Here's a list of resources: https://sendgrid.com/blog/5-ways-check-sending-reputation/
Re:After self-hosting my email for twenty-three years I have... by yomkippur on Sunday September 04, 2022 @02:53PM (#32716416)
was just gonna ask how you would handle DKIM and SPF stuff. Hetzner? Digitalocean?
Re:After self-hosting my email for twenty-three years I have... by zahllos on Sunday September 04, 2022 @03:13PM (#32716637)
I use a small datacentre in my country, actually not far from where I live. DKIM/SPF are independent of the provider. The easiest way to understand is to consider how receiving works. If I'm getting an email from hnemail.example, the first thing I do is consider the IP address. Oh, 257.257.257.1? Ok. So I then ask DNS "what is the SPF record for hnemail.example?" and it returns

    v=spf1 mx -all
This tells me only to accept emails from 'MX' entries for that domain. So I query 'MX' against the DNS server and I get a list of A records, which I can get IPs from. If the IP is in the list, spf passes. Otherwise it fails, mark as spam.

For DKIM, when the email was sent it was signed with a key by the sending server. It is identified by a UUID in the incoming email. So the receiving server again queries DNS for TXT <UUID>._domainkey.hnemail.example and receives the public key as a response. Signature verification passes? Accept email. It fails? Mark as spam.

This doesn't have a lot to do with IP reputation. This is different. If you are a very large email provider, you might develop custom spam filters. IPs are allocated to 'autonomous systems' i.e. who actually uses them and hands them out to users, and depending on the business you might make some decisions about reputation. For example, if the IP address is part of a consumer ISP block that is handed out to users of broadband, chances are high that if they're sending email, it is probably a Windows PC compromised by malware.

Similarly, you might decide some ASNs are better than others. Some hosters are more liberal in what they will accept, such as VPN endpoints, tor nodes and such and as a consequence of this more spam comes from these ranges.

Rightly or wrongly, larger email providers try to add these extra filters to the process to protect their users from spam. This obviously sucks if you are genuinely trying to run an email server on your symmetric home fibre connection with a dedicated IP, but that's the world we live in.

I can't make any general statement on which providers might be best, and some people will have no issue whereas others will find themselves unable to send anything. I don't work for Outlook/Microsoft or Google and never have, so I don't know exactly what rules they use, and in all likeliness they shift constantly depending on spammer patterns. I can only say I've found running from a small DC to work pretty well.

Re:After self-hosting my email for twenty-three years I have... by aaronmdjones on Sunday September 04, 2022 @10:05PM (#32719729)
DKIM selectors aren't UUIDs. You can of course use a UUID as a selector, but you don't have to. My selectors are named S-YYYYMM (when I rotate the keys), so my current public key is at S-202001._domainkey.example.com.
Re:After self-hosting my email for twenty-three years I have... by dspillett on Monday September 05, 2022 @08:40AM (#32723624)
A lot of tools generate UUIDs for the selector, just to get something unique without having to ask the user for something relevant or defining some other heuristic. For instance: the built-in helper tool for Zimbra generates a UUID by default, unless you provide something specific. I think a lot of people assume it should be a UUID just because they see UUIDs used in common examples.

Few people think about key cycling for DKIM as it isn't a built-in requirement at all, so once a UUID is set they just keep it until some point in the future that may never happen when they need to revoke the key because the private half is compromised.

Re:After self-hosting my email for twenty-three years I have... by jhugo on Sunday September 04, 2022 @09:31PM (#32719552)
Find a clueful small provider, local to you if possible. On huge providers like Hetzner and DO, you are guaranteed to have spammers as neighbours some of the time, even if the provider rapidly shuts them down. On the other hand, a good-quality small provider may rarely if ever host spammers.
Re:After self-hosting my email for twenty-three years I have... by Godel_unicode on Monday September 05, 2022 @12:20AM (#32720460)
Counterpoint, our mail admins spend a lot of time trying to convince small-scale providers to shutdown the spam email coming from them. Lots of people who host at small scale providers don’t care about patches, so they send tons of spam.
Re:After self-hosting my email for twenty-three years I have... by jhugo on Monday September 05, 2022 @09:59PM (#32731802)
Doesn't seem like a counterpoint to me. The provider you're describing isn't clueful. A clueful provider pays attention to what's happening on their network and knows how to make themselves an unattractive host for spammers.
Re:After self-hosting my email for twenty-three years I have... by hkt on Monday September 05, 2022 @04:01AM (#32721683)
I suppose that's why the person you're replying to specified clueful!
Re:After self-hosting my email for twenty-three years I have... by 867-5309 on Monday September 05, 2022 @03:29AM (#32721510)
>VPS provider that disallows things like VPN endpoints

this can't exactly be policed

Re:After self-hosting my email for twenty-three years I have... by Avamander on Monday September 05, 2022 @06:46AM (#32722817)
It can be enforced when complaints come in.