#1076604 fetchmail: “configuration invalid, you normally need --ssl for port 995” ← probably incorrect msg

Package:
fetchmail
Source:
fetchmail
Description:
SSL enabled POP3, APOP, IMAP mail gatherer/forwarder
Submitter:
Manny
Date:
2024-07-20 09:30:02 UTC
Severity:
normal
Tags:
#1076604#5
Date:
2024-07-19 13:30:25 UTC
From:
To:
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.

The problem is that fetchmail is making a false assertion. It’s a
nuance of English but fetchmail cannot know for certain if this stanza
is an “invalid” config. The warning should probably be rephrased to
say something like “the configuration is unusual and possibly
incorrect…” And even then, it’s a bit annoying to see this warning
every invocation. IMO it would be more appropriate to put the warning
in the logs, not print to the screen. Or perhaps have a separate CLI
option just for checking the config file.
#1076604#10
Date:
2024-07-20 09:23:12 UTC
From:
To:
Am 19.07.24 um 15:30 schrieb Manny:

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.
#1076604#17
Date:
2024-07-20 09:23:12 UTC
From:
To:
Am 19.07.24 um 15:30 schrieb Manny:

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.