On Wed, 20 Oct 2021 09:24:41 +0100 Mark Rogers mark@more-solutions.co.uk allegedly wrote:
As I understand it, in broad terms this involves telling the Internet which hosts are allowed to send mail for the domain, and what to do with mail that doesn't match that?
Yes.
Taking one example, I have a couple of family domain names which I manage, where mark@ comes to me, mike@ goes to my Dad, and so on. Each of the people have their own mail configurations; mine pretty much always goes through Google (I got set up on their workplace package back in the days when you get a 50-user account for free and I'm reluctant to give that up!), my Dad uses Virgin, my uncle uses BT Internet, etc. Am I on a hiding to nothing here?
No, it just complicates the SPF record. You will need an "include:" for all the mail systems which are allowed to send mail from your domain.
(I could set up my own mail server, but then I'd have to reconfigure everyone's phones, laptops, etc and maintain that configuration - and I really don't want to go there!)
And you might then find that no-one will accept mail from your domain at all. As I said, it is becoming increasingly difficult to get email accepted unless it comes from a large recognised source. Practically ALL email systems will reject email if it comes from an IP address recognised as being on a DSL line (so that means that you couldn't host at home). I have also had numerous systems (usually the smaller ones run by idiots) "blacklist" my server's IP address on the gounds that it is hosted on a VM in a large datacentre which may, just may, also host spammers.
It takes time to gain a decent email reputation.
Good luck
Mick
--------------------------------------------------------------------- Mick Morgan gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312 https://baldric.net/about-trivia ---------------------------------------------------------------------