An SPF error in a bounced email message will have many forms and different quantities of descriptive information. However, generally, this is an example of a typical error message triggered by an SPF issue:

The message usually contains 3 pieces of information:

1. The email address to which delivery was denied
2. The domain of the server sending the message
3. The domain and IP address of the server receiving the message
4. The reason the delivery failed - you may or may not see the initials SPF in the error message (this example does not contain a direct reference to SPF)

*** If you have no idea what any of this means, then copy this text and send it to your IT department. Tell them your event invitation campaigns and registration confirmation messages will have better deliverability. ***

If you are using a company email address as the sender of your email messages, they may be bouncing or just do not arrive at their recipient's email inbox because they look like they are spam.

When you send an email message using rsvpBOOK, your Reply-To address is “[email protected]” which looks suspicious to a recipient's email server.  The recipient's email server would ask, “Why does it say it’s from “[email protected]” when I can tell it came from rsvpBOOK’s servers".  This is a common spam tactic and can cause a message to be bounced or just discarded at the firewall.

If your company has an SPF record (most do), a small modification can be made that resolves this problem. This change tells the recipient's email server that rsvpBOOK is allowed to send email for “[email protected]."

If you have access to and can modify your DNS records, add this bit of code to your SPF record to enable authentication for all of your rsvpBOOK events:

• include:rsvpbook.com

For example, your SPF record might look something like this:

• v=spf1 mx ptr include:rsvpbook.com ~all

*** If you have no idea what any of this means, then copy this text and send it to your IT department. Tell them your event invitation campaigns and registration confirmation messages will have better deliverability. ***

1. The sending server is on a Black List - See this help document: What do I do if I'm on a Black List?
2. The message is considered SPAM by the receiving email server - See this help document: What do I do if messages are going to SPAM?
3. The email address was incorrectly entered by the registrant (a typo) - See this help document: What do I do if the registrant submits an erroneous email address?
4. 100 Spam Trigger Words & Phrases To Avoid