ContentsPrevious ArticleNext ArticleHome
  Can't Send/Receive Mail

Sometimes when I start Exchange (or Windows Messaging), it refuses to send or receive mail. If I compose a message, it just stays stuck in the Outbox. If I have Exchange set up automatically to launch a dial-up networking connection, it never gets invoked. If I exit from Exchange and restart the system, the problem goes away for a while.

There are a number of things that can cause Exchange/Windows Messaging to misbehave in this fashion. However, if you are running Windows 95 and have upgraded to Windows Messaging or the full Exchange Client, there is one thing you should check first: Click on the Tools menu and see if the Deliver Now and Remote Mail entries are grayed out. If they are, exit from Exchange and use the three-finger salute (Ctrl+Alt+Delete) to bring up the Close Program dialog. Chances are, you will see a "Mapisp32" entry. Highlight it and click the End Task button. After 20 seconds or so, you should get a "this program is not responding" dialog. Tell Windows 95 to kill it anyway.
     This mapisp32 bug has been floating around for a while now. It doesn't show up on every system but, when it does, it's quite persistent. It will happen much less often if you make it a habit to exit from Exchange/Windows Messaging using the File menu's Exit and Log Off option. Also, you are more likely to trigger this problem if you exit from Exchange and then try to rerun it right away. Nevertheless, mapisp32 will still hang up on you occasionally, no matter what you do.

MS Knowledge Base, search on "Windows Messaging" for Windows 95 related problems.


Maintained by William K. Walker
Copyright 1997 by William K. Walker
Last update: 09 Jan 97