Thanks Serge your are dead right!

I cannot believe it! I was really making the mistake of adding the IP of
the machine as one of the DNS Servers ,that's why it was taking too
long, as to why I did this I a have no idea, this is one big mistake I
had all the time and failed to notice it .  
Its working fine , instantly doing lookups.

Kwirirai Nhakwi


-----Original Message-----
From: Serge Knystautas [mailto:[EMAIL PROTECTED]] 
Sent: Monday, January 13, 2003 4:25 PM
To: James Developers List
Subject: Re: DNS Lookups taking too long

Kwirirai wrote:
> Hi
> This is a simple test I did , I just had to stick in start time and
end
> time in  Remote Delivery Mailet between the code that does the lookup.
> Its just a simple test but its really showing me what I am failing to
> understand. I actually noticed this when I sent mailing list with
about
> 300 emails and it took about one and half days to clear up the mail in
> the spool.
> Is it because I am using J2sdk1.4.1 on windows 2000 ,
> because if doing lookups manually using nslookup (windows 2000) is
that
> fast, I don't think it is the network.

I'm betting you didn't configure your DNS servers in James, and the 
query is timing out.  Ordinarily a DNS server shouldn't take more than a

few seconds to respond, so the only way I could see it taking this long 
is if your DNS servers are not or are misconfigured in james-config.xml.

-- 
Serge Knystautas
Loki Technologies
http://www.lokitech.com


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to