From: Stefano <fet...@po...> - 2008-03-16 05:24:57
|
Evidently, I should have looked more closely at the latest development code in the repository. The particular problem I was having does indeed appear to have been fixed in BRANCH_6-3 (checked it out and built a few hours ago). However, is there not a chance that a similar problem will return in the event that the "defeat opportunistic STLS" block *is* executed? It seems that the only thing that was done is to avoid going through that block in the particular case of a required re-poll when an opportunistic STLS negotiation was not attempted. Without changing the sslproto = "" aspect of that block, or the handling in socket.c, does the potential for the problem to return not remain? Quoting Matthias Andree <mat...@gm...>: > On Sat, 15 Mar 2008, Stefano wrote: > >> I recently installed Fetchmail (6.3.8) to collect my mail from various >> accounts, so that they could be automatically filtered and sorted. Since >> installation, I had been getting the following error whenever it polled >> my ISP's server (POP3): >> >> Invalid SSL protocol '' specified, using default (SSLv23). >> >> This does not happen when accessing other IMAP servers, but they don't >> support IMAP. Given that I had added a cron job to check the accounts >> periodically, I kept receiving messages from the cron daemon with these >> errors; rather irritating. Thus began my quest to track down and >> silence the error. > > Well, try the attached patch and see if it helps, it's actually simpler. > > If the NEWS or TODO.txt parts of the patch fail, nevermind. > >> I had read about this problem while trying to solve it, but it didn't >> seem to have been fixed in the latest development code, so I took a stab >> at it. > > It should be fixed in the SVN repository though, > > http://mknod.org/svn/fetchmail/branches/BRANCH_6-3/ > > (That's where my patch comes from.) > > If not, we'll check again how to fix this. > > Thanks a lot for your report and patch! > > -- > Matthias Andree > |