You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here how I see the thing: every time we build a TPC connection (IMAP and SMTP), we need to apply the right proxy according to given proxy URL. It can be HTTP(S), SOCKS4 or SOCKS5. The proxy URL is taken from http_proxy and https_proxy env vars by default, and we can add a global config entry proxy-url or proxy that overrides this behaviour. Here an example on how to set up the socks proxies, and here an example on how to use the HTTP ones.
The text was updated successfully, but these errors were encountered:
Hi @soywod . I wonder if anyone has claimed the development of proxy feature. I do like to use Himalaya to manage emails but, personally, I need SMTP connection over socks5 proxy to one of my 'special' mail account.
Unfortunately this task is not a priority, there is so much to do before. But I definitely plan to develop the feature. If I'm in advance on my planning, I will give it a shot. Stay tuned!
Here how I see the thing: every time we build a TPC connection (IMAP and SMTP), we need to apply the right proxy according to given proxy URL. It can be HTTP(S), SOCKS4 or SOCKS5. The proxy URL is taken from
http_proxy
andhttps_proxy
env vars by default, and we can add a global config entryproxy-url
orproxy
that overrides this behaviour. Here an example on how to set up the socks proxies, and here an example on how to use the HTTP ones.The text was updated successfully, but these errors were encountered: