When sending emails, Wordbee-Translator uses the email addresses of the user triggering the specific action, or the email address defined in the company settings.
If your company uses its own domain name as email provider, it may require your domain name administrator to allow Wordbee-Translator in your SPF record.
For that purpose, please simply add include:wordbee-translator.com to your SPF record.
Here is an example of a SPF record:
@ IN TXT "v=spf1 ip4:184.108.40.206/20 include:_spf.google.com include:wordbee-translator.com ~all"
- @ refers to your domain name. Example: google.com, wordbee.com
- TXT is the type of record. SPF record uses TXT entities.
- v=spf1 means this TXT record is used for SPF purposes.
- ip4: means that defining an IP address (range) allowed. In our example, it is one of the Gmail range.
- include:_spf.google.com means we include/add the whole SPF record of Google to our SPF record.
- include:wordbee-translator.com is the definition you need to add to allow Wordbee-Translator to send email using @your-domain.tld
- ~all means all the rest is considered as soft-fail.
More information about SPF: http://www.openspf.org/SPF_Record_Syntax
Wordbee supports the highest mail security standards, so an extra option we can sign all email messages which are sent from your Wordbee platform using custom domain and your own From (reply-to) address. Our mail server would add a proper DKIM headers in each mail so your recepient's mail servers will be able to validate emails normally. Please ask Wordbee CSM team to get more details.