himalaya
himalaya copied to clipboard
soywod
Using Himalaya with proxy
Discussed in https://github.com/soywod/himalaya/discussions/263
Originally posted by DhruvaSambrani November 18, 2021 My institute has a manual proxy setting that must be set for applications to connect to the internet. This has been a recent development, and all cli email clients seem to stop connecting to the email servers.
For neomutt, there was a closed issue for no one being interested in implementing the feature, and I have opened an issue for aerc.
Himalaya too doesn't seem to connect to email servers, despite having set http_proxy and https_proxy settings in /etc/environment. All other applications, like curl, work as expected. So, is this a lacking feature in Himalaya (and other clients) or does the NetAdmin have to open some port for email clients to connect?
@soywod So updates about the proxy. I think the NetAdmin has opened the IMAP port, and himalaya works (so does aerc, did not check neomutt) without any changes at all. I think you can close this issue then?
I think the NetAdmin has opened the IMAP port, and himalaya works
Glad to heart that!
I think you can close this issue then?
I still think it could be a good feature after the v1.0.0. Thunderbird seems to be able to propose HTTP, HTTPS, SOCKS v4 and v5 proxies:
