thanks for the various answers. I've got quite a complex network setup and couldn't test it yet. I managed to get the VPN work thus so far I fetch mails via the VPN but I intend to try your solution later on.
Thanks for the great tool. Best regards Matt Le dim. 21 juil. 2019 à 04:40, synflower--- via isync-devel <isync-devel@lists.sourceforge.net> a écrit : > > On Sat, Jul 20, 2019 at 12:26:57PM +0200, Oswald Buddenhagen wrote: > >On Sat, Jul 20, 2019 at 05:55:20AM -0400, synflower--- via isync-devel wrote: > >> The lack of proxy support in mbsync does seem a glaring omission. > >> > >given the available solutions, i'm not sure what exactly would justify > >this bold statement. also, for which proxy protocol would you want to > >implement direct support in mbsync? http, socks, tor, i2p, ssh, *all* of > >them? > > Using an HTTP proxy is not relevant since we are not emitting HTTP > traffic. > > SOCKS5 would be enough -- once you have SOCKS5 support you can use Tor, > SSH, etc. It's not a high priority feature, but given that msmtp > supports SOCKS natively I was rather surprised to find this absent from > mbsync/isync, and spend a fair bit of time paging through the > documentation vainly looking for the appropriate configuration lines! > > At the very least it may be worth adding a note to the documentation that > `torsocks` (or another solution) is the recommended way of using mbsync > in situations that require a proxy. > > > _______________________________________________ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
