In windows mail I have three accounts listed and recently I am unable to send mail from just one of them?
When i go to the service providers site and log on I can send mail from the accopunt but not through windows mail.

What error message do you get? What anti-virus are you using?
Frank Saunders, MS-MVP OE/WM fjsmjs.com
"benjibogs"

Using Mcafee anti virus. Just noticed there is a message stuck in the outbox from the particular account in question. error message saying that there was an error displaying message and to check there is enough memory!?
"Frank Saunders, MS-MVP OE/WM" wrote:

Read oehelp.com/OETips.aspx#3 Then uninstall your antivirus program, reboot, and try WinMail again.
If you still have the problem of the undeletable message in the outbox, see oehelp.com/WMUtil/
After you get your email working, you will need to install a non-intrusive antivirus program such as the free Avast. Whichever antivirus you select, be sure to NOT enable the email scanning option.
Gary VanderMolen
"benjibogs"

I tried running WMutil but it wouldn't work. I'll switch off the email scanner and reboot.
"Gary VanderMolen" wrote:

What do you mean by "it wouldn't work." Try to be more descriptive.
Gary VanderMolen
"benjibogs"

Sorry, I have extracted it to a foulder on the desktop, When I run the programme I get this message:
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click quit, the application will close immediately.
Unable to load DLL 'scxout.dll'. The application has failed to start because it's side-by-side configuration is incorrect. Please see the application event log for more detail. (Exeption from HRESULT:0x800736B1).
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text ************** System.DllNotFoundException: Unable to load DLL 'scxout.dll': The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail. (Exception from HRESULT: 0x800736B1) at WMUtil.MWMUtil1.XOut(IntPtr pszLogPath, IntPtr pszName, XoutCallbackProc x) at WMUtil.frmWMUtil1.btnXOut_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll WMUtil Assembly Version: 1.5.0.0 Win32 Version: 1.5.0.0 CodeBase: file:///C:/Users/Checkley/Desktop/WMutil/WMUtil.exe Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll System.Runtime.Remoting Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
For example:
<configuration> <system.windows.forms jitDebugging="true" /> </configuration>
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

"Gary VanderMolen" wrote:

"benjibogs"

Did you extract _both_ files to the same folder?
Frank Saunders, MS-MVP OE/WM fjsmjs.com

There is a newer version. It still may be buggy, but that error is fixed. oehelp.com/WMUtil/
Delete the old exe and dll first.
steve
"benjibogs"

Thank you Steve that seems to have done the trick!
"Steve Cochran" wrote:

Great. Sorry it took so long to get it right.
steve
"benjibogs"