"Wontfix" is probably the most fitting status of the possibilities that
are given.
I would have reported upstream if it didn't require using gitlab.com
(which pushes CAPTCHAs). Upstream forges often appear in unusable or
controversial places like github or gitlab.com, which actually
discourages
Thank you for your report.
This does not seem likely to be a bug in Ubuntu's packaging of fetchmail
to me, so since there is unlikely to be any action to take in Ubuntu
itself on this, I'm marking the bug task representing the fetchmail
package in Ubuntu as Won't Fix to make this clear. Rather,
///scenario 3: using mapaddress (requires root or tor controller
access)///
With this configuration:
```
poll uw via 10.40.40.46
protocol imap
port 993
username "billyikes"
fetchall
```
/etc/tor/torrc:
```
mapaddress 10.40.40.46 underwood2hj3pwd.onion
```
the
///scenario 1: using torsocks///
With this configuration:
```
poll uw via underwood2hj3pwd.onion
protocol imap
port 993
username "billyikes"
fetchall
```
the terminal output is:
```
$ torsocks fetchmail uw
1618601733 ERROR torsocks[16571]: Unable to resolve.
Bill, fetchmail relies on the system resolver so if that cannot resolve
.onion hosts, that's bound to fail. You are not telling fetchmail to
avoid name resolution.
Please provide information how exactly and which fetchmail version fails
in your << poll underwood2hj3pwd.onion plugin "socat STDIO
