More trouble with Spectrum POP3

bhenry004

posted 2 days ago at 3:15 pm

This has been a recurring problem but recently has gotten worse. I know Spectrum is screwing around with their servers but it's becoming more difficult to connect to their mail.twc.com for POP3 mail. Connection is intermittent in that I can connect once and 5 minutes later it won't connect. Here's what I get most often.

08:04:19.986: --- 7 Nov 2026, 8:04:19.986 ---
08:04:19.986: Connect to 'mail.twc.com', timeout 15 seconds, flags 16842753.
08:04:21.006: [*] Setting SNI hostname to 'mail.twc.com'
08:04:36.047: [!] OpenSSL timed out during handshake.

I've been reading that they don't support TLS 1.3. Does Pegasus use TLS 3.1 to connect? Can it be forced to connect with TLS 1.2 which Spectrum supports?

Any other suggestions?

It looks like this answers my question. Looks like TLS 1.2 is being used.

Here's a more recent successful attempt 14 minutes from the first failure:

08:16:07.640: --- 7 Nov 2026, 8:16:07.640 ---
08:16:07.655: Connect to 'mail.twc.com', timeout 15 seconds, flags 16842753.
08:16:08.901: [] Setting SNI hostname to 'mail.twc.com'
08:16:09.041: [] SSL/TLS session established
08:16:09.041: [] AES256-SHA256, TLSv1.2, Kx=RSA, Au=RSA, Enc=AES(256), Mac=SHA256<lf>
08:16:09.041: [] Peer's certificate name is '/C=US/ST=Missouri/L=St. Louis/O=Charter Communications Operating, LLC/CN=pkvw-mx.msg.pkvw.co.charter.net'.
08:16:09.062: >> +OK InterMail POP3 server ready.<cr><lf>
08:16:09.062: << USER xxxxxxxx@rochester.rr.com<cr><lf>
08:16:09.136: >> +OK please send PASS command<cr><lf>
08:16:09.136: << PASS xxxxxxxx<cr><lf>
08:16:09.199: >> +OK xxxxxxxx@rochester.rr.com is welcome here<cr><lf>
08:16:09.204: << STAT<cr><lf>
08:16:09.264: >> +OK 1 103002<cr><lf>
08:16:09.264: << LIST<cr><lf>
08:16:09.328: >> +OK 1 messages<cr><lf>
08:16:09.328: >> 1 103002<cr><lf>
08:16:09.328: >> .<cr><lf>
08:16:09.328: << RETR 1<cr><lf>
08:16:09.399: >> +OK 103002 octets<cr><lf>
08:16:09.662: << DELE 1<cr><lf>
08:16:09.728: >> +OK<cr><lf>
(… Mail was successfully retrieved)
08:16:09.728: << QUIT<cr><lf>
08:16:09.805: >> +OK xxxxxxxx@rochester.rr.com InterMail POP3 server signing off.<cr><lf>
08:16:09.821: [*] OpenSSL secure session normally terminated.
08:16:09.821: --- Connection closed at 7 Nov 2026, 8:16:09.821. ---
08:16:09.821:

This has been a recurring problem but recently has gotten worse. I know Spectrum is screwing around with their servers but it's becoming more difficult to connect to their mail.twc.com for POP3 mail. Connection is intermittent in that I can connect once and 5 minutes later it won't connect. Here's what I get most often. 08:04:19.986: --- 7 Nov 2026, 8:04:19.986 --- 08:04:19.986: Connect to 'mail.twc.com', timeout 15 seconds, flags 16842753. 08:04:21.006: [*] Setting SNI hostname to 'mail.twc.com' 08:04:36.047: [!] OpenSSL timed out during handshake. I've been reading that they don't support TLS 1.3. Does Pegasus use TLS 3.1 to connect? Can it be forced to connect with TLS 1.2 which Spectrum supports? Any other suggestions? It looks like this answers my question. Looks like TLS 1.2 is being used. Here's a more recent successful attempt 14 minutes from the first failure: 08:16:07.640: --- 7 Nov 2026, 8:16:07.640 --- 08:16:07.655: Connect to 'mail.twc.com', timeout 15 seconds, flags 16842753. 08:16:08.901: [*] Setting SNI hostname to 'mail.twc.com' 08:16:09.041: [*] SSL/TLS session established 08:16:09.041: [*] AES256-SHA256, TLSv1.2, Kx=RSA, Au=RSA, Enc=AES(256), Mac=SHA256<lf> 08:16:09.041: [*] Peer's certificate name is '/C=US/ST=Missouri/L=St. Louis/O=Charter Communications Operating, LLC/CN=pkvw-mx.msg.pkvw.co.charter.net'. 08:16:09.062: >> +OK InterMail POP3 server ready.<cr><lf> 08:16:09.062: << USER xxxxxxxx@rochester.rr.com<cr><lf> 08:16:09.136: >> +OK please send PASS command<cr><lf> 08:16:09.136: << PASS xxxxxxxx<cr><lf> 08:16:09.199: >> +OK xxxxxxxx@rochester.rr.com is welcome here<cr><lf> 08:16:09.204: << STAT<cr><lf> 08:16:09.264: >> +OK 1 103002<cr><lf> 08:16:09.264: << LIST<cr><lf> 08:16:09.328: >> +OK 1 messages<cr><lf> 08:16:09.328: >> 1 103002<cr><lf> 08:16:09.328: >> .<cr><lf> 08:16:09.328: << RETR 1<cr><lf> 08:16:09.399: >> +OK 103002 octets<cr><lf> 08:16:09.662: << DELE 1<cr><lf> 08:16:09.728: >> +OK<cr><lf> (… Mail was successfully retrieved) 08:16:09.728: << QUIT<cr><lf> 08:16:09.805: >> +OK xxxxxxxx@rochester.rr.com InterMail POP3 server signing off.<cr><lf> 08:16:09.821: [*] OpenSSL secure session normally terminated. 08:16:09.821: --- Connection closed at 7 Nov 2026, 8:16:09.821. --- 08:16:09.821:

