Control: tags -1 upstream confirmed fixed-upstream
Control: severity -1wishlist
Am 19.07.24 um 15:30 schrieb Manny:
Package: fetchmail
Version: 6.4.37-1
Severity: minor
Tags: upstream
X-Debbugs-Cc: debbug.fetchm...@sideload.33mail.com
This warning:
fetchmail: WARNING: pop.yandex.com configuration invalid, you normally need
--ssl for port 995/service pop3s.
is triggered by this configuration stanza:
poll pop.yandex.com
no dns
plugin "socat STDIO SOCKS4A:127.0.0.1:%h:%p,socksport=9050"
protocol pop3
port 995
username manny
sslproto 'SSL3+'
sslcertck
sslfingerprint "94:6A:CF:B1:A7:BE:30:11:B5:E0:B1:F9:0C:3B:37:B7"
fetchall
The 'SSL3+' is not accidental or arbitrary. It is there after a
struggle with the normal parameters (“ssl”) and experimentation found
SSL3+ was necessary in order to establish a connection. I stopped
using Yandex when they started blocking Tor years ago, so it’s unclear
whether “SSL3+” still needed. But that’s irrelevant anyway.
Thanks for the report.
The thing is fetchmail cannot assess what plugin you have, such for the
use with "plugin" - but you can probably omit the "port" line or change
it to "port 110".
I'll see (as upstream maintainer) if I can quench the warning and
related ones with plugin in use.
Fixed upstream in Git commit 98a71f86, repos on
gitlab.com/fetchmail/fetchmail and sf.net/projects/fetchmail branch
legacy_6x.
