T_SPF_PERMERROR in logs.
Good day Guys Im seeing T_SPF_PERMERROR in my logs. Does anyone know what or where this is coming from? Regards Brent Clark
Re: T_SPF_PERMERROR in logs.
On Wed, 15 May 2019 13:58:43 +0200 Brent Clark wrote: > Good day Guys > > Im seeing T_SPF_PERMERROR in my logs. > > Does anyone know what or where this is coming from? From rfc 7208: 2.6.7. Permerror A "permerror" result means the domain's published records could not be correctly interpreted. This signals an error condition that definitely requires DNS operator intervention to be resolved.
Re: T_SPF_PERMERROR in logs.
On 15 May 2019, at 7:58, Brent Clark wrote: Good day Guys Im seeing T_SPF_PERMERROR in my logs. For what domain? Does anyone know what or where this is coming from? As RW noted, that is a state that occurs when a SPF record exists but it cannot be properly interpreted. This most commonly has one of two root causes: 1. A typo in the SPF record that makes it syntactically invalid. 2. Excess complexity in a SPF record that results in a need to do more than 10 DNS queries to resolve the fully-expanded record.
Re: T_SPF_PERMERROR in logs.
On 5/15/2019 11:47 AM, Bill Cole wrote: >> Does anyone know what or where this is coming from? > > As RW noted, that is a state that occurs when a SPF record exists but > it cannot be properly interpreted. This most commonly has one of two > root causes: > > 1. A typo in the SPF record that makes it syntactically invalid. > > 2. Excess complexity in a SPF record that results in a need to do more > than 10 DNS queries to resolve the fully-expanded record. >From memory, I think we acknowledge the RFC limit but we actually dive to 20 due to the significant real-world issue a limit of 10 causes. -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
