Thunderbird Error Code 12263

[Justin23]

Hi,

I have Thunderbird set up with my mail.comcast.net. Every so often, when Thunderbird checks for emails, I receive an error code that says that mail.comcast.net sending a bad request (or something of that sort) and then gives the error code -12263. Anyone knows about thunderbird Error Code 12263?

[Zenon]

Is your SSl enabled enabled in you thunderbird browser ??? Or are the permissions to /var/www/html/ and /var/www/error/noindex.html set correctly? With the Live HTTP Headers extension you could take a peek at the interaction between your browser and its server.

[goatape]

Check the following things, to evaluate your problem :

- Check in Tools> Options> Advanced> Network tab of my connection type, whether I was using proxy and if so, was allowed to SSL. Do not use for me, I use the direct Internet connection.
- Check my hosts file, that's fine.
- Make a new profile with the firefox.exe "-ProfileManager command, I did not work, yet the error code 12,263.
- Reinstalling full browser with the manual removal of folders, including those that store personal preferences.

[Sanith]

I don't think there is issue with the Comcast mail servers. Comcast must have limited its support for high internet speed. That means that we have set the connection to High Speed Internet Comcast network and the software included with your High Speed Internet Comcast CD-ROM.

[Zoe]

Thunderbird currently includes a TCP / IP service daemon, and a UDP / IP service daemon. An Internet protocol service (ipsv) daemon waiting for incoming calls connections on a local socket. In the incoming connections, the demon ipsv conditionally executes an arbitrary program by reading from standard input the socket, and standard output writing to the outlet, which controls the connection.

[Seraphim]

I was getting the same error 12,263, is that when when a server requires Secure Socket Layers to serve a page, but for some reason (either front-end (if any) or back-end is enabled / accessible. I managed to fix this error, what was happening when accessing my web server. What happened was that I had the Directive SSLRequireSSL in my virtual machine, but the SSLEngine Directive was in a different virtual machine, which I realized from that specified in a separate file .Conf.