Re: SSL error

"Joe Acquisto-j4" <[email protected]>
Newsgroups gmane.mail.fetchmail.user
Message-ID <611A6209020000850006C8C3@mail>
> Am 16.08.21 um 01:45 schrieb Joe Acquisto-j4:
>>
>>>> Version 6.4.2-rc3+SSL-SSLv2-SSLv3+NLS
>>>>
>>>> Recent ping about SSL issue cause me to look at config and logs.   Surprise.
>>>>   Been going on for months.  My bad for not noticing earlier.
>>>>
>>>> from /var/log/fetchmail.log
>>>>
>>>> fetchmail: Loaded OpenSSL library 0x1010104f newer than headers 0x1010009f,
>>>> trying to continue.
>>>> fetchmail: OpenSSL reported: error:1408F10B:SSL
>>>> routines:ssl3_get_record:wrong version number
>>>>
>>>> I'll search a bit while awaiting the lifeguards . . .
>>>>
>>> Updating to absolute latest on sourceforge resolved the issue.
>>>
>>> Pardon the noise.
>>>
>> Actually . . . I lied.  Secure connections do appear to work, if I leave 
> config options at default,
>> but when I add "ssl" to my config file the particular user I add that for 
> shows this error on attempted fetch:
>>
>> "fetchmail: OpenSSL reported: error:1408F10B:SSL 
> routines:ssl3_get_record:wrong version number"
>>
>> Sorry if this is an added burden, or, horrors, if I misread earlier emails 
> on the subject.
> 
> Joe,
> 
> this is a typical situation when OpenSSL tries to negotiate SSL on a
> port that talks plaintext.
> 
> If you configured the port explicitly, then you need to change it, too,
> to the SSL-wrapped version (POP3 --ssl will use 995, IMAP --ssl will use
> 993) or just remove the --port or --service parameter and go with the
> defaults (if your ISP serves on the usual port, that will be sufficient).
> - else see https://www.fetchmail.info/fetchmail-FAQ.html#G3 for what
> information we need to help you.
> 
> Also, your fetchmail was compiled with OpenSSL 1.1.0i headers and uses a
> run-time library 1.1.1d. This is a strange situation. If you built
> fetchmail yourself, make sure your system is fully updated and then
> clean and rebuild fetchmail.
> 
> Regards,
> Matthias
> 

Thank you.  Removing the port parameter eliminated the error.   Sorry for the bother.

I will look into the OpenSSL mismatch you noticed.

joe a.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.