|Outlook Express suddenly will not Send/Receive|
What to do?
| 3:19 pm on Jul 18, 2005 (gmt 0)|
I'm not sure that this forum, or this site, is the best place to ask, but I'm pretty well stuck.
The client has a home office, with a desktop and a laptop sharing the same connection. The desktop has suddenly, and inexplicably stopped Sending/Receiving.
Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'email@example.com', Server: 'outgoing.verizon.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number: 0x800CCC0F
The laptop is unaffected, and continues to Send/Receive from all accounts without difficulty, but the desktop is vital to keeping things running.
I have verified that the email settings are correct, and have not been changed. I have verified that Norton is updated, then took the additional steps of turning off Norton firewall and Norton AV. I have verified that XP is fully updated.
I installed Thunderbird and imported Outlook Express information. Thunderbird shows an error message also.
The ISP says that it is an Outlook issue, and that Microsoft is responsible...
I've gone to Microsoft and done what I know to do short of jumping in way over my head.
| 3:26 pm on Jul 18, 2005 (gmt 0)|
Have you done everything listed in this Microsoft article?
I've seen this kind of error happen when the Outlook Express program file was damaged. You might want to try reinstalling the program.
| 3:54 pm on Jul 18, 2005 (gmt 0)|
In the 'causes' section I think that I have addressed everything except the corruption of Outlook Express.
(A search for the original disks is underway:))
I was hoping that installing Thunderbird would let me work around Outlook. Is this not an option? (All of this is outside of what I do, but it is hoped that I can sort out the problem.)
| 4:02 pm on Jul 18, 2005 (gmt 0)|
If you have Norton Anti-Virus email scan running, you are getting the error because Outlook Express is trying to download a message with improperly formatted headers. Most typically, it is a spam. And most of the time the cause is the headers are not properly separated from the message body by two line breaks.
Your options are to have an email admin delete the offending message from the email server, download and the message from your other machine, or, to disable Norton Anti-Virus email scanning and then download your email.
If you don't have Norton Anti-Virus email scan running, then never mind.
| 4:07 pm on Jul 18, 2005 (gmt 0)|
NIS is installed. I made sure that it was fully updated, rebooted, then just decided to shut it all off in order to take it out of the loop.
| 5:08 pm on Jul 18, 2005 (gmt 0)|
One source has advised that it is not sufficient to simply turn off Norton; that if the problem lies with Norton, that it might be necessary to completely uninstall in order to expose the problem and get Outlook working again. Opinions?
| 6:20 pm on Jul 18, 2005 (gmt 0)|
I thought you said it was Outlook Express in the original post. If the problem is with Outlook, then that sounds right. If it is with Outlook Express, then this is a problem that has been around for several years. It manifests itself with some email server software and not others. So it is really a 3 vendor issue (Outlook Express - Norton - Email Server), and none of them will ever take ownership.
I quit using Outlook Express because of it.
Again, what I was describing is pretty specific. The error you quoted will happen in Outlook Express when you get an email that does not have each header line terminated with a [carriage return] + [line feed] combination. The last header row (the one before the message body) must be terminated with two such strings.
(The error may happen for other reasons also.)
A few more symptoms of what I am talking about:
- The error seems to happen randomly on certain messages. However, once it occurs, if you try to get your email again from Outlook Express, it will error out on the same message.
- If you get your email from another machine where the error doesn't occur, then you can again begin to access your email from the problem machine. (this happens because the problematic email has now been deleted on the server)
| 12:31 am on Jul 19, 2005 (gmt 0)|
Yes, I meant Outlook Express. Sorry.
Time is money, and both were being lost in a hurry. I brought in a tech, who brought a sledge hammer approach that I didn't like too well.
We had already done a system restore to a 'known' point before the problem arose. The tech wanted to expand the perimeter and set a system restore for over a week ago. In this case that wasn't too painful. (Though there was no expanation of the potential downside.)
It did in fact 'solve' the problem (I'll need to remember that one.), though I had been hoping for a bit more of an educated troubleshooting approach. Had this not worked, the tech's next recommendation was a bigger sledge hammer, and a complete system reinstall.
I'm not happy and am needing another tech option before the next inevitable, but hopefully distant, crisis. Is this really the way they work? Perhaps I have just had a charmed existence. Key files were fully backed up off site, so data loss wasn't crucial. We just needed be made operational.
| 7:41 pm on Mar 17, 2008 (gmt 0)|
Confirmed with the previous posts about NIS, all i had to do to fix this problem was disable the incoming and outgoing email scanners on Norton Internet Security and click Send/Receive, and the OE was working once more...
| 7:09 pm on Mar 19, 2008 (gmt 0)|
what was installed during the period in which you did a system restore point to?