edited 2 days ago at 3:27 pm

msetzerii

posted 2 days ago at 5:32 pm

Possible solution using stunnel.

Could not find option in Pegasus to do it.
stunnel.conf entries.

[spectrum-pop3]
client = yes
accept = 127.0.0.1:110
connect = mail.twc.com:995
sslVersionMin = TLSv1.2
sslVersionMax = TLSv1.2

[spectrum-smtp]
client = yes
accept = 127.0.0.1:25
connect = mail.twc.com:587
protocol = smtp
sslVersionMin = TLSv1.2
sslVersionMax = TLSv1.2

I've used stunnel for a long time with Pegasus Mail.
Pegasus thinks it connects to the local ports, and stunnel makes the secure connection to server.

https://www.stunnel.org/

Hope that helps.

Possible solution using stunnel. Could not find option in Pegasus to do it. stunnel.conf entries. [spectrum-pop3] client = yes accept = 127.0.0.1:110 connect = mail.twc.com:995 sslVersionMin = TLSv1.2 sslVersionMax = TLSv1.2 [spectrum-smtp] client = yes accept = 127.0.0.1:25 connect = mail.twc.com:587 protocol = smtp sslVersionMin = TLSv1.2 sslVersionMax = TLSv1.2 I've used stunnel for a long time with Pegasus Mail. Pegasus thinks it connects to the local ports, and stunnel makes the secure connection to server. https://www.stunnel.org/ Hope that helps.

mikes@guam.net

Brian Fluet

posted 2 days ago at 5:55 pm

@bhenry004 , I routinely receive the same connection failure when POP3ing my Spectrum accounts. It is transient for me. I believe the problem is due to unresponsive Spectrum servers (over whelmed? under resourced?).

Have you heard or been told the Spectrum no longer provides email service? What I was told is that it not available to new customers and will be discontinued for existing accounts at some point. I was told this by customer service after my two accounts were disabled and I pitched a fit over the lack of notice and the absolute need for service while transitioning away. They enabled them with the caveat that they could be discontinued again at any time. That was about two years ago. Mine still work but I no longer depend on them. That conversation led me to believe that Spectrum is not directing resources to email maintenance.

@bhenry004 , I routinely receive the same connection failure when POP3ing my Spectrum accounts. It is transient for me. I believe the problem is due to unresponsive Spectrum servers (over whelmed? under resourced?). Have you heard or been told the Spectrum no longer provides email service? What I was told is that it not available to new customers and will be discontinued for existing accounts at some point. I was told this by customer service after my two accounts were disabled and I pitched a fit over the lack of notice and the absolute need for service while transitioning away. They enabled them with the caveat that they could be discontinued again at any time. That was about two years ago. Mine still work but I no longer depend on them. That conversation led me to believe that Spectrum is not directing resources to email maintenance.

msetzerii

posted 2 days ago at 6:17 pm

In my research, it seems is a know issue. If a connection tries to make connection with TLS 1.3, it is suppose to then try TLS 1.2, but for some reason the spectrum is just closing connection.

Another thing to add. In the stunnel.conf it uses local ports 110 and 25, but you can use other ports. I have 3 setups, so use different ports for each one.

In my research, it seems is a know issue. If a connection tries to make connection with TLS 1.3, it is suppose to then try TLS 1.2, but for some reason the spectrum is just closing connection. Another thing to add. In the stunnel.conf it uses local ports 110 and 25, but you can use other ports. I have 3 setups, so use different ports for each one.

mikes@guam.net

Brian Fluet

posted 2 days ago at 7:37 pm

Regarding the specific question about TLS 1.3 / 1.2, I don't think there is a way to choose.

Also just confirmed... a POP3 to mail.twc.com using port 110 with no SSL still works. Keep in mind that if you create a new POP3 definition to test this it will retrieve all mail in the host inbox unless you use one of the options that checks but doesn't download.

Regarding the specific question about TLS 1.3 / 1.2, I don't think there is a way to choose. Also just confirmed... a POP3 to mail.twc.com using port 110 with no SSL still works. Keep in mind that if you create a new POP3 definition to test this it will retrieve all mail in the host inbox unless you use one of the options that checks but doesn't download.

msetzerii

posted 1 day ago at 9:27 pm

Outgoing (SMTP) mail.twc.com 587 STARTTLS (or SSL/TLS)
Incoming (POP3) mail.twc.com 110 or 995 STARTTLS / SSL

Don't know if the 110 is available from any IP. Long ago, my ISP allowed use of 25 and 110 ports, but only from IPs in there local network. If connecting via another network, you had to use the SSL ports.

Did also see info that new accounts not getting email, and phasing out of others??

So, with Stunnel option, Pegasus sees the local port with no encryption, and stunnel maps and encrypts it to host.

My lines for my gmail connections (using apppassword)
Bold lines are extra options and linux options, and don't use the 110 or 25 for local ports.

[gmailpop]
client=yes
accept = 127.0.0.1:20995
connect = pop.gmail.com:995
debug = 7
verifyChain = yes
CAfile = /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
checkHost = pop.gmail.com
OCSPaia = yes

[gmailsmtp]
client=yes
accept = 127.0.0.1:20465
connect = smtp.gmail.com:465
debug = 7
verifyChain = yes
CAfile = /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
checkHost = smtp.gmail.com
OCSPaia = yes

Outgoing (SMTP) mail.twc.com 587 STARTTLS (or SSL/TLS) Incoming (POP3) mail.twc.com 110 or 995 STARTTLS / SSL Don't know if the 110 is available from any IP. Long ago, my ISP allowed use of 25 and 110 ports, but only from IPs in there local network. If connecting via another network, you had to use the SSL ports. Did also see info that new accounts not getting email, and phasing out of others?? So, with Stunnel option, Pegasus sees the local port with no encryption, and stunnel maps and encrypts it to host. My lines for my gmail connections (using apppassword) Bold lines are extra options and linux options, and don't use the 110 or 25 for local ports. [gmailpop] client=yes accept = 127.0.0.1:20995 connect = pop.gmail.com:995 **debug = 7 verifyChain = yes CAfile = /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem checkHost = pop.gmail.com OCSPaia = yes ** [gmailsmtp] client=yes accept = 127.0.0.1:20465 connect = smtp.gmail.com:465 **debug = 7 verifyChain = yes CAfile = /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem checkHost = smtp.gmail.com OCSPaia = yes **

mikes@guam.net

msetzerii

posted 1 day ago at 3:23 am

Another option that might work??

You have hit a known issue. The Spectrum email infrastructure (mail.twc.com / Time Warner Cable) suffers from an active TLS bug. When modern applications try to negotiate connection protocols, they offer their highest standard (TLS 1.3). Instead of gracefully declining and rolling back to TLS 1.2, the Spectrum server completely crashes and drops the TCP connection.
GitHub
Because Pegasus Mail embeds OpenSSL directly into its core executables (TCPIP.DLL), it lacks a user-facing configuration file (like openssl.cnf) or a checkbox to cap the TLS version.
pmail community
To bypass this and force Pegasus Mail to use TLS 1.2 only, apply one of the following methods:
Method 1: Inject a Local openssl.cnf (Easiest)
Even though Pegasus Mail doesn't ship with an openssl.cnf text file, its embedded OpenSSL library will look for one in its directory at initialization. You can manually force it to drop TLS 1.3 support:

Open Notepad on your computer.
Paste the following configuration lines:
ini

openssl_conf = default_conf

[default_conf]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
MaxProtocol = TLSv1.2

Click File > Save As...
Change Save as type to All Files (.).
Name the file openssl.cnf and save it directly inside the main Pegasus Mail installation folder (usually C:\PMAIL\ or C:\PMAIL\Programs).
Restart Pegasus Mail. The internal OpenSSL library will register this constraint and max out at TLS 1.2, preventing mail.twc.com from dropping your connection.

Another option that might work?? You have hit a known issue. The Spectrum email infrastructure (mail.twc.com / Time Warner Cable) suffers from an active TLS bug. When modern applications try to negotiate connection protocols, they offer their highest standard (TLS 1.3). Instead of gracefully declining and rolling back to TLS 1.2, the Spectrum server completely crashes and drops the TCP connection. GitHub Because Pegasus Mail embeds OpenSSL directly into its core executables (TCPIP.DLL), it lacks a user-facing configuration file (like openssl.cnf) or a checkbox to cap the TLS version. pmail community To bypass this and force Pegasus Mail to use TLS 1.2 only, apply one of the following methods: Method 1: Inject a Local openssl.cnf (Easiest) Even though Pegasus Mail doesn't ship with an openssl.cnf text file, its embedded OpenSSL library will look for one in its directory at initialization. You can manually force it to drop TLS 1.3 support: Open Notepad on your computer. Paste the following configuration lines: ini openssl_conf = default_conf [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MaxProtocol = TLSv1.2 Click File > Save As... Change Save as type to All Files (*.*). Name the file openssl.cnf and save it directly inside the main Pegasus Mail installation folder (usually C:\PMAIL\ or C:\PMAIL\Programs\). Restart Pegasus Mail. The internal OpenSSL library will register this constraint and max out at TLS 1.2, preventing mail.twc.com from dropping your connection.

mikes@guam.net

bhenry004

posted 1 day ago at 4:53 am

msetzerii,

I tried the openssl.cnf method. It seems to attempt to connect using TLSv1.2 while other pop3 isp servers I use connect via tlsv1.3 (gmail & yahoo). The Spectrum server still is erratic in its connection behavior. I tried to connect 7 times within 6 minutes. Got 4 successes and 3 failures.
21:17:01 - yes
21:17:12 - no
21:20:13 - yes
21:21:33 - yes
21:21:49 - no
21:22:15 - no
21:22:41 - yes

I tend to agree with Brian that Spectrum servers may be overworked and under resourced. Spectrum may be phasing out its email support and not spending any resources on maintenance. Cox (which is now owned by Spectrum) started using yahoo as their email provider a couple years ago. Although I have not heard anything from Spectrum about discontinuing my email service, I suspect Spectrum may be moving in the same direction as Cox. It's just a frustrating situation. I've had Spectrum service in NY for years after they bought Time-Warner. They were nearly kicked out of NY for poor performance and service. They have been reaping profits for years but their customer service has been terrible. I think my only alternative is to start migrating all (and there a lot of them) accounts to another email provider.

msetzerii, I tried the openssl.cnf method. It seems to attempt to connect using TLSv1.2 while other pop3 isp servers I use connect via tlsv1.3 (gmail & yahoo). The Spectrum server still is erratic in its connection behavior. I tried to connect 7 times within 6 minutes. Got 4 successes and 3 failures. 21:17:01 - yes 21:17:12 - no 21:20:13 - yes 21:21:33 - yes 21:21:49 - no 21:22:15 - no 21:22:41 - yes I tend to agree with Brian that Spectrum servers may be overworked and under resourced. Spectrum may be phasing out its email support and not spending any resources on maintenance. Cox (which is now owned by Spectrum) started using yahoo as their email provider a couple years ago. Although I have not heard anything from Spectrum about discontinuing my email service, I suspect Spectrum may be moving in the same direction as Cox. It's just a frustrating situation. I've had Spectrum service in NY for years after they bought Time-Warner. They were nearly kicked out of NY for poor performance and service. They have been reaping profits for years but their customer service has been terrible. I think my only alternative is to start migrating all (and there a lot of them) accounts to another email provider.

