If I understand correctly, this is part of the SPF spec. Those things
are defined hard, e.g. %{i} is the source IP of the message, %{ir} is
the same reversed, etc.. There are more, but it's a short list.
So, I guess this is simply not implemented in smtpctl spfwalk.
Btw... this is the first time I ever see this used in the wild, thanks
for the pointer.
On Thu, Jan 26, 2023 at 01:58:45PM +0100, 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?
Every insightful comment is highly appreciated
Harri
