From: Rob F. <rf...@fu...> - 2007-03-19 17:16:08
|
Jochen Hayek wrote: > Trust me (pls!), neither explicit nor implicit sockisification > *usually* work out of the box, ie. w/o changing the code, > so somebody ("a user"), who "moves" into an enforced socks server > environment, will have to try / verify socksification on every single > application on its own, and not all at once by toggling the one and > only global switch. IMHO, the goal should be that configuring socks in one place makes it work everywhere. No, that's not the current situation, but if I need socks then that's what I want. Therefore, if I'm a user needing socks, I want to be able to set up socks.conf and have as much work with socks as possible. I don't want to have to look for --enable-socks runtime switches everywhere. So if fetchmail currently tries to use socks if you've set up socks.conf, then I think that's the right thing to do. If you don't want fetchmail to use socks, don't set up socks.conf. -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |