You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Whenever a new Space is created, all notifications will originate from an email address on the default subdomain chosen for the Space.  If you map a custom domain to the Space, you can optionally enable it as an "Email Domain", which will allow it to be used to send emails.  In order to improve the deliverability of these emails, you must add some additional DNS records, known as SPF Records.

A Sender Policy Framework (SPF) Record is an email authentication standard that compares the email sender’s actual IP address to a list of IP addresses authorized to send mail from that domain. The IP list is published in the domain’s DNS record.

In order to avoid having all of the notifications sent from your Space end up in your Member's spam folder, you will need to add or modify your SPF record to indicate that Member.buzz is a legitimate source of mail for your domain.

If you have an SPF record set for your domain, you must add include:spf.smtp.member.buzz before the all mechanism of the record. If you do not have an SPF record for your domain you must create a TXT record with the value:

v=spf1 a mx include:spf.smtp.member.buzz ~all

Do not create more than one SPF record for a given domain. If you need more than one SPF record, you will want to merge the additional SPF records into a single SPF record.

For example, if your existing record looks like this:

v=spf1 a mx include:spf.protection.outlook.com ~all

You would just need to add our lookup at the end of the string, before the ~all mechanism, like so:

v=spf1 a mx include:spf.protection.outlook.com include:spf.smtp.member.buzz ~all

After this record is added your notifications will be much less likely to end up in your Member's spam folder.

Related
  • No labels