M
Mr. Arnold
Gary VanderMolen said:Likewise.
Is this some kind of justification that you have had no problems with WM,
and it must be something else other than WM?
Even if an av was leading to the problem, which I doubt, then what business
would an av have in the corruption or lost of the psw for WM? It makes no
sense that an av is the root cause of the WM problem ---- no sense.
Why is it, that when WM looses the psw and you repeatedly attempt to
configure WM to hold the psw, it won't hold it and then for some reason it
holds it, that the av is the root cause? It holds it long enough for the
task to be completed, and then it looses the psw again.
Not only have I had the problem of the psw not holding on POP3, WM has lost
the psw for NNTP too. It won't hold the psw in the middle of making a post
and subsequent posts, the same thing happens with email too, then all of a
sudden it holds the credentials.
The pop-up screen that ask for the user's credentials when you make the post
or send the email, because WM has lost the psw, and you tell it to save the
credentials again, again, again and again when doing the post or sending the
email won't save them.
You basically have to give up on that route and go to the WM User Account
to try to set the credentials that it has lost, with telling WM to save the
credentials, just to complete the task at hand of making the post or sending
the email, that WM as you snagged you right in the middle of the whole
process. Then all of a sudden it just stops.
WHAT DOES AN AV HAVE TO DO WITH THIS?
I have written many programs,, debugged and tested many programs over the
years professionally to know that whatever is happening here is solely on WM
doorstep.
end rant.