You may choose the email address to display in the "From" field for messages that Pathable sends to your attendees on your behalf (e.g., invitation email, message notifications, etc.) However, if you choose to an address with your domain instead of an @pathable.com domain, you must follow the instructions below, otherwise you greatly increase the likelihood that such messages will be quarantined as spam by your attendees' mail server.
Spam filters will see the mail that purports to be from @yourdomain.com, see that it is actually being sent from @pathable.com's mail servers and they will be suspicious. The below steps will re-assure the recipient's mail servers that Pathable has permission to send mail on your behalf.
You will likely need the assistance of someone from your IT department to complete these steps. There is some information background on the Sender Policy Framework here.
Pathable uses Sendgrid as our mail server, so have your IT department add the following link to your existing SPF record:
Alternatively, if you don't have an SPF record, they can create a new TXT record, instead:
v=spf1 include:sendgrid.net ~all
After adding the SPF or TXT record visit this website to check it has been inputted correctly. If you see the following warning message there is a possibility emails might get sent to spam.
Warning: The maximum amount of 10 lookups was exceeded. ISPs could ignore your SPF record
As a second, highly recommended step, you will be asked to set up a CName from several subdomains of the domain you are sending from to Pathable's mail server addresses. For example, you might be asked to create the following set of CNames in your zone editor. Please contact your Implementation Specialist for the exact CName settings for your account.
- pathable.example.com - u26399.wl150.sendgrid.net
- s1._domainkey.example.com - s1.domainkey.u26399.wl150.sendgrid.net
- s2._domainkey.example.com - s2.domainkey.u26399.wl150.sendgrid.net
These domain keys assure a mail server that Pathable's mail servers (managed by Sendgrid) are authorized to send mail on behalf of example.com, in this example.
Occasionally, there will be a conflict with the CNames generated. This happens if you have gone through these same steps previously with another provider. If this is the case, please request a custom DKIM selector from your IS.