[Expired for fetchmail (Ubuntu) because there has been no activity for
60 days.]
** Changed in: fetchmail (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the report Bill and even more for the awesome and detailed
explanations Matthias!
AFAICS there is nothing in here for Ubuntu to fix "right now". As versions
6.5/7.0 are releases we will pick them up but that isn't what this bug was
about.
Gladly config based solutions were found to
I see that I overlooked the NEWS file. That's more detailed than I'm
used to seeing. As I was just now skimming through it, it was clear
that moves made to protect users from weak algorithms assumed they're on
an untunneled connection, which is not always the case. Sometimes the
SSL is just
Bill,
I can sense quite a deal of frustration on your end, and am sorry for
that. I should have mentioned to also look into the NEWS file, which at
least would have told you that sslcertck is now the default.
Fetchmail's -vv verbose mode might also try to log more details on the
decisions along
** Changed in: fetchmail (Ubuntu)
Status: Incomplete => New
--
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
I've also noticed that "auto" and "TLS1+" have the same meaning when
passed to --SSLPROTO. That's part of the problem. So now there is
duplication, and no way to get opportunistic crypto. If auto was
previously opportunistic, then the change to remove it should be rolled
back.
--
You received
I appreciate the quick response, but I have to say both of you
overlooked some of the data I presented, so I will elaborate. I was
able to workaround the bug, but there are still bugs here. Having read
the man page more times, I continue to find more anomalies than answers,
which I will
Hello Bill,
I agree with Matthias' reply: fetchmail seems to be working just as
expected. Also please note that we use this bug tracker to work on bugs
in Ubuntu, so feature requests like a per-account SOCKS4a config
parameter don't really fit here; at a first look the right venue would
be [1].
** Description changed:
Version 6.4.16 is unable to fetch mail from the underwood onion site.
This is the output when trying to connect:
fetchmail: normal termination, status 2
fetchmail: 6.4.16 querying underwood-onion (protocol IMAP) at Wed 30 Jun 2021
02:10:52 PM UTC: poll started
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
** Description changed:
Version 6.4.16 is unable to fetch mail from the underwood onion site.
This is the output when trying to connect:
fetchmail: normal termination, status 2
fetchmail: 6.4.16 querying underwood-onion (protocol IMAP) at Wed 30 Jun 2021
02:10:52 PM UTC: poll started
11 matches
Mail list logo
