From: Matthias A. <mat...@gm...> - 2024-01-31 18:48:46
|
Am 29.01.24 um 17:49 schrieb Michael Burgoon: > Thanks very much Lucio. I reran fetchmail with your debug args and got the following output. the IPA for my internal mail server is 192.168.1.111 and that this the address that my router port forwards to. I do not have anything located at 192.168.1.203, the spa that is causing the error, so I’m at a loss as to why fetchmail now, all of a sudden, has decided to use that address for my internal mail/smtp server. > Question: where does fetchmail get that address to query? Wherever it is, it’s getting the wrong ipa. > > Thanks for anyone’s additional assistance. > > Mike B > > ++++++++++++++++++++++++++++++++++++++++++++++++++++ > > mburgoon@mbdiskstation:/opt/etc/init.d$ sudo /opt/bin/fetchmail -vvv --nodetach --nosyslog -f /opt/etc/fetchmailrc > Password: > fetchmail: WARNING: Running as root is discouraged. > gethostbyname failed for mbdiskstation > Name or service not knownCannot find my own host in hosts database to qualify it! > Trying to continue with unqualified hostname. > DO NOT report broken Received: headers, HELO/EHLO lines or similar problems! > DO repair your /etc/hosts, DNS, NIS or LDAP instead. Mike, ^ these warnings you quoted above are relevant. The host running fetchmail needs fixing. Also, your fetchmail is nine years old. Who is maintaining the software and providing bug fixes? What software is it? Some NAS? > [...] > Trying to connect to 192.168.1.203/25...connection failed. > fetchmail: connection to localhost:smtp [192.168.1.203/25] failed: No route to host. Why does your mail server believe that "localhost" has address 192.168.1.203? You write you don't have something there (that's what you intend), but your host running fetchmail that localhost isn't 127.0.0.1 (or possibly 127.0.1.1 on some systems), but 192.168.1.203, which is non-standard and probably part of the problem you are posing. This is an issue on your operating system on the fetchmail host - and you need to find out where that address comes from. Check your /etc/hosts on the host running fetchmail, and local name servers if any (including on your router). You may find out with (as root): grep -r 192.168.1.203 /etc Also, you did not tell fetchmail to your internal mail server - there is no smtphost argument or similar which would mention that 192.168.1.111 that you intend to use. Where you did intend this to happen? > # Edit carefully, see the fetchmail(1) manual page, section "THE RUN CONTROL FILE". > > poll pop.earthlink.net proto pop3 localdomains mindspring.com user"mbu...@mi..." password “XXXXXXXX", is "mbu...@mb...” here |