One of the most important things Floify does is send out email notifications to borrowers throughout the loan process in Floify.
Needs List emails are sent out from Floify on your behalf. You are listed on the FROM line of the email, but the email comes directly from a Floify server.
To keep your email notifications out of your borrowers’ spam, have your IT person follow the directions below.
It takes the Internet a while to warm up to the idea of, “Floify is sending email on my behalf.” That’s a major reason why your Needs List emails can end up in your borrower’s spam.
What we want to do is tell the Internet, “It’s ok for Floify to send emails on my behalf.” This means that your Needs List emails will go to spam far less often, which is what we want if we want to fund some loans!
If editing your SPF record does not work, please reach out to Support and ask the team to help configure a DKIM. Please provide this information when requesting DKIM configuration:
DNS Provider (ex. Go Daddy)
How do we tell the Internet that it’s ok for Floify to send email on your behalf?
You edit your SPF record in your DNS and add Floify as an allowed sender of email.
Go to www.kitterman.com/spf/validate.html and type in your domain name at the top of the page.
(Another good SPF tool is http://tools.wordtothewise.com/spf.)
Click “Get SPF Record” to view the results.
If your domain already has an SPF record, which is likely, it will look something like the following. (If the SPF tool reports that there are no SPF records, see the section below called “How to Create an SPF Record”.)
v=spf1 include:aspmx.googlemail.com ~all
The line above says that it’s ok for Gmail to send email on your behalf.
Now let’s add in Floify.
Edit your DNS’s SPF record to insert “include:spf.floify.com” before the first “include” tag, like so:
v=spf1 include:spf.floify.com include:aspmx.googlemail.com ~all
Now you are telling the Internet, “It’s ok for Floify to send email on my behalf.”
Now your Needs List emails will go to spam far less often than before. That’s what we want!
After your DNS is updated, it takes some time for the information to propagate around the Internet, but it usually takes less than 24 hours. As an alternative to checking your DNS SPF records on kitterman.com, you can run “dig” from the command line like so:
dig YOURDOMAIN.com txt
The answer section of the dig query will show your domain’s TXT records, which is where your SPF record is stored.
How to Create an SPF Record
If your domain does not have an SPF record, you can create one. Create a TXT record in your DNS that looks like this:
v=spf1 mx a include:spf.floify.com ~all
Allow MX servers listed on this domain to send email for this domain
Allow the root of this domain (the apex/naked domain) to send email for this domain
Mail servers should accept email from this domain whether or not it matches the parameters in the SPF record