Sending an e-mail is very convenient and a fast means of communication. Unfortunately, it is quite easy to send false e-mails (spam) on behalf of another person. This is possible because the e-mail protocol does not check by default whether the person sending the e-mail is allowed to do so on behalf of that domain. By building in Sender Policy Framework (SPF) records you keep control.
By determining whether the sender of an e-mail message (Coachview) is entitled to send a message on behalf of the sender (you), we try to reduce spam. This is done by describing in an SPF record which servers are allowed to send e-mails on behalf of the domain name. Based on the SPF-record, a receiving server can pass on this e-mail, mark it as unsafe or refuse it altogether.
How do you do this?
For each domain (@your domain1, @your domain2) that is going to be sent an e-mail, it is wise to add the Coachview e-mail server. The Coachview email server is authorized to send email on behalf of these domain names.
Also read this information:
A check to test whether an e-mail from Coachview is going to arrive correctly is desirable and sensible. If the SFP-record is not set correctly, it is possible that some e-mail will arrive internally in your own e-mail, but not in Gmail, Outlook, etc. This will result in a so called 'softfail'. In this case the e-mails can be marked as spam.
Via the website https://vamsoft.com/support/tools/spf-policy-tester you can check if the new SPF-record works.
Testing is already possible without adjusting the dns.
Fill in the following: