Bill,
as to your report, I'll break it down along the same bug numbers.
Note I am speaking as the upstream maintainer here and am unaware of Ubuntu's
Bug #1. Fetchmail behaves properly. You requested some sslproto on a
non-wrapped port (i. e. no "ssl" option), so fetchmail tries STARTTLS
instead, which then fails. I suggest you re-read the manual for the
relevant options that you are using and potential references from those
options to others, if any. This is deliberately worded quite vaguely.
Bug #2 fetchmail has a 'login or authentication' error it cannot spell
out in more detail for you, hence "unknown". Feel free to propose a
better wording.
3a. I suggest you read the section "SOCKS" of the manual page. New
options are quite high maintenance and I can't test them upstream for
lack of socks proxies.
3b. From your earlier report [*] I suppose you might get away with
something such as:
poll underwood2hj3pwd.onion via 127.0.0.1
plugin "socat STDIO SOCKS4A:127.0.0.1:%h:%p,socksport=9050"
# other options here
_____
[*] https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1924609
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934155
Title:
fetchmail can no longer connect to underwood & gives false error msg
(TLS issues)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1934155/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
