Re: Failure to connect with cox.net

On 02/12/2016 12:02 PM, James Moe wrote:
> Error Code=unknown secondary
> domain name
>
  This was due to a setting that was counter-productive. In
General::Other::TLS Sessions "Process Target Domain extensions" was set.
Poor choice.
  However, unsetting that feature has had no affect on accessibility by
cox.net.
  Below are other log entries which indicate a failure to connect. Note
the 15 minute timeout. These are all of the log entries for a typical
failure to connect.

12:30:06.677 2 IMAP-000377([72.208.72.31]) '[email protected]'
connected(CLRTXT) from [72.208.72.31]:42690(tls)

  -- wait for it --

12:45:16.962 3 IMAP-000377([72.208.72.31]) read failed. Error
Code=connection reset by peer
12:45:16.962 2 IMAP-000377([72.208.72.31]) '[email protected]'
disconnected ([72.208.72.31]:42690)

13:50:30.493 2 IMAP-000664([97.44.128.123]) '[email protected]'
connected(CLRTXT) from [97.44.128.123]:2161(tls)(temp client)

  -- wait for it --

14:05:46.504 3 IMAP-000664([97.44.128.123]) read failed. Error
Code=connection reset by peer
14:05:46.504 2 IMAP-000664([97.44.128.123]) '[email protected]'
disconnected ([97.44.128.123]:2161)

  Any ideas what may be causing this?

-- 
James Moe
jimoe at sohnen-moe dot com

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[email protected]>.
To unsubscribe, E-mail to: <[email protected]>
To switch to the DIGEST mode, E-mail to <[email protected]>
To switch to the INDEX mode, E-mail to <[email protected]>
Send administrative queries to  <[email protected]>