Re: Failure to connect with cox.net

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/15/2016 01:09 PM, Bill Cole wrote:
>>> However, unsetting that feature has had no affect on
>>> accessibility by cox.net. Below are other log entries which
>>> indicate a failure to connect.
> Au contraire, they indicate *SUCCESSFUL* connections. Really.
> 
  Hmm, okay. Thanks.
  I have set the logging to a more verbose level. All I have to do now
is convince the affected user to send mail so I can have log entries
to ponder (the user does not seem overly eager to resolve the issue).

- -- 
James Moe
moe dot james at sohnen-moe dot com
520.743.3936
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlbEt9MACgkQzTcr8Prq0ZO54ACfTgWodZldij3p85CupvLVPvIN
regAoIzFSdMSFDlg4/Qh//MV8qlBI+vZ
=BOxJ
-----END PGP SIGNATURE-----

#############################################################
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]>