> On 26. Jan 2023, at 15:17, [email protected] wrote:
>
> On 1/26/23 13:58, Harald Dunkel wrote:
>> Hi folks,
>> smtpctl spfwalk returns messages like
>> smtpctl: lookup_record: %{i}._spf.mta.salesforce.com contains macros and
>> can't be resolved
>> smtpctl: lookup_record: %{ir}.%{v}.%{d}.spf.has.pphosted.com contains macros
>> and can't be resolved
>> smtpctl: lookup_record: %{i}._spf.mta.salesforce.com contains macros and
>> can't be resolved
>> smtpctl: lookup_record: %{ir}.%{v}.%{d}.spf.has.pphosted.com contains macros
>> and can't be resolved
>> smtpctl: lookup_record: %{i}._spf.mta.salesforce.com contains macros and
>> can't be resolved
>> smtpctl: lookup_record: %{i}._spf.mta.salesforce.com contains macros and
>> can't be resolved
>> smtpctl: lookup_record: %{i}._spf.mta.salesforce.com contains macros and
>> can't be resolved
>> smtpctl: lookup_record: %{i}._spf.corp.salesforce.com contains macros and
>> can't be resolved
>> smtpctl: lookup_record: %{i}._spf.mta.salesforce.com contains macros and
>> can't be resolved
>> is this something the owner of the SPF record in DNS has to fix, is
>> this not implemented yet, or what is the story here?
> %{i} is a macro that is substituted at connection time and cannot be included
> in a
> static list.
> There are only few domains that are using SPF macros afaik.
> Giovanni
In my case, there are quite a number of domains that use SPF macros. Out of 215
domains I do SPF walk, 64 return macros.
Michael