msetzerii

posted 1 day ago at 5:42 am

Did more, and this option might do better?

openssl_conf = default_conf

[default_conf]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
MaxProtocol = TLSv1.2
CipherString = DEFAULT:@SECLEVEL=1

Seems to think the stunnel option might be better solution.
Just to note with linux it using openssl-3.5.9-1

Not sure what version the windows stunnel uses.

Did more, and this option might do better? openssl_conf = default_conf [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MaxProtocol = TLSv1.2 CipherString = DEFAULT:@SECLEVEL=1 Seems to think the stunnel option might be better solution. Just to note with linux it using openssl-3.5.9-1 Not sure what version the windows stunnel uses.

mikes@guam.net

msetzerii

posted 1 day ago at 11:10 am

Did a test. Added stunnel entries to my stunnel.conf and then did tests.

telnet 127.0.0.1 110 and telnet 127.0.0.1 25 and both connect so got past the TLS and at login, but I have not userid or password.

Testing had change the server name?

[spectrum-pop3]
client = yes
accept = 127.0.0.1:110
; Switched to universal spectrum server
connect = mail.spectrum.net:995
debug = 7
; Enforce modern TLS standards safely
sslVersionMin = TLSv1.2

[spectrum-smtp]
client = yes
accept = 127.0.0.1:25
connect = mail.spectrum.net:587
; CRITICAL: Tells stunnel to handle the STARTTLS negotiation flow
protocol = smtp
debug = 7
sslVersionMin = TLSv1.2

did connect to telnet 127.0.0.1 110 and it seems to connect.

connection to telnet 127.0.0.1 25 closes immediately.

Nov  8 21:03:00 setzcodell stunnel[52831]: LOG5[3]: Service [spectrum-pop3] accepted connection from 127.0.0.1:53582
Nov  8 21:03:00 setzcodell stunnel[52831]: LOG6[3]: s_connect: connecting 47.43.18.8:995
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG5[3]: s_connect: connected 47.43.18.8:995
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG5[3]: Service [spectrum-pop3] connected remote server from 192.168.1.16:46664
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: SNI: sending servername: mail.spectrum.net
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: Peer certificate not required
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: CERT: Certificate verification disabled
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: CERT: Certificate verification disabled
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: OCSP: Certificate chain verification disabled
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: Client certificate not requested
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: TLS connected: new session negotiated
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: TLSv1.2 ciphersuite: AES256-SHA256 (256-bit encryption)
Nov  8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: No peer temporary key received
Nov  8 21:03:08 setzcodell stunnel[52831]: LOG6[3]: Read socket closed (readsocket)
Nov  8 21:03:08 setzcodell stunnel[52831]: LOG6[3]: SSL_shutdown successfully sent close_notify alert
Nov  8 21:03:08 setzcodell stunnel[52831]: LOG6[3]: TLS socket closed (SSL_read)
Nov  8 21:03:08 setzcodell stunnel[52831]: LOG5[3]: Connection closed: 0 byte(s) sent to TLS, 34 byte(s) sent to socket
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: Service [spectrum-smtp] accepted connection from 127.0.0.1:48524
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG6[4]: s_connect: connecting 47.43.18.8:587
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: s_connect: connected 47.43.18.8:587
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: Service [spectrum-smtp] connected remote server from 192.168.1.16:53386
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG6[4]: SNI: sending servername: mail.spectrum.net
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG6[4]: Peer certificate not required
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG3[4]: SSL_connect: tls_validate_record_header@ssl/record/methods/tlsany_meth.c:77: error:0A00010B:SSL routines::wrong version number: client 127.0.0.1:48524
Nov  8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket

Seems mail.spectrum.net doesn't have smtp, so it might be using a different name?
nmap mail.spectrum.net -Pn
Starting Nmap 7.92 ( https://nmap.org ) at 2026-11-08 21:07 ChST
Nmap scan report for mail.spectrum.net (47.43.18.8 )
Host is up (0.074s latency).
rDNS record for 47.43.18.8: mail.charter.net.msg.chrl.nc.charter.net
Not shown: 995 filtered tcp ports (no-response)
PORT STATE SERVICE
110/tcp open pop3
143/tcp open imap
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s

Nmap done: 1 IP address (1 host up) scanned in 5.92 seconds

Did a test. Added stunnel entries to my stunnel.conf and then did tests. telnet 127.0.0.1 110 and telnet 127.0.0.1 25 and both connect so got past the TLS and at login, but I have not userid or password. Testing had change the server name? ```` [spectrum-pop3] client = yes accept = 127.0.0.1:110 ; Switched to universal spectrum server connect = mail.spectrum.net:995 debug = 7 ; Enforce modern TLS standards safely sslVersionMin = TLSv1.2 [spectrum-smtp] client = yes accept = 127.0.0.1:25 connect = mail.spectrum.net:587 ; CRITICAL: Tells stunnel to handle the STARTTLS negotiation flow protocol = smtp debug = 7 sslVersionMin = TLSv1.2 ```` did connect to telnet 127.0.0.1 110 and it seems to connect. connection to telnet 127.0.0.1 25 closes immediately. ```` Nov 8 21:03:00 setzcodell stunnel[52831]: LOG5[3]: Service [spectrum-pop3] accepted connection from 127.0.0.1:53582 Nov 8 21:03:00 setzcodell stunnel[52831]: LOG6[3]: s_connect: connecting 47.43.18.8:995 Nov 8 21:03:01 setzcodell stunnel[52831]: LOG5[3]: s_connect: connected 47.43.18.8:995 Nov 8 21:03:01 setzcodell stunnel[52831]: LOG5[3]: Service [spectrum-pop3] connected remote server from 192.168.1.16:46664 Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: SNI: sending servername: mail.spectrum.net Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: Peer certificate not required Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: CERT: Certificate verification disabled Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: CERT: Certificate verification disabled Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: OCSP: Certificate chain verification disabled Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: Client certificate not requested Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: TLS connected: new session negotiated Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: TLSv1.2 ciphersuite: AES256-SHA256 (256-bit encryption) Nov 8 21:03:01 setzcodell stunnel[52831]: LOG6[3]: No peer temporary key received Nov 8 21:03:08 setzcodell stunnel[52831]: LOG6[3]: Read socket closed (readsocket) Nov 8 21:03:08 setzcodell stunnel[52831]: LOG6[3]: SSL_shutdown successfully sent close_notify alert Nov 8 21:03:08 setzcodell stunnel[52831]: LOG6[3]: TLS socket closed (SSL_read) Nov 8 21:03:08 setzcodell stunnel[52831]: LOG5[3]: Connection closed: 0 byte(s) sent to TLS, 34 byte(s) sent to socket Nov 8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: Service [spectrum-smtp] accepted connection from 127.0.0.1:48524 Nov 8 21:03:14 setzcodell stunnel[52831]: LOG6[4]: s_connect: connecting 47.43.18.8:587 Nov 8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: s_connect: connected 47.43.18.8:587 Nov 8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: Service [spectrum-smtp] connected remote server from 192.168.1.16:53386 Nov 8 21:03:14 setzcodell stunnel[52831]: LOG6[4]: SNI: sending servername: mail.spectrum.net Nov 8 21:03:14 setzcodell stunnel[52831]: LOG6[4]: Peer certificate not required Nov 8 21:03:14 setzcodell stunnel[52831]: LOG3[4]: SSL_connect: tls_validate_record_header@ssl/record/methods/tlsany_meth.c:77: error:0A00010B:SSL routines::wrong version number: client 127.0.0.1:48524 Nov 8 21:03:14 setzcodell stunnel[52831]: LOG5[4]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket ```` Seems mail.spectrum.net doesn't have smtp, so it might be using a different name? nmap mail.spectrum.net -Pn Starting Nmap 7.92 ( https://nmap.org ) at 2026-11-08 21:07 ChST Nmap scan report for mail.spectrum.net (47.43.18.8 ) Host is up (0.074s latency). rDNS record for 47.43.18.8: mail.charter.net.msg.chrl.nc.charter.net Not shown: 995 filtered tcp ports (no-response) PORT STATE SERVICE 110/tcp open pop3 143/tcp open imap 587/tcp open submission 993/tcp open imaps 995/tcp open pop3s Nmap done: 1 IP address (1 host up) scanned in 5.92 seconds

mikes@guam.net

msetzerii

posted 1 day ago at 11:24 am

found this for smtp for spectrum??

. Core Outgoing (SMTP) Settings
For most users with a @charter.net or @spectrum.net email address, use the following settings:
SkyMigrate +1

SMTP Server: mobile.charter.net (Note: If your email ends in @roadrunner.com, @twc.com, @brighthouse.com, @adelphia.net, or a regional rr.com domain, use mail.twc.com instead)
SMTP Port: 587
SSL/TLS Encryption: On (or STARTTLS if prompted)
Requires Authentication: Yes (or check "My outgoing server requires authentication")
Username: Your full Spectrum email address (e.g., username@charter.net)
Password: Your Spectrum email password 
Spectrum.net +3

found this for smtp for spectrum?? . Core Outgoing (SMTP) Settings For most users with a @charter.net or @spectrum.net email address, use the following settings: SkyMigrate +1 SMTP Server: mobile.charter.net (Note: If your email ends in @roadrunner.com, @twc.com, @brighthouse.com, @adelphia.net, or a regional rr.com domain, use mail.twc.com instead) SMTP Port: 587 SSL/TLS Encryption: On (or STARTTLS if prompted) Requires Authentication: Yes (or check "My outgoing server requires authentication") Username: Your full Spectrum email address (e.g., username@charter.net) Password: Your Spectrum email password Spectrum.net +3

mikes@guam.net

Brian Fluet

posted 1 day ago at 12:13 pm

I think my only alternative is to start migrating all (and there a lot of them) accounts to another email provider.

That is what I did after my cancellation/re-enable experience with them. I really thought their email service would stop working again at any time. I am surprised that is still does.

[quote="pid:59333, uid:26261"]I think my only alternative is to start migrating all (and there a lot of them) accounts to another email provider.[/quote] That is what I did after my cancellation/re-enable experience with them. I really thought their email service would stop working again at any time. I am surprised that is still does.

msetzerii

posted 8 hours ago

Since I don't have an account with time, can only do so many things. May just be the moved the accounts from the twc.com to sprectrum.net servers.

I've had my primary account with local ISP going back to the late 80s.
Originally (if memory servers) servers were pop3.kuentos.guam.net and smtp.kuentos.guam.net and email was mikes@kuentos.guam.net.
Back then it was 3 Compaq PCs and about 20 dialup modems with a 255K connection to California.
Later the dropped kuentos from name, but could still use mikes@kuentos.guam.net or mikes@guam.net so even now that works, but servers changed to pop3.guam.net and smtp.guam.net. At some point, smtp.guam.net became smtp1.guam.net.
But email still works fine. Guam.net was bought by DocomoPacific.com and think new users get accounts under that, and that is what they use. But the guam.net is still supported. Would be a major issue if they dropped it.
I can do connection to these other servers, but since don't have userid or passords can not check if they actually connect to actual email accounts.

dig shows.

spectrum.net. 60 IN A 44.223.116.84
spectrum.net. 60 IN A 3.226.176.222
spectrum.net. 21600 IN NS ns-1572.awsdns-04.co.uk.
spectrum.net. 21600 IN NS ns-960.awsdns-56.net.
spectrum.net. 21600 IN NS ns-151.awsdns-18.com.
spectrum.net. 21600 IN NS ns-1336.awsdns-39.org.
spectrum.net. 900 IN SOA ns-1336.awsdns-39.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
spectrum.net. 300 IN MX 10 mx0.charter.net.
spectrum.net. 300 IN TXT "facebook-domain-verification=rz86gtthhiwz8v7qqp2ni4xfx21sas"
spectrum.net. 300 IN TXT "v=spf1 ip4:72.183.83.140 ip4:76.85.250.140 ip4:72.31.122.83 ip4:75.180.154.140 ip4:64.209.227.0/24 ip4:68.114.188.0/22 ip4:47.43.20.0/24 ip4:47.43.16.0/23 ip4:142.136.234.0/23 ~all"
spectrum.net. 300 IN TXT "google-site-verification=GD3r4tgpyqSV-B4DANuR2G4_66MHEeIvlulokJMo-yY"

dig spectrum.com

spectrum.com. 21600 IN NS a2-65.akam.net.
spectrum.com. 21600 IN NS a11-66.akam.net.
spectrum.com. 21600 IN NS a1-187.akam.net.
spectrum.com. 21600 IN NS a12-66.akam.net.
spectrum.com. 21600 IN NS a7-66.akam.net.
spectrum.com. 21600 IN NS a18-65.akam.net.
spectrum.com. 14400 IN A 142.136.168.58
spectrum.com. 14400 IN A 142.136.81.136
spectrum.com. 14400 IN A 142.136.81.135
spectrum.com. 14400 IN A 142.136.168.7
spectrum.com. 14400 IN MX 0 spectrum-com.mail.protection.outlook.com.
spectrum.com. 14400 IN TXT "facebook-domain-verification=gggrjx1q04wkwyb3g51ew9a0uvb3h0b"
spectrum.com. 14400 IN TXT "00D41000000cQ2w=1TB7y00000009rJ"
spectrum.com. 14400 IN TXT "adobe-idp-site-verification=204abc57a67dcfff034aee07aa9db2a7577ce9bdb3bf45a3657c0a2a3fecb289"
spectrum.com. 14400 IN TXT "v=spf1 ip4:142.136.234.128/27 ip4:142.136.235.128/27 include:aspmx.pardot.com include:everbridge.net include:spf.protection.outlook.com ~all"
spectrum.com. 14400 IN TXT "anthropic-domain-verification-rs19vn=hBt71QbMoLxxZ8xOOuxMByp8G"
spectrum.com. 14400 IN TXT "_4b8dc5b762cd5b4abdfdb6ea9237829e.zfyfvmchrl.acm-validations.aws."
spectrum.com. 14400 IN TXT "miro-verification=e51116d30341c8179b1529830f0d0a994990af6e"
spectrum.com. 14400 IN TXT "pexip-ms-tenant-domain-verification=e09712b4-39a7-44ce-a036-a242f0e3f332"
spectrum.com. 14400 IN TXT "smartsheet-site-validation=jOF0xArkkltDAbImVHr7xIkIaRJ-yeFI"
spectrum.com. 14400 IN TXT "cisco-ci-domain-verification=2616c4069abfb4cde83eab2f36c7645638aa84439c3b46f75372f9e9d945ee40"
spectrum.com. 14400 IN TXT "_ec65e45dac93fc3934fa5fdbb9bcf36a.spectrum.com."
spectrum.com. 14400 IN TXT "lucid-verification=crz_byg9nke4bne1QBP"
spectrum.com. 14400 IN TXT "postman-domain-verification=03636d118ea216ce2b7deaec31ccd70b5f593e1d0cbfec3b6b47f4f6da1358101082916a55e4fa40acd5541eb52fec96427b142cc83eae0186e509736b16a808"
spectrum.com. 14400 IN TXT "flexera-domain-verification-oaimpehnwckstwhr"
spectrum.com. 14400 IN TXT "smartsheet-site-validation=ZeIXL7WWBXaeYMbk20Nj0Bw6wd-DZdtV"
spectrum.com. 14400 IN TXT "flexera-domain-verification-lblhsdtuutrgdumi"
spectrum.com. 14400 IN TXT "google-site-verification=0bRYti_wd6n2BgDhRaJ7JazASd9YHEzMGyX3fDXN36o"
spectrum.com. 14400 IN TXT "ms-domain-verification=31dce107-7863-4da1-91ec-acba091a8778"
spectrum.com. 14400 IN TXT "@ MS=ms86718722"
spectrum.com. 14400 IN TXT "wrike-verification=NjkzNDcyNTo1NmUwOTdiZjNhNmU5ZWI3ZmQ4NDM0MjIyZjQwZTY4ZDE0ZGQyYzFjOTAwNzAwNjAwNWI3ZWI1Y2JkZTYzZWFi"
spectrum.com. 14400 IN TXT "insomnia-validation=8a6b7b20c0fb4a2ab8d7b0be5ff831eb6de71f05784d5ea690f05be80384dfc4"
spectrum.com. 14400 IN TXT "_0560d4c7f0ee467cfa8856068f5120e9.djqtsrsxkq.acm-validations.aws."
spectrum.com. 14400 IN TXT "docusign=f0e077d7-0eb2-4fc6-bd99-7cfe6227e228"
spectrum.com. 14400 IN TXT "SFMC-m2xZGT7-Ntc-O1HYMTGFW_SXjGyI_plkuo6mae4V"
spectrum.com. 14400 IN TXT "ms=ms45056673"
spectrum.com. 14400 IN TXT "7HLhOjsPmLXtqhkcpc7LvXFaZW1zjHo1-YAi1t7K5gESLZakuNo7NQ"
spectrum.com. 14400 IN TXT "facebook-domain-verification=oh9iz8g9in0fc1uzwop7nqa2qhgwqs"
spectrum.com. 14400 IN TXT "docusign=a0cbf796-bb93-4544-bab0-f637c55cc80d"
spectrum.com. 14400 IN TXT "00DWB000006aAgX=1TBWB00000002Ej"
spectrum.com. 14400 IN TXT "_29620b79c3743504308685c884570739.spectrum.com."
spectrum.com. 14400 IN TXT "00DO200000EkTBq=1TBO20000000ERB"
spectrum.com. 14400 IN TXT "google-site-verification=QQsT4V9HBHhkUnVgV7QXFH1NiS-Ug-L28YxfbmBVyeo"
spectrum.com. 14400 IN TXT "atlassian-domain-verification=5q5r35hSgdQxHaBJ0S0BVJ9CBnmQ5/PNh8dPKJF6oHvKHTI4diJ2cF0L8r0wPxwH"
spectrum.com. 14400 IN TXT "apple-domain-verification=ljFf9Ht3HWJXytvP34auvCc5G2VOU1m2FKzRBTWtjZc"
spectrum.com. 14400 IN TXT "paloaltonetworks-site-verification=0f8aee8f1efecd666f61dd2e122cd3cd4fd01559231867de7421bbbd7ff5ec70"
spectrum.com. 14400 IN TXT "docker-verification=5484f6dd-6c7e-4cdd-9f16-715034d56455"
spectrum.com. 14400 IN TXT "dr7h5d42l6onl2cunp6l5lfec2"
spectrum.com. 14400 IN TXT "figma-domain-verification=d6976db429d27190853a51e2a795ca7f543818bcf389f6f21237a60902462b1a-1743432666"
spectrum.com. 21600 IN SOA ns1.charter.com. hostmaster.charter.com. 2026090442 43200 3600 2419200 3600

Spectrum.net and Spectrum.com could be same company or totally different.

Getting ahold of the right tech person would give correct names for the pop3 and smtp servers. Then the issue of username. Some just want username up to the @ and others want the username@domain.

Good Luck.

Since I don't have an account with time, can only do so many things. May just be the moved the accounts from the twc.com to sprectrum.net servers. I've had my primary account with local ISP going back to the late 80s. Originally (if memory servers) servers were pop3.kuentos.guam.net and smtp.kuentos.guam.net and email was mikes@kuentos.guam.net. Back then it was 3 Compaq PCs and about 20 dialup modems with a 255K connection to California. Later the dropped kuentos from name, but could still use mikes@kuentos.guam.net or mikes@guam.net so even now that works, but servers changed to pop3.guam.net and smtp.guam.net. At some point, smtp.guam.net became smtp1.guam.net. But email still works fine. Guam.net was bought by DocomoPacific.com and think new users get accounts under that, and that is what they use. But the guam.net is still supported. Would be a major issue if they dropped it. I can do connection to these other servers, but since don't have userid or passords can not check if they actually connect to actual email accounts. dig shows. spectrum.net. 60 IN A 44.223.116.84 spectrum.net. 60 IN A 3.226.176.222 spectrum.net. 21600 IN NS ns-1572.awsdns-04.co.uk. spectrum.net. 21600 IN NS ns-960.awsdns-56.net. spectrum.net. 21600 IN NS ns-151.awsdns-18.com. spectrum.net. 21600 IN NS ns-1336.awsdns-39.org. spectrum.net. 900 IN SOA ns-1336.awsdns-39.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 spectrum.net. 300 IN MX 10 mx0.charter.net. spectrum.net. 300 IN TXT "facebook-domain-verification=rz86gtthhiwz8v7qqp2ni4xfx21sas" spectrum.net. 300 IN TXT "v=spf1 ip4:72.183.83.140 ip4:76.85.250.140 ip4:72.31.122.83 ip4:75.180.154.140 ip4:64.209.227.0/24 ip4:68.114.188.0/22 ip4:47.43.20.0/24 ip4:47.43.16.0/23 ip4:142.136.234.0/23 ~all" spectrum.net. 300 IN TXT "google-site-verification=GD3r4tgpyqSV-B4DANuR2G4_66MHEeIvlulokJMo-yY" dig spectrum.com spectrum.com. 21600 IN NS a2-65.akam.net. spectrum.com. 21600 IN NS a11-66.akam.net. spectrum.com. 21600 IN NS a1-187.akam.net. spectrum.com. 21600 IN NS a12-66.akam.net. spectrum.com. 21600 IN NS a7-66.akam.net. spectrum.com. 21600 IN NS a18-65.akam.net. spectrum.com. 14400 IN A 142.136.168.58 spectrum.com. 14400 IN A 142.136.81.136 spectrum.com. 14400 IN A 142.136.81.135 spectrum.com. 14400 IN A 142.136.168.7 spectrum.com. 14400 IN MX 0 spectrum-com.mail.protection.outlook.com. spectrum.com. 14400 IN TXT "facebook-domain-verification=gggrjx1q04wkwyb3g51ew9a0uvb3h0b" spectrum.com. 14400 IN TXT "00D41000000cQ2w=1TB7y00000009rJ" spectrum.com. 14400 IN TXT "adobe-idp-site-verification=204abc57a67dcfff034aee07aa9db2a7577ce9bdb3bf45a3657c0a2a3fecb289" spectrum.com. 14400 IN TXT "v=spf1 ip4:142.136.234.128/27 ip4:142.136.235.128/27 include:aspmx.pardot.com include:everbridge.net include:spf.protection.outlook.com ~all" spectrum.com. 14400 IN TXT "anthropic-domain-verification-rs19vn=hBt71QbMoLxxZ8xOOuxMByp8G" spectrum.com. 14400 IN TXT "_4b8dc5b762cd5b4abdfdb6ea9237829e.zfyfvmchrl.acm-validations.aws." spectrum.com. 14400 IN TXT "miro-verification=e51116d30341c8179b1529830f0d0a994990af6e" spectrum.com. 14400 IN TXT "pexip-ms-tenant-domain-verification=e09712b4-39a7-44ce-a036-a242f0e3f332" spectrum.com. 14400 IN TXT "smartsheet-site-validation=jOF0xArkkltDAbImVHr7xIkIaRJ-yeFI" spectrum.com. 14400 IN TXT "cisco-ci-domain-verification=2616c4069abfb4cde83eab2f36c7645638aa84439c3b46f75372f9e9d945ee40" spectrum.com. 14400 IN TXT "_ec65e45dac93fc3934fa5fdbb9bcf36a.spectrum.com." spectrum.com. 14400 IN TXT "lucid-verification=crz_byg9nke4bne1QBP" spectrum.com. 14400 IN TXT "postman-domain-verification=03636d118ea216ce2b7deaec31ccd70b5f593e1d0cbfec3b6b47f4f6da1358101082916a55e4fa40acd5541eb52fec96427b142cc83eae0186e509736b16a808" spectrum.com. 14400 IN TXT "flexera-domain-verification-oaimpehnwckstwhr" spectrum.com. 14400 IN TXT "smartsheet-site-validation=ZeIXL7WWBXaeYMbk20Nj0Bw6wd-DZdtV" spectrum.com. 14400 IN TXT "flexera-domain-verification-lblhsdtuutrgdumi" spectrum.com. 14400 IN TXT "google-site-verification=0bRYti_wd6n2BgDhRaJ7JazASd9YHEzMGyX3fDXN36o" spectrum.com. 14400 IN TXT "ms-domain-verification=31dce107-7863-4da1-91ec-acba091a8778" spectrum.com. 14400 IN TXT "@ MS=ms86718722" spectrum.com. 14400 IN TXT "wrike-verification=NjkzNDcyNTo1NmUwOTdiZjNhNmU5ZWI3ZmQ4NDM0MjIyZjQwZTY4ZDE0ZGQyYzFjOTAwNzAwNjAwNWI3ZWI1Y2JkZTYzZWFi" spectrum.com. 14400 IN TXT "insomnia-validation=8a6b7b20c0fb4a2ab8d7b0be5ff831eb6de71f05784d5ea690f05be80384dfc4" spectrum.com. 14400 IN TXT "_0560d4c7f0ee467cfa8856068f5120e9.djqtsrsxkq.acm-validations.aws." spectrum.com. 14400 IN TXT "docusign=f0e077d7-0eb2-4fc6-bd99-7cfe6227e228" spectrum.com. 14400 IN TXT "SFMC-m2xZGT7-Ntc-O1HYMTGFW_SXjGyI_plkuo6mae4V" spectrum.com. 14400 IN TXT "ms=ms45056673" spectrum.com. 14400 IN TXT "7HLhOjsPmLXtqhkcpc7LvXFaZW1zjHo1-YAi1t7K5gESLZakuNo7NQ" spectrum.com. 14400 IN TXT "facebook-domain-verification=oh9iz8g9in0fc1uzwop7nqa2qhgwqs" spectrum.com. 14400 IN TXT "docusign=a0cbf796-bb93-4544-bab0-f637c55cc80d" spectrum.com. 14400 IN TXT "00DWB000006aAgX=1TBWB00000002Ej" spectrum.com. 14400 IN TXT "_29620b79c3743504308685c884570739.spectrum.com." spectrum.com. 14400 IN TXT "00DO200000EkTBq=1TBO20000000ERB" spectrum.com. 14400 IN TXT "google-site-verification=QQsT4V9HBHhkUnVgV7QXFH1NiS-Ug-L28YxfbmBVyeo" spectrum.com. 14400 IN TXT "atlassian-domain-verification=5q5r35hSgdQxHaBJ0S0BVJ9CBnmQ5/PNh8dPKJF6oHvKHTI4diJ2cF0L8r0wPxwH" spectrum.com. 14400 IN TXT "apple-domain-verification=ljFf9Ht3HWJXytvP34auvCc5G2VOU1m2FKzRBTWtjZc" spectrum.com. 14400 IN TXT "paloaltonetworks-site-verification=0f8aee8f1efecd666f61dd2e122cd3cd4fd01559231867de7421bbbd7ff5ec70" spectrum.com. 14400 IN TXT "docker-verification=5484f6dd-6c7e-4cdd-9f16-715034d56455" spectrum.com. 14400 IN TXT "dr7h5d42l6onl2cunp6l5lfec2" spectrum.com. 14400 IN TXT "figma-domain-verification=d6976db429d27190853a51e2a795ca7f543818bcf389f6f21237a60902462b1a-1743432666" spectrum.com. 21600 IN SOA ns1.charter.com. hostmaster.charter.com. 2026090442 43200 3600 2419200 3600 Spectrum.net and Spectrum.com could be same company or totally different. Getting ahold of the right tech person would give correct names for the pop3 and smtp servers. Then the issue of username. Some just want username up to the @ and others want the username@domain. Good Luck.

mikes@guam.net

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history