On 22/12/2020 20:39, John Levine via mailop wrote:
> In article <21e3c5bb-b8bd-460b-84d9-6419b5434...@one.com> you write:
>>> On 21 Dec 2020, at 21.16, Kevin A. McGrail via mailop
>>> wrote:
>>>
>>> On 12/21/2020 1:56 PM, Eric Tykwinski via mailop wrote:
Just a heads up:
v=spf1
In article <21e3c5bb-b8bd-460b-84d9-6419b5434...@one.com> you write:
>> On 21 Dec 2020, at 21.16, Kevin A. McGrail via mailop
>> wrote:
>>
>> On 12/21/2020 1:56 PM, Eric Tykwinski via mailop wrote:
>>> Just a heads up:
>>>
>>> v=spf1 include:spf2.bluehost.com include:_spf.qualtrics.com
>>>
On 12/22/2020 2:54 AM, Sidsel Jensen via mailop wrote:
Is this still a valid limit? I’d like to hear your thoughts about it.
IMO know. It hasn't been valid for years in the real-world. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7182 for more
background when the Apache SpamAssassin
On 12/22/20 2:54 AM, Sidsel Jensen via mailop wrote:
Is this still a valid limit? I’d like to hear your thoughts about it.
The limit was chosen for performance reasons, and for that it's still
valid. SPF validates envelope information, so those lookups happen even
if the message will
> On 21 Dec 2020, at 21.16, Kevin A. McGrail via mailop
> wrote:
>
> On 12/21/2020 1:56 PM, Eric Tykwinski via mailop wrote:
>> Just a heads up:
>>
>> v=spf1 include:spf2.bluehost.com include:_spf.qualtrics.com
>> include:_spf.google.com include:_spf.salesforce.com
>>
On 12/21/2020 1:56 PM, Eric Tykwinski via mailop wrote:
Just a heads up:
v=spf1 include:spf2.bluehost.com include:_spf.qualtrics.com
include:_spf.google.com include:_spf.salesforce.com
include:sparkpostmail.com include:spf.mailjet.com -all
evaluating...
Results - PermError SPF Permanent
