Forums

Resolved
0 votes
Hello,

Fetchmail is working just fine, generally speaking. However, today I have this problem for the second time. Fetchmail stops collecting e-mails from my ISP. /var/mail/maillog gives these lines:
Jan 11 03:07:01 mailservercos7 fetchmail[1265]: Connection errors for this poll:#012name 0: connection to pop.xs4all.nl:pop3s ["MyOwnIP"/995] failed: No route to host.
Jan 11 03:07:01 mailservercos7 fetchmail[1265]: Query status=2 (SOCKET)


Somehow the IP of my ISP (pop.xs4all.nl) is resolved to my own local IP, leading to fetchmail's requests not reaching their destination.

Now I've had that once before, last December. It started overnight at 2:00AM and lasted exactly 24hours. Then after 24h the problem was gone and my e-mails poured in.

That time I checked the DNS settings in the Dashboard, refreshed a lot of things like DNS-servers, fetchmail and network settings, hoping it might lead to a refresh of the DNS settings. But it didn't help. Before I could post anything here, the 24h passed and the problem was solved. But today I have it again. What can I do to force ClearOS and Fetchmail to fix the DNS record?
Friday, January 11 2019, 09:06 AM
Share this post:

Accepted Answer

Friday, January 11 2019, 04:26 PM - #Permalink
Resolved
1 votes
See this for your ping and traceroute differences though it still looks odd.

Perhaps try adding a . after the domain name in fetchmail, although it probably won't take it. You can try editing the underlying file /etc/fetchmail.

Assuming ClearOS is doing your DNS, can you also try flushing the DNS caches with:
service dnsmasq restart
service nscd restart
The reply is currently minimized Show
Responses (3)
  • Accepted Answer

    Friday, January 11 2019, 09:48 PM - #Permalink
    Resolved
    0 votes
    Nick you're the greatest! Your suggestion helped!

    This wasn't the solution:
    service dnsmasq restart
    service nscd restart


    And adding the dot after the domain in Fetchmail wasn't accepted indeed.

    But manually editing /etc/fetchmail and adding the dot after pop.xs4all.nl immediately resolved the problem.

    I'm really grateful for your help, thank you!

    Any idea on why this randomly started and stopped being a problem?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, January 11 2019, 02:25 PM - #Permalink
    Resolved
    0 votes
    Hi Nick, thanks for helping out!

    From "host pop.xs4all.nl" I'm getting the exact same result as you.
    But when I do "traceroute pop.xs4all.nl" the resolved IP is the external IP of my own network, and the route obviously only needs one line.
    When I do a trace route on a complete different machine in my network, it obtains the correct IP (194.109.6.55) and delivers a normal route of several lines.

    Like I said, last time this happened during exactly 24h. I expect it to be over coming night. But I'd prefer to be able to solve it!
    The reply is currently minimized Show
  • Accepted Answer

    Friday, January 11 2019, 10:57 AM - #Permalink
    Resolved
    0 votes
    What do you get from "host pop.xs4all.nl"? I am getting:
    [root@server ~]# host pop.xs4all.nl
    pop.xs4all.nl has address 194.109.6.55
    pop.xs4all.nl has IPv6 address 2001:888:0:18::110
    pop.xs4all.nl mail is handled by 100 mx2.xs4all.nl.
    pop.xs4all.nl mail is handled by 100 mx3.xs4all.nl.
    pop.xs4all.nl mail is handled by 100 mx4.xs4all.nl.
    pop.xs4all.nl mail is handled by 100 mx1.xs4all.nl.
    The reply is currently minimized Show
Your Reply