HMMM
As of 20170827 I do not seem to be able to setup a new POP receiving account in mail using the Spectrum - TWC documented settings for port 110.
Attempted it on at least half a dozen tries over a four hour period.
The following occurs.
I ran a similar log for a POP receiving account for earthlink and it appears to me that all the login traffic is "missing" after the CAPA read - my question is - is mail at fault for NOT providing the proper user and password responses at this point - or is the twc mail server.
This account is presently working just fine with an IMAP receiving account in mail.
SMTP for sending is working just fine also in mail.
INITIATING CONNECTION Aug 25 11:54:38.755 host:mail.twc.com -- port:110 -- socket:0x0 -- thread:0x############[thread numbers removed]
CONNECTED Aug 25 11:54:38.796 [kCFStreamSocketSecurityLevelNone] -- host:mail.twc.com -- port:110 -- socket:0x6080004affc0 -- thread:0x############
READ Aug 25 11:54:38.838 [kCFStreamSocketSecurityLevelNone] -- host:mail.twc.com -- port:110 -- socket:0x6080004affc0 -- thread:0x############
+OK InterMail POP3 server ready.
WROTE Aug 25 11:54:38.838 [kCFStreamSocketSecurityLevelNone] -- host:mail.twc.com -- port:110 -- socket:0x6080004affc0 -- thread:0x############
CAPA
READ Aug 25 11:54:38.880 [kCFStreamSocketSecurityLevelNone] -- host:mail.twc.com -- port:110 -- socket:0x6080004affc0 -- thread:0x############
+OK Capability list follows
TOP
USER
RESP_CODES
PIPELINING
EXPIRE NEVER
UIDL
IMPLEMENTATION Openwave Email vM.8.04.03.24 201-2389-100-172-20151028
.
WROTE Aug 25 11:54:38.881 [kCFStreamSocketSecurityLevelNone] -- host:mail.twc.com -- port:110 -- socket:0x6080004affc0 -- thread:0x############
QUIT