[jira] [Resolved] (JSPF-114) Custom resolver not used by async requests

     [ https://issues.apache.org/jira/browse/JSPF-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emerson Pinter resolved JSPF-114.
---------------------------------
    Resolution: Fixed

Fixed with https://github.com/apache/james-jspf/commit/d171bdb18a1f9d929eaec72f8aee310011961aa1

> Custom resolver not used by async requests
> ------------------------------------------
>
>                 Key: JSPF-114
>                 URL: https://issues.apache.org/jira/browse/JSPF-114
>             Project: James jSPF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: master
>            Reporter: Emerson Pinter
>            Priority: Trivial
>             Fix For: master
>
>
> When a resolver is specified, we expect the library to use the server provided, like in:
> {code:java}
> SimpleResolver resolver = new SimpleResolver("127.0.0.1");
> SPF spf = new SPF(new DNSServiceXBillImpl(resolver));{code}
>  
>  
> With sync requests the resolver is used, but not with async. There are not tests failing, I saw this monitoring network packets.
> A PR was opened to fix this: [https://github.com/apache/james-jspf/pull/27|https://github.com/apache/james-jspf/pull/27]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)