maxDnsProblemRetries doesn't seem to work

[Kevin Puscas <ke...@nitorgroup.com>]

I have a test scenario where a email target on another server requires multiple DNS retries before an MX record can be found.  I tried setting the maxDnsProblemRetries parameter on the RemoteDelivery maiilet but that seemed to have no effect. When I  looked at the code for the RemoteDelivery mailet and walked through with the remote debugger,  it appears as if the dns can’t be resolved (targetServers =0) it always throws a permanent exception in the deliver method and therefore won’t retry again. I’m not sure if this is a bug or if I am missing an additional configuration some where else. 


thanks
-- 
Kevin Puscas
Principal 
Nitor Group, Ltd.
"trust, illumination, leadership"
Phone: 301.919.2978

Re: maxDnsProblemRetries doesn't seem to work

[Eric Charles <er...@apache.org>]

Sounds like a bug.
Better log it for future solving
https://issues.apache.org/jira/browse/JAMES

If you can debug it, maybe you can solve it and submit a patch?

On 07/09/2014 04:26 PM, Kevin Puscas wrote:
> I have a test scenario where a email target on another server requires multiple DNS retries before an MX record can be found.  I tried setting the maxDnsProblemRetries parameter on the RemoteDelivery maiilet but that seemed to have no effect. When I  looked at the code for the RemoteDelivery mailet and walked through with the remote debugger,  it appears as if the dns can’t be resolved (targetServers =0) it always throws a permanent exception in the deliver method and therefore won’t retry again. I’m not sure if this is a bug or if I am missing an additional configuration some where else. 
> 
> 
> thanks
> -- 
> Kevin Puscas
> Principal 
> Nitor Group, Ltd.
> "trust, illumination, leadership"
> Phone: 301.919.2978
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org