Some companies have strict email policies in place to reduce email seen as SPAM from being delivered to their users.
One of these checks is to look at the sender’s address and authenticate that the server sending the mail is 'signed' or 'approved' as a legitimate sender for that email domain.
We use our members’ real email address as the 'From' and 'Reply To' address, but the email is being sent from the CorpNote server. When the email is then authenticated by the receiving server, there is no connection between the email address and the sending server. As a result, the email 'bounces' as undeliverable.
Your email administrator has to set your company email server to recognize (authenticate) the CorpNote email server as an approved sender. This way, when another company receives an email you send from CorpNote and wants to check its validity, your email server says, “yes, this server is legitimate and approved to be sending email using our company’s email domain name.”
What to tell your email administrator:
Email messages sent through CorpNote are being rejected due to failing the Sender Policy Framework (SPF) lookup. The sending domain's SPF record does not include the sending IP address being used to relay the email. Please add the following server information to your domain's DNS to approve CorpNote as an email sender for our domain:
DNS Record Type: TXT
Value: v=spf1 include:spf.corpnote.com ~all
TTL: 3600 seconds or 1 hour
Your domain may have other entries in its SPF record, in which you will only need to add include:spf.corpnote.com directly after v=spf1
If you previously added an SPF entry for CorpNote's mail server, you can safely remove ip4:220.127.116.11 from your record during this time, as the include statement will also contain this address.