We finally solved the problem. For some reason dovecot stopped accepting mail.sgeinc.com but wanted sge.sgeing.com, the real name of the machine, not an alias name with the same IP address. Why it was going for ssh-keygen we don't know.
On 3/3/2024 3:28 AM, Odhiambo Washington wrote:
On Sun, Mar 3, 2024 at 1:46 AM Richard Shetron <guest2@sgeinc.com <mailto:guest2@sgeinc.com>> wrote:
Hello, My sysadmin and I spent a couple hours trying to figure out a POP3 problem that has worked for about 20 or so years. We run our own dns for sgeinc.com <http://sgeinc.com>. I've always used mail.sgeinc.com <http://mail.sgeinc.com> as my incoming and outgoing server. At various times mail has been an alias for another machine. It's currently on the same address as sge.sgeinc.com <http://sge.sgeinc.com>. On the update forced on us on 2/22/24 or 2/23/24 it stopped working. It still works as an outgoing server but incoming POP3 it stopped working. It started working when I changed my incoming server to sge.sgeinc.com <http://sge.sgeinc.com>. You might want to look into it or not. We chased the initial problem to, we think, ssh-keygen in /usr/local/bin/ which was Not found but is there.Why would dovecot need ssh-keygen? What for?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html <http://www.catb.org/~esr/faqs/smart-questions.html>]