didds wrote:mc2fool wrote:It's a long time since I used 123Reg. Do they now have a wizard to automatically set up SPF, DKIM & DMARC for your domain to be used as you describe, so that receivers won't just dump your messages into spam folders, or do you have to do the DNS setup for those yourself?
thats a good question!
TBH I don't know a definitive answer to that (as our emails arent anything but personal use etc) but if there isnt anything automagical, then the dns interface at 123reg is very simple and it should be easy enough to set your own up.
I only sued 123reg as an example cos thats what I/we use - id imagine other domain providers have similar offerings etc .
UPDATE: I have now found this wrt 123reg
https://www.123-reg.co.uk/support/serve ... ing-email/
cheersdidds
That link doesn't solve the issue that mc2fool is on about. I've customised my domain email DNS/TXT to allow Gmail/Outlook.com SMTP sending and it still drops a bit on deliverability scores across all the various testing sites compared to my domain hosts native sent email setup (Fasthosts).
The only way you can really effectively use Gmail or MS Outlook/exchange with domain email these days is if you have the email portion hosted with them so that all the DNS ducks align.
123Reg offer MS365 as an add on domain package (via MS' domain host GoDaddy) that should solve all the DNS issues if it's being done correctly.
Google sold their domain hosting to Squarespace last year and I couldn't see any offering for Google Workspaces as an add on package on 123Reg.
For Gmail there is third party Gmailify as a $6.99 per annum option to run free Gmail accounts with domains - lengthy explainer here...
https://www.gmailify.com/docsDeliverability could still potentially be an issue as they explain in their documentation here...
https://www.gmailify.com/docs#t2-16The major email companies are tightening up on spammer issues this year for both received and sent email, aliasing is one of the main routes for spammers so expect inbox deliverability scores to go down if you use the free workarounds for sending domain email from anyone but the designated email host.
The way it works with the third party bulk email companies like Sendrgid etc. is they generally have nominated subdomains to work from with their own DNS/TXT settings (partially to get around the SPF lookup limits) and they will rotate their SMTP IP addresses to keep off 'ze lists' (DNSBL et al).
They also have the size and clout to deal with MS/Google directly about any deliverability issues, smaller outfits don't - as many have blogged about like Tutanota with their MS blanket SMTP IP blocks that took a tech media coverage blitz to eventually get resolved...