This seems to be happening regularly - enough to be causing serious SPF
reliability errors
Received-SPF: permerror (homedepot.com: Unknown mechanism type 'inclu' in
'v=spf1' record) receiver=assp.OurCharity.org; identity=mailfrom;
envelope-from="homede...@homedepot.com"; helo=mail-ext.escalate.com;
client-ip=64.124.92.69
When I do a NSLookup in Windows 8 or Windows 2012, I see:
"v=spf1 ip4:207.11.40.24 ip4:207.11.40.25 ip4:207.11.27.104
ip4:207.11.27.105 ip4:50.57.54.137 ip4:64.124.92.69
a:smtp01.edifecs.com a:smtp02.edifecs.com include:
spf.messaging.microsoft.com include:cust-spf.exacttarget.com include:s
pf.mailengine1.com inclu" <--- note the quote and the line break
"de:spf.mtasv.net ~all"
That "inclu" at the end of the line is interpreted as ASSP as invalid,
which it IS, but assp should be seeing that 2nd line that starts "de" to
make "include." Of course this seems like more of a problem with windows
DNS. It dosn't matter if I use internal windows DNS servers or Google's
(presumably Linux) 8.8.8.8 server. Same formatting of the results.
Anyone else seeing this on windows?
On Tue, May 5, 2015 at 10:22 AM, K Post <nntp.p...@gmail.com> wrote:
> On my windows systems, when I do a NSLookup for the SPF record for
> b.news.saksoff5th.com, I get
> > b.news.saksoff5th.com
> Server: google-public-dns-a.google.com
> Address: 8.8.8.8
> b.news.saksoff5th.com text =
>
> "v=spf1 ip4:63.232.236.204/30 ip4:8.7.44.124/31 ip4:8.7.44.123/32
> ip4:8.7.44.126/32 ip4:207.251.96.0/24 ip4:65.1
> 25.54.0/24 ip4:2"
> "08.49.63.128/28 ip4:63.211.90.16/29 ip4:8.7.42.16/29 ip4:
> 8.7.43.16/29 ip4:63.232.236.144/29 ip4:8.7.44.144/29 i
> p4:63.236.31.128"
> "/26 ip4:63.236.76.0/23 ip4:8.30.201.0/26 ~all"
>
> Looking at the mail analyzer, I get:
> Received-SPF: permerror (b.news.saksoff5th.com: Missing required IPv4
> address in 'ip4:2') receiver=antispam.nexario.net; identity=mailfrom;
> envelope-from="bo-b9vk0mvatcv9czaumtyq5qcby69...@b.news.saksoff5th.com";
> helo=mta954.news.saksoff5th.com; client-ip=8.7.44.125
>
> So ASSP doesn't like ip4:2 which is't seeing at the end of line 1 of the
> DNS entry.
>
> I think this might be a windows problem. If I go here:
>
> http://mxtoolbox.com/SuperTool.aspx?action=txt%3ab.news.saksoff5th.com&run=toolpage
> I see the entire record, without the line splits.
>
> Any chance of having ASSP combine records like this? I feel like it could
> potentially be a problem for DKIM and DMARC records too, though I'm just
> guessing based on potential length, not experience.
>
>
> thanks
>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
