Hi,
I have a contact form on my website (hosted with Digital Ocean). The contact form sends form submissions to my Google G-Suite email address. Unfortunately emails are being marked as spam.
My setup
SPF and a DKIM txt records but emails from the form still end up in my spam folder.Where I’m up to
PTR recorddmarc record.dmarc record.Have I correctly setup my PTR record? This is what I’ve done:
Droplet was called my-company-websiteDigitalOcean will set a PTR record for your server as long as you use a fully qualified domain name (FQDN) like pluto.example.com rather than a single-label hostname like pluto.
mywebsite.co.ukdigitalocean.mywebsite.co.uk to name my Droplethost xx.xxx.xx.xxdomain name pointer is now the same as my droplet namexx.xx.xxx.xx.in-addr.arpa domain name pointer digitalocean.mywebsite.co.uk.PTR record setup?Kind regards Stephen Meehan
UPDATE
I’ve not waited 24 hours for the changes to take affect, but it looks like they have partly worked…
I’ve ran a test submission from my contact form on my website, emails are still going to spam. But I thought I’d take a look at the email header to see if I can spot any mention to the updated domain name pointer
It looks like Google Mail can see the update, digitalocean.mywebsite.co.uk. is in the header…
This bit looks like it could be wrong:
Received: from my-company-website.localdomain.example.com (digitalocean.mywebsite.co.uk. [xx.xxx.xx.xx])
It still says Received: from my-company-website. That was the original name of my Droplet
Is that supposed to still say that?
Here’s the full header, I’ve redacted any IP addresses.
Delivered-To: s.meehan@mywebsite.co.uk
Received: by 10.79.31.67 with SMTP id f64csp2990959ivf;
Thu, 2 Feb 2017 03:50:54 -0800 (PST)
X-Received: by 10.28.45.197 with SMTP id t188mr7968770wmt.15.1486036253973;
Thu, 02 Feb 2017 03:50:53 -0800 (PST)
Return-Path: <s.meehan@mywebsite.co.uk>
Received: from my-company-website.localdomain.example.com (digitalocean.mywebsite.co.uk. [xx.xxx.xx.xx])
by mx.google.com with ESMTP id xxxxxxxxxxxxxxxxxxxxxxxx
for <s.meehan@mywebsite.co.uk>;
Thu, 02 Feb 2017 03:50:53 -0800 (PST)
Received-SPF: softfail (google.com: domain of transitioning s.meehan@mywebsite.co.uk does not designate xx.xxx.xx.xx as permitted sender) client-ip=xx.xxx.xx.xx;
Authentication-Results: mx.google.com;
spf=softfail (google.com: domain of transitioning s.meehan@mywebsite.co.uk does not designate xx.xxx.xx.xx as permitted sender) smtp.mailfrom=s.meehan@mywebsite.co.uk
Received: by my-company-website.localdomain (Postfix, from userid 1000) id 0CD8E40899; Thu,
2 Feb 2017 11:50:53 +0000 (UTC)
To: s.meehan@mywebsite.co.uk
Subject: Paul - Enquiry
Date: Thu, 2 Feb 2017 11:50:52 +0000
From: Company Name <s.meehan@mywebsite.co.uk>
Reply-To: demoemail@gmail.com
Message-ID: <75aca06ac1bd0890ff9a106e41baca4b@mywebsite.co.uk>
X-Mailer: PHPMailer 5.2.21 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Name: Paul Test
Email: demoemail@gmail.com
Message:
This is a test
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
The hostname in the headers are the one in your mail server config. Just do a grep for it in /etc/
Hi
Thanks for the reply. I’m pretty new to this.
Droplet was called my-company-websitedigitalocean.mywebsite.co.ukHostname and hosts files
In my hostname file located at /etc/hostname it shows the new Droplet name digitalocean.mywebsite.co.uk
The hosts file located at etc/hosts shows the original Droplet name my-company-website
Email header
The email header still shows the old Droplet name my-company-website:
Received: from my-company-website.localdomain.example.com (digitalocean.mywebsite.co.uk. [xx.xxx.xx.xx])
by mx.google.com with ESMTP id xxxxxxxxxxxxxxxxxxxxxxxx
A couple of questions about this header:
example.com?Received part of the email header getting my-company-website from the etc/hosts file? Looks like it is…What next?
The etc/hosts file displays the old Droplet name my-company-website:
127.0.1.1 my-company-website.localdomain my-company-website
I’m not sure what I need to change this to?
Do I need to update it to use the new droplet name digitalocean.mywebsite.co.uk
127.0.1.1 digitalocean.mywebsite.co.uk.localdomain digitalocean.mywebsite.co.uk
Or do I use just the domain name?
127.0.1.1 mywebsite.co.uk.localdomain mywebsite.co.uk
Bit confused?
Hi
Thanks for the replies.
etc/hosts to keep the edits I made after a sever rebootDropletwith a FQDN from the startPTR record was the only part of the puzzleDroplet with a FQDN, I noticed emails did appear in my inboxspf softfailspf recordspf pass (brilliant).Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.