broken fetchmail configuration

I'm attempting to set up fetchmail on my OSX 10.5.6 box. I've arrangement my.fetchmailrc as adheres to:

poll with proto IMAP 
timeout 30
user "username" is "username" here options ssl keep 

I'm making use of a.netrc documents to store my usernames/passwords as so:

login username
password secret

However, when I run fetchmail I get the adhering to mistake:

reading message [email protected]:1 of 458 (4436 octets)
fetchmail: timeout after 30 seconds waiting for listener to respond.
fetchmail: socket error while fetching from [email protected] and delivering to SMTP host localhost
fetchmail: Query status=2 (SOCKET)
fetchmail: Server certificate verification error: unable to get local issuer certificate
fetchmail: Server certificate verification error: certificate not trusted
fetchmail: Server certificate verification error: unable to verify the first certificate
fetchmail: Error exchanging credentials

It appears fetchmail can login alright yet it falls short to supply anything to postfix (which I've validated is up and also running by telnetting to localhost:25).

Next I conjured up fetchmail with - vv flags to get some added details concerning what is taking place. I see the adhering to weird message:

Trying to connect to timeout after 5 seconds waiting for listener to respond.
fetchmail: 6.3.8 querying (protocol POP3) at Tue, 14 Jul 2009 18:20:09 +1000 (EST): poll completed
fetchmail: discarding new UID list
fetchmail: Query status=2 (SOCKET)

That IP address is really weird. Should not fetchmail just be attempting to connect to localhost for message distribution? A fast nslookup discloses the target host domain name is one jankymail - wtf?

This is all with out - of - the - box fetchmail install btw - - it is an all new iMac! Does any person have a suggestion what could be taking place or what I'm doing incorrect?

2022-06-07 14:30:33
Source Share
Answers: 1

Add the alternative: smtphost localhost or perhaps smtphost to inform it to supply to localhost. I have no suggestion why it is failing to another thing (is that your whole fetchmail config?).

In fact, that might be it trying to make use of ETRN or something ; that IP settles to jankymail - is that your mail web server?

Additionally, you might require the sslcommonname or sslfingerprint alternative if the certification is either self - authorized or does not match the hostname.

2022-06-07 14:45:09