Fixed in V47 and newer.
|
The automatic option is the most nicest implementation: |
|
|
|
|
|
|
|
(v) Option to Bypass Greylisting on SPF Pass |
|
|
|
If protector receives an email from a domain which has published SPF records, and the IP address connecting to protector is authorized to send from this domain, and this option is enabled, protector will not perform grey listing. |
||
|
|
|
|
|
(v) Option Bypass Greylisting when message arrives from A or MX record. |
||
|
Prior to running grey listing, protector will do a DNS/A and DNS/MX lookup. If the connecting address is found in one of the records, the grey listing will be skipped if this option is enbabled. |
||
|
|
|
|
|
Otherwise manual entries of spf records will also do: |
|
|
|
|
|
|
|
v=spf1 include:spf.protection.outlook.com -all |
outlook |
https://technet.microsoft.com/en-us/library/dn789058(v=exchg.150).aspx |
|
v=spf1 include:_spf.google.com |
|
|
|
v=spf1 include:mail.zendesk.com |
zendesk |
|
|
v=spf1 include:email.freshdesk.com |
freshdesk |
|
|
v=spf1 include:spf.mandrillapp.com |
mandrilapp |
|
|
v=spf1 include:servers.mcsv.net |
mailchimp |
|
|
v=spf1 exists:%{i}._spf.mta.salesforce.com |
salesforce |
|
Comments
0 comments
Please sign in to leave a comment.