Re: EarthLink issue
Michael Burgoon <[email protected]> Mon, 29 Jan 2024 11:49:12 -0500
| Newsgroups | gmane.mail.fetchmail.user |
|---|---|
| Message-ID | <[email protected]> |
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. Old UID list from pop.earthlink.net: <empty> Scratch list of UIDs: <empty> fetchmail: 6.3.26 querying pop.earthlink.net (protocol POP3) at Mon, 29 Jan 2024 16:34:57 +0000 (UTC): poll started Trying to connect to 24.41.66.181/110...connected. fetchmail: POP3< +OK NGPopper vEL_0_1_42_MP_1_P at earthlink.net ready <[email protected]> fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< apop fetchmail: POP3< pass fetchmail: POP3< top fetchmail: POP3< uidl fetchmail: POP3< user fetchmail: POP3< . fetchmail: POP3> USER [email protected] fetchmail: POP3< +OK Pass required for [email protected] fetchmail: POP3> PASS * fetchmail: POP3< +OK mburgoon has 25 messages (35879814 octets). fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 25 35879814 fetchmail: POP3> LAST fetchmail: POP3< +OK 0 25 messages for [email protected] at pop.earthlink.net (35879814 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< +OK 1 19510 fetchmail: POP3> TOP 1 99999999 fetchmail: POP3< +OK reading message [email protected]@pop.earthlink.net:1 of 25 (19510 octets) About to rewrite Return-Path: <[email protected]>... ...rewritten version is Return-Path: <[email protected]>. About to rewrite Sender: [email protected]... ...rewritten version is Sender: [email protected]. About to rewrite From: Jerrys Leesburg Chevrolet <[email protected]>... ...rewritten version is From: Jerrys Leesburg Chevrolet <[email protected]>. About to rewrite To: [email protected]... ...rewritten version is To: [email protected]. 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. fetchmail: Connection errors for this poll: name 0: connection to localhost:smtp [192.168.1.203/25] failed: No route to host. fetchmail: SMTP connect to localhost failed fetchmail: POP3> QUIT fetchmail: POP3< <!DOCTYPE html> fetchmail: SMTP transaction error while fetching from [email protected]@pop.earthlink.net and delivering to SMTP host localhost fetchmail: 6.3.26 querying pop.earthlink.net (protocol POP3) at Mon, 29 Jan 2024 16:35:01 +0000 (UTC): poll completed Merged UID list from pop.earthlink.net: <empty> fetchmail: Query status=10 (SMTP) fetchmail: normal termination, status 10 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ FETCHMAILRC # Edit carefully, see the fetchmail(1) manual page, section "THE RUN CONTROL FILE". poll pop.earthlink.net proto pop3 localdomains mindspring.com user "[email protected]" password “XXXXXXXX", is "[email protected]” here +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On Jan 27, 2024, at 8:09 AM, Lucio Chiappetti <[email protected]> wrote: On Fri, 26 Jan 2024, Michael Burgoon wrote: > explain where the following statements go: > > The output of env LC_ALL=C fetchmail -V called with whatever other command-line options you used. > The output of env LC_ALL=C fetchmail --nodetach -vvv --nosyslog with whatever other command-line options you use routinely. The statements shall be issued from a terminal emulator (xterm, console etc.). It depends how you call procmail (as a daemon, or via crontab, whether you use .fetchmailrc or a custom .fetchmailrc.SOMETHING (for instance I had two (now three) different .fetchmailrc.SOMETHING fopr different servers, and call by crontab at different frequencies. If I wanto to debug a particular .fetchmailrc.SOMETHING fetchmail -V -v --nodetach --nosyslog -f /path/to/.fetchmailrc.SOMETHING will analyse the .fetchmailrc.SOMETHING for syntax errors (and do nothing) fetchmail -vvv --nodetach --nosyslog -f /path/to/.fetchmailrc.SOMETHING will executw it and produce verbose diagnostic messages. It's all written in the man pages (where I found it recently when I needed to make checks for a new server) -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ A middle rank researcher at end career is not rich but is in the top 5% of the Italian income tax taxpayers. Does it not sound strange ? _______________________________________________ Fetchmail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fetchmail-users