Re: [msmtp-users] Proxy support patch

[grarpamp <grarpamp@...20...>]

On Fri, Oct 3, 2014 at 1:23 PM, CustaiCo <custaico@...373...> wrote:
> I've written an patch that allows msmtp to use a socks

Good to see someone working on this.

Is it necessary to invoke new dependencies on third party libraries?
Especially one that hasn't been maintained since 2005?
What about simply including socks5 in msmtp directly?

You could borrow a socks5 + IPv6 implementation from...

A tool with 3-clause BSD license:
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/nc/

A tool with GPL + restrictions, has some win/mac code:
https://svn.nmap.org/nmap/ncat/

Other tools:
http://www.dest-unreach.org/socat/
http://www.privoxy.org/

http://en.wikipedia.org/wiki/SOCKS

> or html proxy.

It's known as an "HTTP[S] CONNECT" proxy rather than "html" proxy.

> It does support tls, but only using gnutls.

Is anyone actually using TLS/GSSAPI in the socks5 client-server path?

I'd suggest in order of likely usage priority...
- socks5, with IPv6, with DNS through it not leaked around it, auth.
- HTTPS and HTTP CONNECT.
- socks4a, DNS through, auth.

The patch has dos CRLF instead of unix CR at line end.

Replied because socks5 + IPv6 in msmtp (and even mpop) would be
cool and I think this might be the first work towards that :)

I'm sure there are lots of users who will point it directly at Tor
127.0.0.1:9050 so they can reach submission STARTTLS 587 on the
other side. Same for I2P. And their respective hidden services.

Another code reference...
https://gitweb.torproject.org/torsocks.git