<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Bernd,<div class=""><br class=""></div><div class="">Are you specifically talking about a SOCKS proxy, or something else?</div><div class=""><br class=""></div><div class="">-Chris.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 3 Jan 2018, at 12:10, Bernd Eckenfels <<a href="mailto:ecki@zusammenkunft.net" class="">ecki@zusammenkunft.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><!-- This file has been automatically generated. See web/README.md -->
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div class="">
<div id="compose-container" style="direction: ltr" itemscope="" itemtype="https://schema.org/EmailMessage" class="">
<span itemprop="creator" itemscope="" itemtype="https://schema.org/Organization" class=""><span itemprop="name" content="Outlook Mobile for iOS" class=""></span></span>
<div class="">
<div style="direction: ltr;" class="">Hello,</div>
<div class=""><br class="">
</div>
<div style="direction: ltr;" class="">Just to add to the discussion, if proxies are used, the error should make clear if the problem is connecting the proxy or the endpoint. And for that case (especially with multiple proxies) the actual failed address is also interesting
for trouble shooting (in that case higher level code won’t have the information)</div>
<div class=""><br class="">
</div>
<div class="acompli_signature">
<div class="">Gruss</div>
<div class="">Bernd</div>
<div class="">-- </div>
<div class=""><a href="http://bernd.eckenfels.net" class="">http://bernd.eckenfels.net</a></div>
</div>
</div>
</div>
</div>
</div></blockquote></div><br class=""></div></body></html>