- Why am I seeing this Email Warning?
- Why would emails be more likely to get flagged as Spam?
- How do I fix this?
- I’m not allowed to create an SPF record for my domain!
- How do I know my SPF record is correct?
- Is there a way to remove the error without an SPF record?
When a site is making use of a custom sender e-mail (other than the default email@example.com) recipients of your e-mails are more likely to flag your e-mails as spam. This is not a new item within FluidReview, however due to an increased number of support tickets relating back to e-mails not sending or being received, we have implemented this notice for administrators.
When a site is making use of a custom e-mail sender address, the recipient sees that the sender is from one domain (i.e. firstname.lastname@example.org), and the mail server is from another (fluidreview). As a result of this mismatch, there is an increased chance that mail can be marked as spam, especially in cases of sending out to larger institutions with stricter mail filtering and holding processes (i.e. government, educational facilities, or large corporations).
In order to ensure mail being sent through your custom sender address is sent through normally, we are recommending that clients using our services create an SPF record for their domain. In most cases, the only information you require to achieve this is the IP address provided through the warning message, ip4:18.104.22.168
The SPF record gives our mail server permission to send e-mails via any e-mail address on your web domain, specifically this means we are permitted to send e-mails through FluidReview from your custom sender e-mail address. Additionally, that e-mail address can be switched out for any other sender e-mail address on your domain once the SPF record has been set up.
The IP address listed above, and in the warning message, can be provided to your IT department for implementation. If there are any concerns, or if information is missing, our technical support team would be happy to help!
There are bound to be some cases where setting up an SPF record is not possible, in those cases we recommend setting up a subdomain, and using an e-mail address from that. The SPF record can be tied to the subdomain without impacting your domain. Again, your IT department should be able to set this up for you. If this method is also not possible, please get in touch with support so we can discuss any other options.
When the SPF record has been set up successfully, the warning message will be removed from your site right away! The warning message is consistently checking the relationship between the custom domain entered in the sender address field on your text and translations page, as soon as we verify a successful link the warning message will be removed.
At present time the only option if you do not wish to set up an SPF record would be to revert the sender e-mail address to email@example.com, which is our default sender address, and is already linked with our mail server.