Re: [exim] Sporadic "Unroutable main domain" error

Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: Ludwig Meyerhoff
Fecha:  
A: Exim User's Mailing List
Asunto: Re: [exim] Sporadic "Unroutable main domain" error
Hallo!

Well, here are some example domains ...
hanser.de
gemline.com.tr
mmsship.com.tr
aceralialargos.com
digicom.bg


Here is the resolv.conf (192.168.1.10 is the server itself, do not
remember why I changed from localhost):
srv:/tmp# cat /etc/resolv.conf
search antar.de
nameserver 192.168.1.10
nameserver 194.25.2.129
nameserver 117.237.151.33


The forwarders-section of my BIND configuration is:
         forwarders {
           213.191.74.18;
           213.191.74.19;
           212.108.160.1;
          };




I had a look at older logfiles, the problem was already in february
(older logfiles archived), but noone noticed!
A deeper look in the mainlog results in many many incoming mails before
these errors, many local deliveries but no outgoing delivery.

As it were not the forwarders and it is not the reloading of the Bind
(12 minutes difference), the problem can be in a "deeper" configuration
of exim.



Could it be the 3000 mails in the spool (/var/spool/exim/input has 6000
files, one data and one header) - eximstats tells about 98.9% of the
emails remain under 1 min in the queue and 99.4% under 1h - just about
90 stay more.




Saluti!

Ludwig









Greg A. Woods wrote:
> [ On Wednesday, April 27, 2005 at 09:19:31 (+0200), Ludwig Meyerhoff wrote: ]
>
>>Subject: [exim] Sporadic "Unroutable main domain" error
>>
>>I run Exim 3.35 a small mailserver (static IP, "always on" since years)
>>since years, and everything went fine. Until last week, when outgoing
>>mails are bounced with the reason "unroutable mail domain".
>>When the users send the mail again after getting the bounce-message, the
>>delivery succeeds.
>
>
> Hmmm.... perhaps you could post both a list of some example domains
> your users are having trouble with, as well as the content of your
> /etc/resolv.conf
>
> (and open up your caching resolver(s) for public access, if they'er not
> already accessible, and at least temporarily so remote debugging can be
> done)
>
> Have you tried using some other caching resolver as a test, e.g. your ISP's?
>