Bug ??

Sometimes, when I click on "send", the message is correctly moved to the
Outbox and sent, but the window does not close, unless I do it manually. Is
it a known bug ? I experienced the same issue in OE.
Thanks.

Mike

"Mike" <Mike@xxxxxx> wrote in message
news:F35576E4-265E-4253-AA71-38CDCF1AAD19@xxxxxx Do you see an Acorn shaped icon on the bottom right of that dialogue box?
Try clicking it.


--
Regards Steve.
MS-MVP. MAIL. [DTS]
http://www.getsafeonline.org/

Thanks, Steve.
Like I said it does not always happen. What do you mean by "dialogue box" ?
The actual message window that does not close ?

"mac" wrote:

"Mike" <Mike@xxxxxx> wrote in message
news:301E12FD-AF64-4DD9-B122-D0F1760F79F9@xxxxxx Mike, I was referring to the box that appears after clicking send/ receive.

I now see that you mean the actual message window.

I would 'guess' that could be a video problem, check the website of your
graphics card manufacturer for any updates to its drivers?


--
Regards Steve.
MS-MVP. MAIL. [DTS] UK

Your AV isn't scanning outgoing mail, is it?
--
Noel

"Mike" <Mike@xxxxxx> wrote in message
news:301E12FD-AF64-4DD9-B122-D0F1760F79F9@xxxxxx

Is this with an IMAP account? I've seen some reports in OE newsgroups
on that in the past.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



"Mike" <Mike@xxxxxx> wrote in message
news:F35576E4-265E-4253-AA71-38CDCF1AAD19@xxxxxx

Yes. It's an IMAP account.

"Michael Santovec" wrote:

Sorry, I don't know of any fix for that. But it looks like it's a bug
that WLM carried over from OE.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



"Mike" <Mike@xxxxxx> wrote in message
news:84509817-B409-4CB9-A0E0-504032853952@xxxxxx

I am experiencing the same problem as Mike. What I have found is that the
message sends the first time I click the Send button, but the window does not
close. Thinking I must have mis-clicked, I click the button again and the
message is sent a second time and the window closes. I have been using WLM
for quite a while (a year maybe?), and this problem only started happening in
the last week or two. I recently installed Windows XP SP3, so perhaps it is
related to that. I can't think of any other recent changes.

TNTitan89

"Michael Santovec" wrote: