From: Joe Acquisto-j. <jo...@j4...> - 2020-02-05 19:10:08
|
>Checked that "less secure" apps was still enabled. Did find some "security > warnings" about suspicious access attempts and approved them. That did not > resolve the issue. >> >> Many indications on the web that gmail is particularly reluctant to play > nice with others. >> >> FWIW there are several accounts defined in the same fetchmailrc file at > another provider that work just fine in the same fetch cycle. > > If Ralph's answer (try ssl) doesn't help, we're at the point where it > boils down to the canned answer, please provide output per > <https://www.fetchmail.info/fetchmail-FAQ.html#G3> and mask your > passwords. Generally I'd say, however, that a timeout < 30 s might be > fraught with problems. > Well . . . oops? Don't know how I missed the port issue. At some point the "ssl" option was deleted from the user line. That resolved the connection failure. Working after a few fetch cycles and chasing a gmail issue. The ssl fingerprint seems to change, seemingly with what IP it happens to connect. While I do find almost immediate response when connecting (human eyeball time) I set the timeout to 30 for the moment. Thanks for the assistance, I'll look into improving the ssl business. joe a. |