For our business, we send out a significant amount of newsletter alerts to customers that sign up for it on our website. We used to send this mail directly from our web server via PHP. But because the web server limited us to the number of
emails we could send per day, we purchased a VM server at a different host (that doesn't throttle email) and we are going to use that account solely for sending out the
emails.
Anyways, now that the SPF records are going to be different from what they used to be and the source mail server is different, what steps need to be taken to prevent these
emails being flagged as spam?
I know in Gmail, it's pretty smart about determining if the person actually sending the email is sending it from the server it expects (for flagging Phishing
emails, etc). We don't want that to happen to our
emails. Just sending a couple test
emails out, Gmail's shows the SPF record saying:
Authentication-Results: mx.google.com; spf=neutral (google.com:
XXX.XXX.23.176 is neither permitted nor denied by best guess record
for domain of
[email protected])
[email protected]
So is there anything we need to do with regards to SPF records as we move forward?
