From: <dv...@in...> - 2021-03-29 07:15:26
|
On 28.03.21 20:22, Matthias Andree wrote: > There are two ways out here for you: > > 1. The good one is adding "ssl". That makes fetchmail connect to port > 995 and talk TLS right away (SSL-wrapped or TLS-wrapped mode) and is > what I'd recommend. That worked fine, so no need for the bad one. :-) > 2. The bad one, and I shall clearly discourage that, is adding > nosslcertck (this defeats man-in-the-middle eavesdropping protection). > > > In about 30 years of fetchmail use, I've completely forgotten what it > > is tohave an email fetch issue. This is quite novel. > > Thanks for the honors for ESR, but fetchmail is only 25 years old and > even with popclient it's not sure we get to 30. ;-) Yes, 12 yrs in last job, 12 yrs retired, so it's 24 tears tops that I've used fetchmail, on reflection. Just finished a 2 year rural off-grid owner-build last Monday - that makes everything beforehand seem further in the past, I kid you not. Many thanks for the fix. I would not have guessed that turning SSL on would make the problem go away, but can see it now, I'll make notes. Erik |