Many thanks to the person who noticed the exposed password Nothing like being tired and ready to do something else after hours of pure frustration to breed carelessness. Getting that password changed was much easier said than done. I finally spoke with somebody who understood the problem well enough that it appears that the now defunct password just got changed. I have a cron job that kicks off every few minutes to do a pop session in fetchmail and it suddenly began generating system messages stating: From: root@localhost (Cron Daemon) Subject: Cron <martin@wb5agz> do_mail
fetchmail: Authorization failure on marti...@suddenlink.net@pop.altice.prod.cloud.openwave.ai fetchmail: For help, see http://www.fetchmail.info/fetchmail-FAQ.html#R15 I never thought I'd live to be happy to see that message. I was even happier when I put the new password in .fetchmailrc and it all started working again. The information about the certificate being expired was no surprise to me. Persuading this large corporation to part with a few Dollars to renew that certificate is about as likely as an Olympic ice skating contest on the frozen surface of hell, itself. On that day, nobody will see it because they will be too busy craning their necks to watch the pigs fly North for the Summer. If you are reading this message, they also changed the PW in the outgoing server. Until I can get exim4 v4.96 to be happy with sending the outgoing messages, I must still do it this way though. -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
