Re: OE Version.
- From: "Poprivet" <poprivet@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 13 May 2007 10:48:57 -0400
FWIW: I just remembered my sister is having the same complaints about MSN
newsgroups. Similar but different, I know; but they are having problems for
the last month or so and she doesn't have any e-mail virus checks.
Good observational work, BTW.
Pop`
Kman wrote:
The version number "problem" is exactly as everyone explained.
I like your 2 possible explanations about timing on the occasional
failure to send/receive. Since I am in this condition now, I had a
chance to do a few tests.
Test 1. "Send" only works OK.
Test 2. "Receive" only doesn't work.
Test 3. Turn of NAV email scanning. "Receive" only still doesn't work.
Plus - I have noticed that the failure message comes up when msn is
trying to *authorize* my connection rather than during incoming
email. Test 3, and this observation leads to the conclusion that the
timing problem is more likely at Microsoft's end due to (as you
suggest) heavy load, systems off-line for maintenance, DOS attack or
whatever - rather than NAV.
Kman
"Poprivet" wrote:
Kman wrote:
On a recent thread, one of the MVP's said that the latest vesion of
OE was
6.00.2900.3028. I then checked *my* version and it is at
6.00.2900.2180!!!!
I am 100% up to date with Microsoft Update, so how do I get the
missing updates to OE?
Not a problem; the "version" part that's important is the 6.00.2900.
The rest of it depends on a few things, exactly what I don't know,
but I've come across that situation before. I'm also completely up
to date and from OE About it says 2180. But down in the list of
components below in the About window, you'll note there are some
3028 indicators in the notes there, I'm pretty sure; at least I do.
Occasionally MVPs will mention things in ways that should be
clarified but neglect to do so. Well, not just MVPs: Lots of
people do that.
FWIW, I also have a comment about the "failure to send and receive"
problems that crop up from time to time. The error message is:
"Your server has unexpectedly terminated the connection. Possible
causes for this include server problems, network problems, or a long
period of inactivity. Account: 'pop3.email.msn.com', Server:
'pop3.email.msn.com', Protocol: POP3, Port: 110, Secure(SSL): No,
Error Number: 0x800CCC0F"
The MVPs typically say disable NAV, etc, etc but I have found
through experience that if one does *absoultely nothing* the problem
disappears in a day or two. IMHO it is an intermittent Microsoft POP
server problem.
This is simplistic, but I think accurate enough to be useful:
There are two things at work here and both are right, IMO.
The server speeds/loads/traffic/status are always changing and
funnies can happen. And sometimes they will go away on their own,
just as you describe. In particular it can happen on a server with
very heavy traffic loads or when parts of it are down for
maintenance. A "server| is typically actually a group of computers
so if they take one down, its workload has to be picked up by the
others and if traffic is high on top of it, they can take so long
getting back to service your connection that your client thinks the
server has gone away.
On the other hand, Antivirus software can make about the same thing
happen. It takes a finite length of time to do the virus scan on the
incoming e-mails and that's sometimes enough to once again make your
system think the connection had gone away. The antivirus software
sticks itself in between your mail client and the incoming data, so
there is no communication possible to/from your client to the 'net
while the scanner is evaluating the e-mail for viruses. That's
often long enough for the mail client to ask if the other end is
still present but, since the antivirus is in the way, the question
never goes out, there isn't any answer, and thus your client says
the connection has been broken. It's a similar process for
outgoing e-mails and that results in your mail client thinking the
mail WAS sent, because the antivirus software accepted the mail; so
your mail client sticks it in your Sent folder, as it should do.
But, if the antivirus gets a failure message back, it should but
doesn't always tell you so, and if you look in the Sent folder, it
looks like the mail was sent. For me those are unacceptable
situations and thus I don't use the mail scanning features of AV
software.
It's also true that you are still protected if you don't scan your
mails as they come in. All you've really lost is the advance
notification; a virus will still be caught and you'll still be
notified, just not during the download of the e-mail. So, you don't
really lose anything by turning off the email scanning. I also
recommend to people that they turn it off.
That's the easiest way I know to explain it all. I suspect there
will be those purists and arguementative types that will want to
pick at that, but that's OK. If they add something of value, great,
and if not, well, it's usually not hard to tell they're just trying
to show off or misguide something into something they can argue
about.
HTH
Pop`
.
- References:
- Re: OE Version.
- From: Poprivet
- Re: OE Version.
- From: Kman
- Re: OE Version.
- Prev by Date: Re: OE newsgroup .dbx file name BUG
- Next by Date: Re: OE Version.
- Previous by thread: Re: OE Version.
- Next by thread: Re: OE Version.
- Index(es):
Relevant Pages
|
