[
https://issues.apache.org/jira/browse/JAMES-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3920.
---------------------------------
Fix Version/s: master
3.9.0
Resolution: Fixed
Adopting JSPF 1.0.4 solved the issue.
> SPF record: not found for host
> ------------------------------
>
> Key: JAMES-3920
> URL: https://issues.apache.org/jira/browse/JAMES-3920
> Project: James Server
> Issue Type: Bug
> Reporter: Günter Paul
> Priority: Major
> Fix For: master, 3.9.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> I tested "apache-jspf-resolver-1.0.3.jar" with newest source code.
> Here an output:
> {{Received-SPF: none (spfCheck: 209.85.217.49 is neither permitted nor denied
> by domain of googlemail.com) client-ip=209.85.217.49;
> [email protected]; helo=googlemail.com;}}
> I tested it with other mailserver to, the same problem.
> After I changed the class "org.apache.james.jspf.impl.SPF". In the
> constructor I changed the "executor" form "AsynchronousSPFExecutor" to
> "SynchronousSPFExecutor" and the problem was solved.
> this.executor = new SynchronousSPFExecutor(dnsProbe);
> {{It'a a workaround, not a solution.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
