You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Michael Bryant <mg...@4mi.net> on 2006/11/10 01:52:54 UTC
dnsserver problems w/ 2.3.0
Hi all,
I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except that
the dnsserver will not work.
I had to change my gateway entry in config.xml from a hostname to an
IP address to be able to send mail. Also, a custom mailet I have been
using to whitelist certain sending domains is not working, because
DNS lookups are failing.
Before I changed my gateway entry to an IP address, RemoteDelivery
mailet was logging the following:
09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Unknown gateway
host: unknown host
09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: This could be a
DNS server error or configuration error.
09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Temporary
exception delivering mail (Mail1163086557437-10-!277200:
09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Storing message
Mail1163086557437-10-!277200 into outgoing after 0 retries
I know that my machine can successfully perform DNS queries.
SpamAssassin has no problems doing lookups as well. I attempted to
turn up logging in the dnsserver, but it has not yielded any
additional information.
-Mike Bryant.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Stefano Bagnara <ap...@bago.org>.
Michael Bryant wrote:
> Hi all,
>
> I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except that the
> dnsserver will not work.
>
> I had to change my gateway entry in config.xml from a hostname to an IP
> address to be able to send mail. Also, a custom mailet I have been using
> to whitelist certain sending domains is not working, because DNS lookups
> are failing.
What did your mailet do?
InetAddress lookups? or did you use DNSJava?
> Before I changed my gateway entry to an IP address, RemoteDelivery
> mailet was logging the following:
>
> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Unknown gateway
> host: unknown host
> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: This could be a
> DNS server error or configuration error.
> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Temporary
> exception delivering mail (Mail1163086557437-10-!277200:
> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Storing message
> Mail1163086557437-10-!277200 into outgoing after 0 retries
>
> I know that my machine can successfully perform DNS queries.
What platform? Windows?
Can you check what dnsservers have been autodiscovered by James Server
(beginning of dnsserver log) and if the hostname you put in
RemoteDelivery is resolvable by that name?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Marcus2 <mk...@mlsit.de>.
Hello,
I now found the problem.
After using the right DNS the Mailserver at kundenserver simply didn´t take
the
message (Error 421 in mailet.log) because there was a wrong entry in a
"Anti-Spam Database" for my IP-Adress,
because this IP-Range have dynamic and static adresses. So all adresses
where added to this list
as dynamic adresses.
See: http://www.sorbs.net for details.
Thanks for your help.
Regards Marcus
Hello Stefano,
it seems that there are some DNS-server which are not giving the correct
information.
So I simplify my config and use only one dns server.
The MX-Request ansewered as follow:
> set type=MX
> globalplanets.de
Server: dnscache2.terralink.de
Address: 217.9.16.25
Nicht autorisierte Antwort:
globalplanets.de MX preference = 10, mail exchanger =
mx01.kundenserver.de
globalplanets.de MX preference = 10, mail exchanger =
mx00.kundenserver.de
globalplanets.de nameserver = ns9.schlund.de
globalplanets.de nameserver = ns10.schlund.de
ns9.schlund.de internet address = 195.20.224.165
ns10.schlund.de internet address = 212.227.123.9
and the other response:
> set type=A
> globalplanets.de
Server: dnscache2.terralink.de
Address: 217.9.16.25
Nicht autorisierte Antwort:
Name: globalplanets.de
Address: 82.165.96.217
Hope it helps to find the problem.
Regards Marcus
Stefano Bagnara-2 wrote:
>
> Marcus2 wrote:
>
> please try:
> host -t mx globalplanets.de. servername
> host -t a mx00.globalplanets.de. servername
>
> for each of the 8 servers and report them here.
>
> Stefano
>
>> Thanks in advice
>> Marcus
>>
>>
>>
>
>
>
>
>
--
View this message in context: http://www.nabble.com/dnsserver-problems-w--2.3.0-tf2605214.html#a7277986
Sent from the James - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Marcus2 <mk...@mlsit.de>.
Hello Stefano,
it seems that there are some DNS-server which are not giving the correct
information.
So I simplify my config and use only one dns server.
The MX-Request ansewered as follow:
> set type=MX
> globalplanets.de
Server: dnscache2.terralink.de
Address: 217.9.16.25
Nicht autorisierte Antwort:
globalplanets.de MX preference = 10, mail exchanger =
mx01.kundenserver.de
globalplanets.de MX preference = 10, mail exchanger =
mx00.kundenserver.de
globalplanets.de nameserver = ns9.schlund.de
globalplanets.de nameserver = ns10.schlund.de
ns9.schlund.de internet address = 195.20.224.165
ns10.schlund.de internet address = 212.227.123.9
and the other response:
> set type=A
> globalplanets.de
Server: dnscache2.terralink.de
Address: 217.9.16.25
Nicht autorisierte Antwort:
Name: globalplanets.de
Address: 82.165.96.217
Hope it helps to find the problem.
Regards Marcus
Marcus2 wrote:
please try:
host -t mx globalplanets.de. servername
host -t a mx00.globalplanets.de. servername
for each of the 8 servers and report them here.
Stefano
> Thanks in advice
> Marcus
>
>
>
--
View this message in context: http://www.nabble.com/dnsserver-problems-w--2.3.0-tf2605214.html#a7277364
Sent from the James - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Stefano Bagnara <ap...@bago.org>.
Marcus2 wrote:
> Hello Stefano,
>
> thanks for your replay.
>
> The original domain is for example globalplanets.de
> The domain is hostet by one of the largest german provider. So if i try to
> send an mail from them to james
> evrything is ok.
> when i reply the message will never be there.
>
> an nslookup found the mx00.kundenserver.de.
>> mx00.kundenserver.de
> Server: dnscache2.terralink.de
> Address: 217.9.16.25
>
> kundenserver.de
> primary name server = nsa.schlund.de
> responsible mail addr = hostmaster.schlund.de
> serial = 2006111001
> refresh = 7200 (2 hours)
> retry = 3600 (1 hour)
> expire = 604800 (7 days)
> default TTL = 86400 (1 day)
>
> With the dig command i found some server, which does not work.
> But aome others in the list replied correctly.
> What should I do ?
This depends on the meaning of "does not work".
If they really gives you bad replies you should remove them from your
dnsservers.
please try:
host -t mx globalplanets.de. servername
host -t a mx00.globalplanets.de. servername
for each of the 8 servers and report them here.
Stefano
> Thanks in advice
> Marcus
>
>
>
> Stefano Bagnara-2 wrote:
>> You should manually check the 8 dns servers to see what they do reply to
>> "mx00.kundenserver.de".
>>
>> "dig @servername mx00.kundenserver.de"
>> for each server should help understanding the problem.
>>
>> What is the original domain? I see that dnsserver found an mx server (so
>> some dns server provided it) and that mx00.kundenserver.de has a record
>> in dns but mx00 is not the mx server for kundenserver.de but probably
>> for some other domain, right?
>>
>> Stefano
>>
>> Marcus2 wrote:
>>> Hallo,
>>>
>>> I also have problems with the dns-servers.
>>> At the beginning of the dnsserver-log I see the 8 dns servers I added to
>>> the
>>> config file.
>>>
>>> Later in the file, there is an error Message like:
>>> ERROR dnsserver: Couldn't resolve IP address for discovered host
>>> mx00.kundenserver.de..
>>>
>>> Can anyone give me a hint?
>>>
>>> Thanks in advice
>>> Marcus
>>>
>>>
>>>
>>> Noel J. Bergman wrote:
>>>>> I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except that
>>>>> the dnsserver will not work.
>>>>> I had to change my gateway entry in config.xml from a hostname to an
>>>>> IP address to be able to send mail. Also, a custom mailet I have been
>>>>> using to whitelist certain sending domains is not working, because
>>>>> DNS lookups are failing.
>>>> What do you see at the beginning of the DNS server log, where it lists
>>>> the
>>>> DNS servers that will be used?
>>>>
>>>> --- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Marcus2 <mk...@mlsit.de>.
Hello Stefano,
thanks for your replay.
The original domain is for example globalplanets.de
The domain is hostet by one of the largest german provider. So if i try to
send an mail from them to james
evrything is ok.
when i reply the message will never be there.
an nslookup found the mx00.kundenserver.de.
> mx00.kundenserver.de
Server: dnscache2.terralink.de
Address: 217.9.16.25
kundenserver.de
primary name server = nsa.schlund.de
responsible mail addr = hostmaster.schlund.de
serial = 2006111001
refresh = 7200 (2 hours)
retry = 3600 (1 hour)
expire = 604800 (7 days)
default TTL = 86400 (1 day)
With the dig command i found some server, which does not work.
But aome others in the list replied correctly.
What should I do ?
Thanks in advice
Marcus
Stefano Bagnara-2 wrote:
>
> You should manually check the 8 dns servers to see what they do reply to
> "mx00.kundenserver.de".
>
> "dig @servername mx00.kundenserver.de"
> for each server should help understanding the problem.
>
> What is the original domain? I see that dnsserver found an mx server (so
> some dns server provided it) and that mx00.kundenserver.de has a record
> in dns but mx00 is not the mx server for kundenserver.de but probably
> for some other domain, right?
>
> Stefano
>
> Marcus2 wrote:
>> Hallo,
>>
>> I also have problems with the dns-servers.
>> At the beginning of the dnsserver-log I see the 8 dns servers I added to
>> the
>> config file.
>>
>> Later in the file, there is an error Message like:
>> ERROR dnsserver: Couldn't resolve IP address for discovered host
>> mx00.kundenserver.de..
>>
>> Can anyone give me a hint?
>>
>> Thanks in advice
>> Marcus
>>
>>
>>
>> Noel J. Bergman wrote:
>>>> I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except that
>>>> the dnsserver will not work.
>>>> I had to change my gateway entry in config.xml from a hostname to an
>>>> IP address to be able to send mail. Also, a custom mailet I have been
>>>> using to whitelist certain sending domains is not working, because
>>>> DNS lookups are failing.
>>> What do you see at the beginning of the DNS server log, where it lists
>>> the
>>> DNS servers that will be used?
>>>
>>> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/dnsserver-problems-w--2.3.0-tf2605214.html#a7275991
Sent from the James - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Stefano Bagnara <ap...@bago.org>.
You should manually check the 8 dns servers to see what they do reply to
"mx00.kundenserver.de".
"dig @servername mx00.kundenserver.de"
for each server should help understanding the problem.
What is the original domain? I see that dnsserver found an mx server (so
some dns server provided it) and that mx00.kundenserver.de has a record
in dns but mx00 is not the mx server for kundenserver.de but probably
for some other domain, right?
Stefano
Marcus2 wrote:
> Hallo,
>
> I also have problems with the dns-servers.
> At the beginning of the dnsserver-log I see the 8 dns servers I added to the
> config file.
>
> Later in the file, there is an error Message like:
> ERROR dnsserver: Couldn't resolve IP address for discovered host
> mx00.kundenserver.de..
>
> Can anyone give me a hint?
>
> Thanks in advice
> Marcus
>
>
>
> Noel J. Bergman wrote:
>>> I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except that
>>> the dnsserver will not work.
>>> I had to change my gateway entry in config.xml from a hostname to an
>>> IP address to be able to send mail. Also, a custom mailet I have been
>>> using to whitelist certain sending domains is not working, because
>>> DNS lookups are failing.
>> What do you see at the beginning of the DNS server log, where it lists the
>> DNS servers that will be used?
>>
>> --- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: dnsserver problems w/ 2.3.0
Posted by Marcus2 <mk...@mlsit.de>.
Hallo,
I also have problems with the dns-servers.
At the beginning of the dnsserver-log I see the 8 dns servers I added to the
config file.
Later in the file, there is an error Message like:
ERROR dnsserver: Couldn't resolve IP address for discovered host
mx00.kundenserver.de..
Can anyone give me a hint?
Thanks in advice
Marcus
Noel J. Bergman wrote:
>
>> I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except that
>> the dnsserver will not work.
>
>> I had to change my gateway entry in config.xml from a hostname to an
>> IP address to be able to send mail. Also, a custom mailet I have been
>> using to whitelist certain sending domains is not working, because
>> DNS lookups are failing.
>
> What do you see at the beginning of the DNS server log, where it lists the
> DNS servers that will be used?
>
> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/dnsserver-problems-w--2.3.0-tf2605214.html#a7275515
Sent from the James - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: dnsserver problems w/ 2.3.0
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Hmm. good question, Stefano. It uses InetAddress.getByAddress().
That means it bypasses our DNS support and uses whatever InetAddress chooses
to use for resolution.
We really should modify the environment to force InetAddress to use dnsjava
as the DNS resolver.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Michael Bryant <mg...@4mi.net>.
On Nov 10, 2006, at 4:19 AM, Stefano Bagnara wrote:
> Michael Bryant wrote:
>> Hi all,
>> I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except
>> that the dnsserver will not work.
>> I had to change my gateway entry in config.xml from a hostname to
>> an IP address to be able to send mail. Also, a custom mailet I
>> have been using to whitelist certain sending domains is not
>> working, because DNS lookups are failing.
>
> What did your mailet do?
> InetAddress lookups? or did you use DNSJava?
Hmm. good question, Stefano. It uses InetAddress.getByAddress().
>
>> Before I changed my gateway entry to an IP address, RemoteDelivery
>> mailet was logging the following:
>> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Unknown
>> gateway host: unknown host
>> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: This could
>> be a DNS server error or configuration error.
>> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Temporary
>> exception delivering mail (Mail1163086557437-10-!277200:
>> 09/11/06 10:36:02 INFO James.Mailet: RemoteDelivery: Storing
>> message Mail1163086557437-10-!277200 into outgoing after 0 retries
>> I know that my machine can successfully perform DNS queries.
>
> What platform? Windows?
OS X v 10.3.
> Can you check what dnsservers have been autodiscovered by James
> Server (beginning of dnsserver log) and if the hostname you put in
> RemoteDelivery is resolvable by that name?
I have included some RemoteDelivery log samples in another email. I
have also verified that I can do a lookup on my gateway server
(smtp.tds.net).
-Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: dnsserver problems w/ 2.3.0
Posted by Michael Bryant <mg...@4mi.net>.
Another piece of information. I use fetchmail for a few email
addresses, and it is having no problems doing DNS lookups.
-Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: dnsserver problems w/ 2.3.0
Posted by "Noel J. Bergman" <no...@devtech.com>.
> I switched from 2.2.1RC1 to 2.3.0 yesterday. All is well except that
> the dnsserver will not work.
> I had to change my gateway entry in config.xml from a hostname to an
> IP address to be able to send mail. Also, a custom mailet I have been
> using to whitelist certain sending domains is not working, because
> DNS lookups are failing.
What do you see at the beginning of the DNS server log, where it lists the
DNS servers that will be used?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org