From noreply at sourceforge.net Fri Aug 7 20:39:28 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 07 Aug 2009 18:39:28 +0000 Subject: [spambayes-bugs] [ spambayes-Bugs-1103976 ] Outlook.exe will not terminate when launched via mailto Message-ID: Bugs item #1103976, was opened at 2005-01-17 10:56 Message generated for change (Comment added) made by jeremydunn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: 1.1.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: robert (elitemrp) Assigned to: Mark Hammond (mhammond) Summary: Outlook.exe will not terminate when launched via mailto Initial Comment: I first ran into this problem a few months ago at work. But at the time I thought it was related to a custom program we run here. But now I noticed I can easily reproduce the problem on any computer running SpamBayes+Outlook 2003 on Windows XP. Basically, I will open Outlook via the icon to read mail. I will then close Outlook, and if I have Task Manager open, I will see that Outlook.exe closes correctly. Now if I launch a mailto: link (or use a program that launches a new mail), where the Compose Mail window opens, but not the actual outlook program, the problem occurs. If I close the compose mail window, by either clicking Send, or closing it without sending, the OUTLOOK.EXE task will not exit. If I launch Outlook again, I'll now have multiple instances of OUTLOOK.EXE in task manager. Now the multiple instances is what caused the problem with our custom software at work, but that has nothing to do with the fact that Outlook does not exit correctly when running Spambayes and having a program/mailto link open the Compose Mail window. Yes I realize there have been 2 previous tickets about OUTLOOK.EXE closing, but none came to the conclusion that it's caused by a Compose Mail window. And both are closed without a solution. I have tested this on several computers and have tried multiple things to try to fix it (such as renaming extend.dat and other files) and nothing seems to work. ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-07 14:39 Message: This problem still exists in SB 1.0.4 using Outlook/Office 2003 on Windows 2000. It can easily be replicated using VB similar to that posted by fsnyder on 2005-2-25 What's confusing the issue is that the same problem is also caused by other outlook plugins, notably PGP. Running my MSAccess app, with all plugins disabled, the problem does not occur. Exit app, enable SB, try again, problem occurs. Exit app, disable SB, enable PGP, problem occurs. Exit app, disable PGP, disable SB, enable all other plugins, problem does not occur. This is more than a nuisance. Running in a Terminal Services environment, each open instance of Outlook consumes ~30MB of RAM which is the single scarce resource. If one user generates dozens of emails using a batch process, each of which open a copy of Outlook and consume ~30MB RAM, all other users on the server are hosed. I would be very happy to demonstrate this problem to anyone with the skills to correct it, which I do not have. I can supply log files, etc. as needed. ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2008-01-15 21:48 Message: Logged In: YES user_id=366391 Originator: NO Problem still exists... ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2007-07-23 21:43 Message: Logged In: YES user_id=44345 Originator: NO Mark, I'm reassigning this to you to see if you see an easy fix for this problem. -- Skip ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-07-23 20:59 Message: Logged In: YES user_id=366391 Originator: NO The unload problem occurs also while: - start outlook - connect PDA via USB/Active sync - let PDA turned On - close outlook Outlook stays open in background. Now turn off PDA. Normal behavior (without SpamBayes) - outlook closes Bad behavior (With SpamBayes) - outlook stays "hanging" on background This BUG is killing me, because I have to kill the outlook process... And that can cause a damage to the pst file. Problem exists in SpamBayes 1.1a3 and older. PLEASE FIX IT !!! ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-03-24 22:42 Message: Logged In: YES user_id=366391 Originator: NO Its 2007 and this is still not fixed ---------------------------------------------------------------------- Comment By: Sadie (sadie_187) Date: 2006-08-16 18:05 Message: Logged In: YES user_id=1577414 Problem: Outlook 2003 does not terminate the outlook.exe process at closing of the program. Possible Solution (worked for me) : Active sync for my outlook was causing the process to hang. Removed the calendar, contacts sink option; which I rarely use. ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2006-05-23 19:12 Message: Logged In: YES user_id=1369127 To be honest Outlook 2003 was fine for a bit after disabling the spam blocker and then it started with the refusing to shut down again. I finally gave up and paid $5 for an addin that makes sure the program is shut down (http://www.daveswebsite.com/software/olshutdown/ ). I truely do not believe it is SpamBayes causing the trouble as I have it without this program. I have found it often happens if I click on an email link in a browser when the program is not open. I do know I have had this problem for years and I don't use addons in my email as a general rule. ---------------------------------------------------------------------- Comment By: Christian Blackburn (seier) Date: 2006-05-23 17:04 Message: Logged In: YES user_id=561770 Hi NyteTears, > It seems that the spam filter in outlook is causing it to >hang. I wasn't able to reproduce this in Outlook 2003, which is where the problem is at for most people. Perhaps you'd like to tell us what version you're using and the exact steps you took to resolve this. As far as I can tell the problem the rest of us are experiencing is indeed related to SpamBayes' plugin and not outlook itself, although I'm sure in the past with all those security updates the scenario you've described must have been true at least once. Thanks, Christian Blackburn ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 04:24 Message: Logged In: YES user_id=552329 See also: [ 1336405 ] Add-In breaks MAPI control http://sourceforge.net/tracker/index.php?func=detail&aid=1336405&group_id=61702&atid=498104 ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2005-10-27 15:59 Message: Logged In: YES user_id=1369127 I had this problem on my computer and tried removing various different program to fix it. Nothing worked. I have found it is not related to any program outside of outlook. It is an outlook problem. It seems that the spam filter in outlook is causing it to hang. Once I turned off the spam filter that came with outlook I never had the program hang once. I could not tell you why it does this or a fix for it beyond turning the option off but that is the cause of outlook remaining open in the task manager. ---------------------------------------------------------------------- Comment By: Kip Cartwright (kcartwri) Date: 2005-03-29 19:26 Message: Logged In: YES user_id=192708 I have the same problem on Outlook 2003. No problem with Outlook XP (2002). ---------------------------------------------------------------------- Comment By: fsnyder (fsnyder) Date: 2005-02-25 17:00 Message: Logged In: YES user_id=1227716 This behavior of the Outlook.exe not being stopped properly can be duplicated using the following VBScript code. OPTION EXPLICIT On error Resume Next err.clear Dim oOutlookApp, oOutlookNS Set oOutlookApp = GetObject(,"Outlook.Application") if Err <> 0 then MsgBox "Outlook not currently running." & VbCrLf & "Creating New Outlook Application. I'll kill it when I'm done" set oOutlookApp = CreateObject ("Outlook.Application") else MsgBox "Outlook was running. I'll kill it anyway when I'm done." End If MsgBox oOutlookApp.name & " version# " & oOutlookApp.version MsgBox "Now I'll kill the Outlook.exe process the clean way" oOutlookApp.Quit set oOutlookNS = Nothing set oOutlookApp = Nothing MsgBox "END" Run it and watch the TaskManager for when the Outlook.exe process gets created, and killed (as long as the SpamBayes Add-In is NOT activated in Outlook) This should normally kill the process unless some other add- in or anti-virus code is not allowing Outlook to exit cleanly. Hope this Helps -fsnyder ---------------------------------------------------------------------- Comment By: Hal Smith (bpu_webguy) Date: 2005-02-03 13:00 Message: Logged In: YES user_id=842378 One other source of hanging OL up, with or without Spambayes is ActiveSync for your PDA, celll phone or whatever. AS does tend to work behind your back, a little bit. One of the reasons I love Process Explorer from System Internals... -h ---------------------------------------------------------------------- Comment By: Gil (spambayes411) Date: 2005-02-02 05:52 Message: Logged In: YES user_id=1210353 I've discovered this is not limited to the mailto function. I use a program called SynchPST to keep outlook sychronized between my home computer and my laptop. When SynchPST opens, I see it in the task manager and it opens Outlook as well. After I synch my PST files, I close SynchPST. It closes but Outlook remains in the task manager. If the Spambayes add-in is not loaded, then both SynchPST and Outlook quit as they should. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 18:22 Message: Logged In: YES user_id=552329 Thanks Kenny :) I don't really know what might be causing this, but I guess you could start by checking to see if the spambayes log gets to the "addin terminating" part. Let me know if I can help at all (though I don't have OL2003 anywhere). ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2005-01-24 11:23 Message: Logged In: YES user_id=859086 Yep, I was able to confirm this problem on Outlook 2003. If I activate a mailto link with SpamBayes loaded and enabled, OUTLOOK.EXE will not exit when I close the compose window. If I disable SpamBayes filtering from SpamBayes Manager, OUTLOOK.EXE still doesn't exit. If I completely disable loading of SpamBayes from the COM Add-ins dialog then OUTLOOK.EXE closes properly when I close the compose window. I'll look into this further when I get a chance. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 00:53 Message: Logged In: YES user_id=552329 Maybe this is specific to Outlook 2003 then? Kenny: you've got 2003, right? Can you try and replicate this? ---------------------------------------------------------------------- Comment By: robert (elitemrp) Date: 2005-01-21 06:49 Message: Logged In: YES user_id=1198932 Yes, it only happens with SpamBayes installed. I install SpamBayes, set up the toolbar, etc Close Outlook, type mailto:blah at blah.com in a browser or click a mail link and it opens the Compose Mail window. Once I close this window, Outlook.exe ramains in the task list. If I click another mailto link I'll have 2 stuck open, then 3, etc If I have only 1 process loaded and it's the main Outlook window, when I click a mailto link it will work fine since it doesn't load a separate outlook.exe process. It only does this when the main outlook program isn't loaded. Once I uninstall SpamBayes or uncheck it in the COM Add-Ins area in Outlook, this problem goes away. As soon as I close a Compose Mail window, OUTLOOK.EXE terminates correctly. I've tried this on several PCs, some with fresh installs of XP/ Outlook, some with several months old installs and other applications, it's the same on each. Thanks ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-20 22:17 Message: Logged In: YES user_id=552329 Have you tried this without SpamBayes installed? I get the same behaviour without SpamBayes, which says to me it's an Outlook problem, not a SpamBayes one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 From noreply at sourceforge.net Sat Aug 8 13:41:33 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 08 Aug 2009 11:41:33 +0000 Subject: [spambayes-bugs] [ spambayes-Bugs-1103976 ] Outlook.exe will not terminate when launched via mailto Message-ID: Bugs item #1103976, was opened at 2005-01-17 09:56 Message generated for change (Comment added) made by montanaro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: 1.1.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: robert (elitemrp) Assigned to: Mark Hammond (mhammond) Summary: Outlook.exe will not terminate when launched via mailto Initial Comment: I first ran into this problem a few months ago at work. But at the time I thought it was related to a custom program we run here. But now I noticed I can easily reproduce the problem on any computer running SpamBayes+Outlook 2003 on Windows XP. Basically, I will open Outlook via the icon to read mail. I will then close Outlook, and if I have Task Manager open, I will see that Outlook.exe closes correctly. Now if I launch a mailto: link (or use a program that launches a new mail), where the Compose Mail window opens, but not the actual outlook program, the problem occurs. If I close the compose mail window, by either clicking Send, or closing it without sending, the OUTLOOK.EXE task will not exit. If I launch Outlook again, I'll now have multiple instances of OUTLOOK.EXE in task manager. Now the multiple instances is what caused the problem with our custom software at work, but that has nothing to do with the fact that Outlook does not exit correctly when running Spambayes and having a program/mailto link open the Compose Mail window. Yes I realize there have been 2 previous tickets about OUTLOOK.EXE closing, but none came to the conclusion that it's caused by a Compose Mail window. And both are closed without a solution. I have tested this on several computers and have tried multiple things to try to fix it (such as renaming extend.dat and other files) and nothing seems to work. ---------------------------------------------------------------------- >Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 06:41 Message: Jeremy, can you try with SpamBayes 1.1a4? I'm not a Windows user so I can't investigate the problem in any way. I just ran through the entire chain of comments though. It seems that there are other non-SpamBayes ways that this can occur. Also, the fact that it occurs in Outlook 2003 but not Outlook XP suggests this is a bug in Outlook itself. OTOH, the text at the daveswebsite.com link reads, in part: Outlook is notorious for hanging around in the background when a user exits the application. The cause of this is partly a random behavior of Outlook itself and most often a user installed addin that does not release itself from Outlook correctly. Can someone investigate what it means for an addin to "not release itself from Outlook correctly?" ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-07 13:39 Message: This problem still exists in SB 1.0.4 using Outlook/Office 2003 on Windows 2000. It can easily be replicated using VB similar to that posted by fsnyder on 2005-2-25 What's confusing the issue is that the same problem is also caused by other outlook plugins, notably PGP. Running my MSAccess app, with all plugins disabled, the problem does not occur. Exit app, enable SB, try again, problem occurs. Exit app, disable SB, enable PGP, problem occurs. Exit app, disable PGP, disable SB, enable all other plugins, problem does not occur. This is more than a nuisance. Running in a Terminal Services environment, each open instance of Outlook consumes ~30MB of RAM which is the single scarce resource. If one user generates dozens of emails using a batch process, each of which open a copy of Outlook and consume ~30MB RAM, all other users on the server are hosed. I would be very happy to demonstrate this problem to anyone with the skills to correct it, which I do not have. I can supply log files, etc. as needed. ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2008-01-15 20:48 Message: Logged In: YES user_id=366391 Originator: NO Problem still exists... ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2007-07-23 20:43 Message: Logged In: YES user_id=44345 Originator: NO Mark, I'm reassigning this to you to see if you see an easy fix for this problem. -- Skip ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-07-23 19:59 Message: Logged In: YES user_id=366391 Originator: NO The unload problem occurs also while: - start outlook - connect PDA via USB/Active sync - let PDA turned On - close outlook Outlook stays open in background. Now turn off PDA. Normal behavior (without SpamBayes) - outlook closes Bad behavior (With SpamBayes) - outlook stays "hanging" on background This BUG is killing me, because I have to kill the outlook process... And that can cause a damage to the pst file. Problem exists in SpamBayes 1.1a3 and older. PLEASE FIX IT !!! ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-03-24 21:42 Message: Logged In: YES user_id=366391 Originator: NO Its 2007 and this is still not fixed ---------------------------------------------------------------------- Comment By: Sadie (sadie_187) Date: 2006-08-16 17:05 Message: Logged In: YES user_id=1577414 Problem: Outlook 2003 does not terminate the outlook.exe process at closing of the program. Possible Solution (worked for me) : Active sync for my outlook was causing the process to hang. Removed the calendar, contacts sink option; which I rarely use. ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2006-05-23 18:12 Message: Logged In: YES user_id=1369127 To be honest Outlook 2003 was fine for a bit after disabling the spam blocker and then it started with the refusing to shut down again. I finally gave up and paid $5 for an addin that makes sure the program is shut down (http://www.daveswebsite.com/software/olshutdown/ ). I truely do not believe it is SpamBayes causing the trouble as I have it without this program. I have found it often happens if I click on an email link in a browser when the program is not open. I do know I have had this problem for years and I don't use addons in my email as a general rule. ---------------------------------------------------------------------- Comment By: Christian Blackburn (seier) Date: 2006-05-23 16:04 Message: Logged In: YES user_id=561770 Hi NyteTears, > It seems that the spam filter in outlook is causing it to >hang. I wasn't able to reproduce this in Outlook 2003, which is where the problem is at for most people. Perhaps you'd like to tell us what version you're using and the exact steps you took to resolve this. As far as I can tell the problem the rest of us are experiencing is indeed related to SpamBayes' plugin and not outlook itself, although I'm sure in the past with all those security updates the scenario you've described must have been true at least once. Thanks, Christian Blackburn ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 03:24 Message: Logged In: YES user_id=552329 See also: [ 1336405 ] Add-In breaks MAPI control http://sourceforge.net/tracker/index.php?func=detail&aid=1336405&group_id=61702&atid=498104 ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2005-10-27 14:59 Message: Logged In: YES user_id=1369127 I had this problem on my computer and tried removing various different program to fix it. Nothing worked. I have found it is not related to any program outside of outlook. It is an outlook problem. It seems that the spam filter in outlook is causing it to hang. Once I turned off the spam filter that came with outlook I never had the program hang once. I could not tell you why it does this or a fix for it beyond turning the option off but that is the cause of outlook remaining open in the task manager. ---------------------------------------------------------------------- Comment By: Kip Cartwright (kcartwri) Date: 2005-03-29 18:26 Message: Logged In: YES user_id=192708 I have the same problem on Outlook 2003. No problem with Outlook XP (2002). ---------------------------------------------------------------------- Comment By: fsnyder (fsnyder) Date: 2005-02-25 16:00 Message: Logged In: YES user_id=1227716 This behavior of the Outlook.exe not being stopped properly can be duplicated using the following VBScript code. OPTION EXPLICIT On error Resume Next err.clear Dim oOutlookApp, oOutlookNS Set oOutlookApp = GetObject(,"Outlook.Application") if Err <> 0 then MsgBox "Outlook not currently running." & VbCrLf & "Creating New Outlook Application. I'll kill it when I'm done" set oOutlookApp = CreateObject ("Outlook.Application") else MsgBox "Outlook was running. I'll kill it anyway when I'm done." End If MsgBox oOutlookApp.name & " version# " & oOutlookApp.version MsgBox "Now I'll kill the Outlook.exe process the clean way" oOutlookApp.Quit set oOutlookNS = Nothing set oOutlookApp = Nothing MsgBox "END" Run it and watch the TaskManager for when the Outlook.exe process gets created, and killed (as long as the SpamBayes Add-In is NOT activated in Outlook) This should normally kill the process unless some other add- in or anti-virus code is not allowing Outlook to exit cleanly. Hope this Helps -fsnyder ---------------------------------------------------------------------- Comment By: Hal Smith (bpu_webguy) Date: 2005-02-03 12:00 Message: Logged In: YES user_id=842378 One other source of hanging OL up, with or without Spambayes is ActiveSync for your PDA, celll phone or whatever. AS does tend to work behind your back, a little bit. One of the reasons I love Process Explorer from System Internals... -h ---------------------------------------------------------------------- Comment By: Gil (spambayes411) Date: 2005-02-02 04:52 Message: Logged In: YES user_id=1210353 I've discovered this is not limited to the mailto function. I use a program called SynchPST to keep outlook sychronized between my home computer and my laptop. When SynchPST opens, I see it in the task manager and it opens Outlook as well. After I synch my PST files, I close SynchPST. It closes but Outlook remains in the task manager. If the Spambayes add-in is not loaded, then both SynchPST and Outlook quit as they should. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 17:22 Message: Logged In: YES user_id=552329 Thanks Kenny :) I don't really know what might be causing this, but I guess you could start by checking to see if the spambayes log gets to the "addin terminating" part. Let me know if I can help at all (though I don't have OL2003 anywhere). ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2005-01-24 10:23 Message: Logged In: YES user_id=859086 Yep, I was able to confirm this problem on Outlook 2003. If I activate a mailto link with SpamBayes loaded and enabled, OUTLOOK.EXE will not exit when I close the compose window. If I disable SpamBayes filtering from SpamBayes Manager, OUTLOOK.EXE still doesn't exit. If I completely disable loading of SpamBayes from the COM Add-ins dialog then OUTLOOK.EXE closes properly when I close the compose window. I'll look into this further when I get a chance. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-23 23:53 Message: Logged In: YES user_id=552329 Maybe this is specific to Outlook 2003 then? Kenny: you've got 2003, right? Can you try and replicate this? ---------------------------------------------------------------------- Comment By: robert (elitemrp) Date: 2005-01-21 05:49 Message: Logged In: YES user_id=1198932 Yes, it only happens with SpamBayes installed. I install SpamBayes, set up the toolbar, etc Close Outlook, type mailto:blah at blah.com in a browser or click a mail link and it opens the Compose Mail window. Once I close this window, Outlook.exe ramains in the task list. If I click another mailto link I'll have 2 stuck open, then 3, etc If I have only 1 process loaded and it's the main Outlook window, when I click a mailto link it will work fine since it doesn't load a separate outlook.exe process. It only does this when the main outlook program isn't loaded. Once I uninstall SpamBayes or uncheck it in the COM Add-Ins area in Outlook, this problem goes away. As soon as I close a Compose Mail window, OUTLOOK.EXE terminates correctly. I've tried this on several PCs, some with fresh installs of XP/ Outlook, some with several months old installs and other applications, it's the same on each. Thanks ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-20 21:17 Message: Logged In: YES user_id=552329 Have you tried this without SpamBayes installed? I get the same behaviour without SpamBayes, which says to me it's an Outlook problem, not a SpamBayes one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 From noreply at sourceforge.net Sat Aug 8 14:01:45 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 08 Aug 2009 12:01:45 +0000 Subject: [spambayes-bugs] [ spambayes-Bugs-1103976 ] Outlook.exe will not terminate when launched via mailto Message-ID: Bugs item #1103976, was opened at 2005-01-17 10:56 Message generated for change (Comment added) made by jeremydunn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: 1.1.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: robert (elitemrp) Assigned to: Mark Hammond (mhammond) Summary: Outlook.exe will not terminate when launched via mailto Initial Comment: I first ran into this problem a few months ago at work. But at the time I thought it was related to a custom program we run here. But now I noticed I can easily reproduce the problem on any computer running SpamBayes+Outlook 2003 on Windows XP. Basically, I will open Outlook via the icon to read mail. I will then close Outlook, and if I have Task Manager open, I will see that Outlook.exe closes correctly. Now if I launch a mailto: link (or use a program that launches a new mail), where the Compose Mail window opens, but not the actual outlook program, the problem occurs. If I close the compose mail window, by either clicking Send, or closing it without sending, the OUTLOOK.EXE task will not exit. If I launch Outlook again, I'll now have multiple instances of OUTLOOK.EXE in task manager. Now the multiple instances is what caused the problem with our custom software at work, but that has nothing to do with the fact that Outlook does not exit correctly when running Spambayes and having a program/mailto link open the Compose Mail window. Yes I realize there have been 2 previous tickets about OUTLOOK.EXE closing, but none came to the conclusion that it's caused by a Compose Mail window. And both are closed without a solution. I have tested this on several computers and have tried multiple things to try to fix it (such as renaming extend.dat and other files) and nothing seems to work. ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-08 08:01 Message: It's frustrating to me that SB maintainers keep trying to make this an "Outlook" problem. Yes, obviously it's an Outlook(-related) problem - SB is used as an Outlook plugin!! We have to accept the buggy nature of the host we have chosen to live with. The real issue is as I stated previously- the problem can EASILY be demonstrated to go *completely* away when SB and other offending plugins (e.g. PGP) are disabled, and can EASILY be demonstrated to reappear, consistently, without any ambiguity, when SB and/or other offending plugins are enabled. I will try with SB 1.1a4 and report results again. However we tried 1.1a4 recently on our terminal server (which is the only place I have access to Outlook - I do not use it myself) and it caused some other problems which I don't remember, so I need to be a little cautious. It's a production environment. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 07:41 Message: Jeremy, can you try with SpamBayes 1.1a4? I'm not a Windows user so I can't investigate the problem in any way. I just ran through the entire chain of comments though. It seems that there are other non-SpamBayes ways that this can occur. Also, the fact that it occurs in Outlook 2003 but not Outlook XP suggests this is a bug in Outlook itself. OTOH, the text at the daveswebsite.com link reads, in part: Outlook is notorious for hanging around in the background when a user exits the application. The cause of this is partly a random behavior of Outlook itself and most often a user installed addin that does not release itself from Outlook correctly. Can someone investigate what it means for an addin to "not release itself from Outlook correctly?" ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-07 14:39 Message: This problem still exists in SB 1.0.4 using Outlook/Office 2003 on Windows 2000. It can easily be replicated using VB similar to that posted by fsnyder on 2005-2-25 What's confusing the issue is that the same problem is also caused by other outlook plugins, notably PGP. Running my MSAccess app, with all plugins disabled, the problem does not occur. Exit app, enable SB, try again, problem occurs. Exit app, disable SB, enable PGP, problem occurs. Exit app, disable PGP, disable SB, enable all other plugins, problem does not occur. This is more than a nuisance. Running in a Terminal Services environment, each open instance of Outlook consumes ~30MB of RAM which is the single scarce resource. If one user generates dozens of emails using a batch process, each of which open a copy of Outlook and consume ~30MB RAM, all other users on the server are hosed. I would be very happy to demonstrate this problem to anyone with the skills to correct it, which I do not have. I can supply log files, etc. as needed. ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2008-01-15 21:48 Message: Logged In: YES user_id=366391 Originator: NO Problem still exists... ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2007-07-23 21:43 Message: Logged In: YES user_id=44345 Originator: NO Mark, I'm reassigning this to you to see if you see an easy fix for this problem. -- Skip ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-07-23 20:59 Message: Logged In: YES user_id=366391 Originator: NO The unload problem occurs also while: - start outlook - connect PDA via USB/Active sync - let PDA turned On - close outlook Outlook stays open in background. Now turn off PDA. Normal behavior (without SpamBayes) - outlook closes Bad behavior (With SpamBayes) - outlook stays "hanging" on background This BUG is killing me, because I have to kill the outlook process... And that can cause a damage to the pst file. Problem exists in SpamBayes 1.1a3 and older. PLEASE FIX IT !!! ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-03-24 22:42 Message: Logged In: YES user_id=366391 Originator: NO Its 2007 and this is still not fixed ---------------------------------------------------------------------- Comment By: Sadie (sadie_187) Date: 2006-08-16 18:05 Message: Logged In: YES user_id=1577414 Problem: Outlook 2003 does not terminate the outlook.exe process at closing of the program. Possible Solution (worked for me) : Active sync for my outlook was causing the process to hang. Removed the calendar, contacts sink option; which I rarely use. ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2006-05-23 19:12 Message: Logged In: YES user_id=1369127 To be honest Outlook 2003 was fine for a bit after disabling the spam blocker and then it started with the refusing to shut down again. I finally gave up and paid $5 for an addin that makes sure the program is shut down (http://www.daveswebsite.com/software/olshutdown/ ). I truely do not believe it is SpamBayes causing the trouble as I have it without this program. I have found it often happens if I click on an email link in a browser when the program is not open. I do know I have had this problem for years and I don't use addons in my email as a general rule. ---------------------------------------------------------------------- Comment By: Christian Blackburn (seier) Date: 2006-05-23 17:04 Message: Logged In: YES user_id=561770 Hi NyteTears, > It seems that the spam filter in outlook is causing it to >hang. I wasn't able to reproduce this in Outlook 2003, which is where the problem is at for most people. Perhaps you'd like to tell us what version you're using and the exact steps you took to resolve this. As far as I can tell the problem the rest of us are experiencing is indeed related to SpamBayes' plugin and not outlook itself, although I'm sure in the past with all those security updates the scenario you've described must have been true at least once. Thanks, Christian Blackburn ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 04:24 Message: Logged In: YES user_id=552329 See also: [ 1336405 ] Add-In breaks MAPI control http://sourceforge.net/tracker/index.php?func=detail&aid=1336405&group_id=61702&atid=498104 ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2005-10-27 15:59 Message: Logged In: YES user_id=1369127 I had this problem on my computer and tried removing various different program to fix it. Nothing worked. I have found it is not related to any program outside of outlook. It is an outlook problem. It seems that the spam filter in outlook is causing it to hang. Once I turned off the spam filter that came with outlook I never had the program hang once. I could not tell you why it does this or a fix for it beyond turning the option off but that is the cause of outlook remaining open in the task manager. ---------------------------------------------------------------------- Comment By: Kip Cartwright (kcartwri) Date: 2005-03-29 19:26 Message: Logged In: YES user_id=192708 I have the same problem on Outlook 2003. No problem with Outlook XP (2002). ---------------------------------------------------------------------- Comment By: fsnyder (fsnyder) Date: 2005-02-25 17:00 Message: Logged In: YES user_id=1227716 This behavior of the Outlook.exe not being stopped properly can be duplicated using the following VBScript code. OPTION EXPLICIT On error Resume Next err.clear Dim oOutlookApp, oOutlookNS Set oOutlookApp = GetObject(,"Outlook.Application") if Err <> 0 then MsgBox "Outlook not currently running." & VbCrLf & "Creating New Outlook Application. I'll kill it when I'm done" set oOutlookApp = CreateObject ("Outlook.Application") else MsgBox "Outlook was running. I'll kill it anyway when I'm done." End If MsgBox oOutlookApp.name & " version# " & oOutlookApp.version MsgBox "Now I'll kill the Outlook.exe process the clean way" oOutlookApp.Quit set oOutlookNS = Nothing set oOutlookApp = Nothing MsgBox "END" Run it and watch the TaskManager for when the Outlook.exe process gets created, and killed (as long as the SpamBayes Add-In is NOT activated in Outlook) This should normally kill the process unless some other add- in or anti-virus code is not allowing Outlook to exit cleanly. Hope this Helps -fsnyder ---------------------------------------------------------------------- Comment By: Hal Smith (bpu_webguy) Date: 2005-02-03 13:00 Message: Logged In: YES user_id=842378 One other source of hanging OL up, with or without Spambayes is ActiveSync for your PDA, celll phone or whatever. AS does tend to work behind your back, a little bit. One of the reasons I love Process Explorer from System Internals... -h ---------------------------------------------------------------------- Comment By: Gil (spambayes411) Date: 2005-02-02 05:52 Message: Logged In: YES user_id=1210353 I've discovered this is not limited to the mailto function. I use a program called SynchPST to keep outlook sychronized between my home computer and my laptop. When SynchPST opens, I see it in the task manager and it opens Outlook as well. After I synch my PST files, I close SynchPST. It closes but Outlook remains in the task manager. If the Spambayes add-in is not loaded, then both SynchPST and Outlook quit as they should. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 18:22 Message: Logged In: YES user_id=552329 Thanks Kenny :) I don't really know what might be causing this, but I guess you could start by checking to see if the spambayes log gets to the "addin terminating" part. Let me know if I can help at all (though I don't have OL2003 anywhere). ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2005-01-24 11:23 Message: Logged In: YES user_id=859086 Yep, I was able to confirm this problem on Outlook 2003. If I activate a mailto link with SpamBayes loaded and enabled, OUTLOOK.EXE will not exit when I close the compose window. If I disable SpamBayes filtering from SpamBayes Manager, OUTLOOK.EXE still doesn't exit. If I completely disable loading of SpamBayes from the COM Add-ins dialog then OUTLOOK.EXE closes properly when I close the compose window. I'll look into this further when I get a chance. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 00:53 Message: Logged In: YES user_id=552329 Maybe this is specific to Outlook 2003 then? Kenny: you've got 2003, right? Can you try and replicate this? ---------------------------------------------------------------------- Comment By: robert (elitemrp) Date: 2005-01-21 06:49 Message: Logged In: YES user_id=1198932 Yes, it only happens with SpamBayes installed. I install SpamBayes, set up the toolbar, etc Close Outlook, type mailto:blah at blah.com in a browser or click a mail link and it opens the Compose Mail window. Once I close this window, Outlook.exe ramains in the task list. If I click another mailto link I'll have 2 stuck open, then 3, etc If I have only 1 process loaded and it's the main Outlook window, when I click a mailto link it will work fine since it doesn't load a separate outlook.exe process. It only does this when the main outlook program isn't loaded. Once I uninstall SpamBayes or uncheck it in the COM Add-Ins area in Outlook, this problem goes away. As soon as I close a Compose Mail window, OUTLOOK.EXE terminates correctly. I've tried this on several PCs, some with fresh installs of XP/ Outlook, some with several months old installs and other applications, it's the same on each. Thanks ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-20 22:17 Message: Logged In: YES user_id=552329 Have you tried this without SpamBayes installed? I get the same behaviour without SpamBayes, which says to me it's an Outlook problem, not a SpamBayes one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 From noreply at sourceforge.net Sat Aug 8 19:37:51 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 08 Aug 2009 17:37:51 +0000 Subject: [spambayes-bugs] [ spambayes-Bugs-1103976 ] Outlook.exe will not terminate when launched via mailto Message-ID: Bugs item #1103976, was opened at 2005-01-18 02:56 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: 1.1.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: robert (elitemrp) Assigned to: Mark Hammond (mhammond) Summary: Outlook.exe will not terminate when launched via mailto Initial Comment: I first ran into this problem a few months ago at work. But at the time I thought it was related to a custom program we run here. But now I noticed I can easily reproduce the problem on any computer running SpamBayes+Outlook 2003 on Windows XP. Basically, I will open Outlook via the icon to read mail. I will then close Outlook, and if I have Task Manager open, I will see that Outlook.exe closes correctly. Now if I launch a mailto: link (or use a program that launches a new mail), where the Compose Mail window opens, but not the actual outlook program, the problem occurs. If I close the compose mail window, by either clicking Send, or closing it without sending, the OUTLOOK.EXE task will not exit. If I launch Outlook again, I'll now have multiple instances of OUTLOOK.EXE in task manager. Now the multiple instances is what caused the problem with our custom software at work, but that has nothing to do with the fact that Outlook does not exit correctly when running Spambayes and having a program/mailto link open the Compose Mail window. Yes I realize there have been 2 previous tickets about OUTLOOK.EXE closing, but none came to the conclusion that it's caused by a Compose Mail window. And both are closed without a solution. I have tested this on several computers and have tried multiple things to try to fix it (such as renaming extend.dat and other files) and nothing seems to work. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-08-09 03:37 Message: I'm sorry you are frustrated with our free tool and free support. About all I can suggest is that you avoid using any such outlook plugins which give you this problem, including SpamBayes. You might also like to chat to the authors of some of those other plugins with the same issue so see if they can shed any light for us. ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-08 22:01 Message: It's frustrating to me that SB maintainers keep trying to make this an "Outlook" problem. Yes, obviously it's an Outlook(-related) problem - SB is used as an Outlook plugin!! We have to accept the buggy nature of the host we have chosen to live with. The real issue is as I stated previously- the problem can EASILY be demonstrated to go *completely* away when SB and other offending plugins (e.g. PGP) are disabled, and can EASILY be demonstrated to reappear, consistently, without any ambiguity, when SB and/or other offending plugins are enabled. I will try with SB 1.1a4 and report results again. However we tried 1.1a4 recently on our terminal server (which is the only place I have access to Outlook - I do not use it myself) and it caused some other problems which I don't remember, so I need to be a little cautious. It's a production environment. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 21:41 Message: Jeremy, can you try with SpamBayes 1.1a4? I'm not a Windows user so I can't investigate the problem in any way. I just ran through the entire chain of comments though. It seems that there are other non-SpamBayes ways that this can occur. Also, the fact that it occurs in Outlook 2003 but not Outlook XP suggests this is a bug in Outlook itself. OTOH, the text at the daveswebsite.com link reads, in part: Outlook is notorious for hanging around in the background when a user exits the application. The cause of this is partly a random behavior of Outlook itself and most often a user installed addin that does not release itself from Outlook correctly. Can someone investigate what it means for an addin to "not release itself from Outlook correctly?" ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-08 04:39 Message: This problem still exists in SB 1.0.4 using Outlook/Office 2003 on Windows 2000. It can easily be replicated using VB similar to that posted by fsnyder on 2005-2-25 What's confusing the issue is that the same problem is also caused by other outlook plugins, notably PGP. Running my MSAccess app, with all plugins disabled, the problem does not occur. Exit app, enable SB, try again, problem occurs. Exit app, disable SB, enable PGP, problem occurs. Exit app, disable PGP, disable SB, enable all other plugins, problem does not occur. This is more than a nuisance. Running in a Terminal Services environment, each open instance of Outlook consumes ~30MB of RAM which is the single scarce resource. If one user generates dozens of emails using a batch process, each of which open a copy of Outlook and consume ~30MB RAM, all other users on the server are hosed. I would be very happy to demonstrate this problem to anyone with the skills to correct it, which I do not have. I can supply log files, etc. as needed. ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2008-01-16 13:48 Message: Logged In: YES user_id=366391 Originator: NO Problem still exists... ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2007-07-24 11:43 Message: Logged In: YES user_id=44345 Originator: NO Mark, I'm reassigning this to you to see if you see an easy fix for this problem. -- Skip ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-07-24 10:59 Message: Logged In: YES user_id=366391 Originator: NO The unload problem occurs also while: - start outlook - connect PDA via USB/Active sync - let PDA turned On - close outlook Outlook stays open in background. Now turn off PDA. Normal behavior (without SpamBayes) - outlook closes Bad behavior (With SpamBayes) - outlook stays "hanging" on background This BUG is killing me, because I have to kill the outlook process... And that can cause a damage to the pst file. Problem exists in SpamBayes 1.1a3 and older. PLEASE FIX IT !!! ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-03-25 12:42 Message: Logged In: YES user_id=366391 Originator: NO Its 2007 and this is still not fixed ---------------------------------------------------------------------- Comment By: Sadie (sadie_187) Date: 2006-08-17 08:05 Message: Logged In: YES user_id=1577414 Problem: Outlook 2003 does not terminate the outlook.exe process at closing of the program. Possible Solution (worked for me) : Active sync for my outlook was causing the process to hang. Removed the calendar, contacts sink option; which I rarely use. ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2006-05-24 09:12 Message: Logged In: YES user_id=1369127 To be honest Outlook 2003 was fine for a bit after disabling the spam blocker and then it started with the refusing to shut down again. I finally gave up and paid $5 for an addin that makes sure the program is shut down (http://www.daveswebsite.com/software/olshutdown/ ). I truely do not believe it is SpamBayes causing the trouble as I have it without this program. I have found it often happens if I click on an email link in a browser when the program is not open. I do know I have had this problem for years and I don't use addons in my email as a general rule. ---------------------------------------------------------------------- Comment By: Christian Blackburn (seier) Date: 2006-05-24 07:04 Message: Logged In: YES user_id=561770 Hi NyteTears, > It seems that the spam filter in outlook is causing it to >hang. I wasn't able to reproduce this in Outlook 2003, which is where the problem is at for most people. Perhaps you'd like to tell us what version you're using and the exact steps you took to resolve this. As far as I can tell the problem the rest of us are experiencing is indeed related to SpamBayes' plugin and not outlook itself, although I'm sure in the past with all those security updates the scenario you've described must have been true at least once. Thanks, Christian Blackburn ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 20:24 Message: Logged In: YES user_id=552329 See also: [ 1336405 ] Add-In breaks MAPI control http://sourceforge.net/tracker/index.php?func=detail&aid=1336405&group_id=61702&atid=498104 ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2005-10-28 05:59 Message: Logged In: YES user_id=1369127 I had this problem on my computer and tried removing various different program to fix it. Nothing worked. I have found it is not related to any program outside of outlook. It is an outlook problem. It seems that the spam filter in outlook is causing it to hang. Once I turned off the spam filter that came with outlook I never had the program hang once. I could not tell you why it does this or a fix for it beyond turning the option off but that is the cause of outlook remaining open in the task manager. ---------------------------------------------------------------------- Comment By: Kip Cartwright (kcartwri) Date: 2005-03-30 10:26 Message: Logged In: YES user_id=192708 I have the same problem on Outlook 2003. No problem with Outlook XP (2002). ---------------------------------------------------------------------- Comment By: fsnyder (fsnyder) Date: 2005-02-26 09:00 Message: Logged In: YES user_id=1227716 This behavior of the Outlook.exe not being stopped properly can be duplicated using the following VBScript code. OPTION EXPLICIT On error Resume Next err.clear Dim oOutlookApp, oOutlookNS Set oOutlookApp = GetObject(,"Outlook.Application") if Err <> 0 then MsgBox "Outlook not currently running." & VbCrLf & "Creating New Outlook Application. I'll kill it when I'm done" set oOutlookApp = CreateObject ("Outlook.Application") else MsgBox "Outlook was running. I'll kill it anyway when I'm done." End If MsgBox oOutlookApp.name & " version# " & oOutlookApp.version MsgBox "Now I'll kill the Outlook.exe process the clean way" oOutlookApp.Quit set oOutlookNS = Nothing set oOutlookApp = Nothing MsgBox "END" Run it and watch the TaskManager for when the Outlook.exe process gets created, and killed (as long as the SpamBayes Add-In is NOT activated in Outlook) This should normally kill the process unless some other add- in or anti-virus code is not allowing Outlook to exit cleanly. Hope this Helps -fsnyder ---------------------------------------------------------------------- Comment By: Hal Smith (bpu_webguy) Date: 2005-02-04 05:00 Message: Logged In: YES user_id=842378 One other source of hanging OL up, with or without Spambayes is ActiveSync for your PDA, celll phone or whatever. AS does tend to work behind your back, a little bit. One of the reasons I love Process Explorer from System Internals... -h ---------------------------------------------------------------------- Comment By: Gil (spambayes411) Date: 2005-02-02 21:52 Message: Logged In: YES user_id=1210353 I've discovered this is not limited to the mailto function. I use a program called SynchPST to keep outlook sychronized between my home computer and my laptop. When SynchPST opens, I see it in the task manager and it opens Outlook as well. After I synch my PST files, I close SynchPST. It closes but Outlook remains in the task manager. If the Spambayes add-in is not loaded, then both SynchPST and Outlook quit as they should. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-25 10:22 Message: Logged In: YES user_id=552329 Thanks Kenny :) I don't really know what might be causing this, but I guess you could start by checking to see if the spambayes log gets to the "addin terminating" part. Let me know if I can help at all (though I don't have OL2003 anywhere). ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2005-01-25 03:23 Message: Logged In: YES user_id=859086 Yep, I was able to confirm this problem on Outlook 2003. If I activate a mailto link with SpamBayes loaded and enabled, OUTLOOK.EXE will not exit when I close the compose window. If I disable SpamBayes filtering from SpamBayes Manager, OUTLOOK.EXE still doesn't exit. If I completely disable loading of SpamBayes from the COM Add-ins dialog then OUTLOOK.EXE closes properly when I close the compose window. I'll look into this further when I get a chance. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 16:53 Message: Logged In: YES user_id=552329 Maybe this is specific to Outlook 2003 then? Kenny: you've got 2003, right? Can you try and replicate this? ---------------------------------------------------------------------- Comment By: robert (elitemrp) Date: 2005-01-21 22:49 Message: Logged In: YES user_id=1198932 Yes, it only happens with SpamBayes installed. I install SpamBayes, set up the toolbar, etc Close Outlook, type mailto:blah at blah.com in a browser or click a mail link and it opens the Compose Mail window. Once I close this window, Outlook.exe ramains in the task list. If I click another mailto link I'll have 2 stuck open, then 3, etc If I have only 1 process loaded and it's the main Outlook window, when I click a mailto link it will work fine since it doesn't load a separate outlook.exe process. It only does this when the main outlook program isn't loaded. Once I uninstall SpamBayes or uncheck it in the COM Add-Ins area in Outlook, this problem goes away. As soon as I close a Compose Mail window, OUTLOOK.EXE terminates correctly. I've tried this on several PCs, some with fresh installs of XP/ Outlook, some with several months old installs and other applications, it's the same on each. Thanks ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-21 14:17 Message: Logged In: YES user_id=552329 Have you tried this without SpamBayes installed? I get the same behaviour without SpamBayes, which says to me it's an Outlook problem, not a SpamBayes one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 From noreply at sourceforge.net Sat Aug 8 20:30:26 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 08 Aug 2009 18:30:26 +0000 Subject: [spambayes-bugs] [ spambayes-Bugs-1103976 ] Outlook.exe will not terminate when launched via mailto Message-ID: Bugs item #1103976, was opened at 2005-01-17 09:56 Message generated for change (Comment added) made by montanaro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: 1.1.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: robert (elitemrp) Assigned to: Mark Hammond (mhammond) Summary: Outlook.exe will not terminate when launched via mailto Initial Comment: I first ran into this problem a few months ago at work. But at the time I thought it was related to a custom program we run here. But now I noticed I can easily reproduce the problem on any computer running SpamBayes+Outlook 2003 on Windows XP. Basically, I will open Outlook via the icon to read mail. I will then close Outlook, and if I have Task Manager open, I will see that Outlook.exe closes correctly. Now if I launch a mailto: link (or use a program that launches a new mail), where the Compose Mail window opens, but not the actual outlook program, the problem occurs. If I close the compose mail window, by either clicking Send, or closing it without sending, the OUTLOOK.EXE task will not exit. If I launch Outlook again, I'll now have multiple instances of OUTLOOK.EXE in task manager. Now the multiple instances is what caused the problem with our custom software at work, but that has nothing to do with the fact that Outlook does not exit correctly when running Spambayes and having a program/mailto link open the Compose Mail window. Yes I realize there have been 2 previous tickets about OUTLOOK.EXE closing, but none came to the conclusion that it's caused by a Compose Mail window. And both are closed without a solution. I have tested this on several computers and have tried multiple things to try to fix it (such as renaming extend.dat and other files) and nothing seems to work. ---------------------------------------------------------------------- >Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 13:30 Message: If someone has a SpamBayes log file from one of these Outlook-won't-exit occurrences, please attach it to this ticket. Thx, Skip ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-08-08 12:37 Message: I'm sorry you are frustrated with our free tool and free support. About all I can suggest is that you avoid using any such outlook plugins which give you this problem, including SpamBayes. You might also like to chat to the authors of some of those other plugins with the same issue so see if they can shed any light for us. ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-08 07:01 Message: It's frustrating to me that SB maintainers keep trying to make this an "Outlook" problem. Yes, obviously it's an Outlook(-related) problem - SB is used as an Outlook plugin!! We have to accept the buggy nature of the host we have chosen to live with. The real issue is as I stated previously- the problem can EASILY be demonstrated to go *completely* away when SB and other offending plugins (e.g. PGP) are disabled, and can EASILY be demonstrated to reappear, consistently, without any ambiguity, when SB and/or other offending plugins are enabled. I will try with SB 1.1a4 and report results again. However we tried 1.1a4 recently on our terminal server (which is the only place I have access to Outlook - I do not use it myself) and it caused some other problems which I don't remember, so I need to be a little cautious. It's a production environment. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 06:41 Message: Jeremy, can you try with SpamBayes 1.1a4? I'm not a Windows user so I can't investigate the problem in any way. I just ran through the entire chain of comments though. It seems that there are other non-SpamBayes ways that this can occur. Also, the fact that it occurs in Outlook 2003 but not Outlook XP suggests this is a bug in Outlook itself. OTOH, the text at the daveswebsite.com link reads, in part: Outlook is notorious for hanging around in the background when a user exits the application. The cause of this is partly a random behavior of Outlook itself and most often a user installed addin that does not release itself from Outlook correctly. Can someone investigate what it means for an addin to "not release itself from Outlook correctly?" ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-07 13:39 Message: This problem still exists in SB 1.0.4 using Outlook/Office 2003 on Windows 2000. It can easily be replicated using VB similar to that posted by fsnyder on 2005-2-25 What's confusing the issue is that the same problem is also caused by other outlook plugins, notably PGP. Running my MSAccess app, with all plugins disabled, the problem does not occur. Exit app, enable SB, try again, problem occurs. Exit app, disable SB, enable PGP, problem occurs. Exit app, disable PGP, disable SB, enable all other plugins, problem does not occur. This is more than a nuisance. Running in a Terminal Services environment, each open instance of Outlook consumes ~30MB of RAM which is the single scarce resource. If one user generates dozens of emails using a batch process, each of which open a copy of Outlook and consume ~30MB RAM, all other users on the server are hosed. I would be very happy to demonstrate this problem to anyone with the skills to correct it, which I do not have. I can supply log files, etc. as needed. ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2008-01-15 20:48 Message: Logged In: YES user_id=366391 Originator: NO Problem still exists... ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2007-07-23 20:43 Message: Logged In: YES user_id=44345 Originator: NO Mark, I'm reassigning this to you to see if you see an easy fix for this problem. -- Skip ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-07-23 19:59 Message: Logged In: YES user_id=366391 Originator: NO The unload problem occurs also while: - start outlook - connect PDA via USB/Active sync - let PDA turned On - close outlook Outlook stays open in background. Now turn off PDA. Normal behavior (without SpamBayes) - outlook closes Bad behavior (With SpamBayes) - outlook stays "hanging" on background This BUG is killing me, because I have to kill the outlook process... And that can cause a damage to the pst file. Problem exists in SpamBayes 1.1a3 and older. PLEASE FIX IT !!! ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-03-24 21:42 Message: Logged In: YES user_id=366391 Originator: NO Its 2007 and this is still not fixed ---------------------------------------------------------------------- Comment By: Sadie (sadie_187) Date: 2006-08-16 17:05 Message: Logged In: YES user_id=1577414 Problem: Outlook 2003 does not terminate the outlook.exe process at closing of the program. Possible Solution (worked for me) : Active sync for my outlook was causing the process to hang. Removed the calendar, contacts sink option; which I rarely use. ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2006-05-23 18:12 Message: Logged In: YES user_id=1369127 To be honest Outlook 2003 was fine for a bit after disabling the spam blocker and then it started with the refusing to shut down again. I finally gave up and paid $5 for an addin that makes sure the program is shut down (http://www.daveswebsite.com/software/olshutdown/ ). I truely do not believe it is SpamBayes causing the trouble as I have it without this program. I have found it often happens if I click on an email link in a browser when the program is not open. I do know I have had this problem for years and I don't use addons in my email as a general rule. ---------------------------------------------------------------------- Comment By: Christian Blackburn (seier) Date: 2006-05-23 16:04 Message: Logged In: YES user_id=561770 Hi NyteTears, > It seems that the spam filter in outlook is causing it to >hang. I wasn't able to reproduce this in Outlook 2003, which is where the problem is at for most people. Perhaps you'd like to tell us what version you're using and the exact steps you took to resolve this. As far as I can tell the problem the rest of us are experiencing is indeed related to SpamBayes' plugin and not outlook itself, although I'm sure in the past with all those security updates the scenario you've described must have been true at least once. Thanks, Christian Blackburn ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 03:24 Message: Logged In: YES user_id=552329 See also: [ 1336405 ] Add-In breaks MAPI control http://sourceforge.net/tracker/index.php?func=detail&aid=1336405&group_id=61702&atid=498104 ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2005-10-27 14:59 Message: Logged In: YES user_id=1369127 I had this problem on my computer and tried removing various different program to fix it. Nothing worked. I have found it is not related to any program outside of outlook. It is an outlook problem. It seems that the spam filter in outlook is causing it to hang. Once I turned off the spam filter that came with outlook I never had the program hang once. I could not tell you why it does this or a fix for it beyond turning the option off but that is the cause of outlook remaining open in the task manager. ---------------------------------------------------------------------- Comment By: Kip Cartwright (kcartwri) Date: 2005-03-29 18:26 Message: Logged In: YES user_id=192708 I have the same problem on Outlook 2003. No problem with Outlook XP (2002). ---------------------------------------------------------------------- Comment By: fsnyder (fsnyder) Date: 2005-02-25 16:00 Message: Logged In: YES user_id=1227716 This behavior of the Outlook.exe not being stopped properly can be duplicated using the following VBScript code. OPTION EXPLICIT On error Resume Next err.clear Dim oOutlookApp, oOutlookNS Set oOutlookApp = GetObject(,"Outlook.Application") if Err <> 0 then MsgBox "Outlook not currently running." & VbCrLf & "Creating New Outlook Application. I'll kill it when I'm done" set oOutlookApp = CreateObject ("Outlook.Application") else MsgBox "Outlook was running. I'll kill it anyway when I'm done." End If MsgBox oOutlookApp.name & " version# " & oOutlookApp.version MsgBox "Now I'll kill the Outlook.exe process the clean way" oOutlookApp.Quit set oOutlookNS = Nothing set oOutlookApp = Nothing MsgBox "END" Run it and watch the TaskManager for when the Outlook.exe process gets created, and killed (as long as the SpamBayes Add-In is NOT activated in Outlook) This should normally kill the process unless some other add- in or anti-virus code is not allowing Outlook to exit cleanly. Hope this Helps -fsnyder ---------------------------------------------------------------------- Comment By: Hal Smith (bpu_webguy) Date: 2005-02-03 12:00 Message: Logged In: YES user_id=842378 One other source of hanging OL up, with or without Spambayes is ActiveSync for your PDA, celll phone or whatever. AS does tend to work behind your back, a little bit. One of the reasons I love Process Explorer from System Internals... -h ---------------------------------------------------------------------- Comment By: Gil (spambayes411) Date: 2005-02-02 04:52 Message: Logged In: YES user_id=1210353 I've discovered this is not limited to the mailto function. I use a program called SynchPST to keep outlook sychronized between my home computer and my laptop. When SynchPST opens, I see it in the task manager and it opens Outlook as well. After I synch my PST files, I close SynchPST. It closes but Outlook remains in the task manager. If the Spambayes add-in is not loaded, then both SynchPST and Outlook quit as they should. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 17:22 Message: Logged In: YES user_id=552329 Thanks Kenny :) I don't really know what might be causing this, but I guess you could start by checking to see if the spambayes log gets to the "addin terminating" part. Let me know if I can help at all (though I don't have OL2003 anywhere). ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2005-01-24 10:23 Message: Logged In: YES user_id=859086 Yep, I was able to confirm this problem on Outlook 2003. If I activate a mailto link with SpamBayes loaded and enabled, OUTLOOK.EXE will not exit when I close the compose window. If I disable SpamBayes filtering from SpamBayes Manager, OUTLOOK.EXE still doesn't exit. If I completely disable loading of SpamBayes from the COM Add-ins dialog then OUTLOOK.EXE closes properly when I close the compose window. I'll look into this further when I get a chance. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-23 23:53 Message: Logged In: YES user_id=552329 Maybe this is specific to Outlook 2003 then? Kenny: you've got 2003, right? Can you try and replicate this? ---------------------------------------------------------------------- Comment By: robert (elitemrp) Date: 2005-01-21 05:49 Message: Logged In: YES user_id=1198932 Yes, it only happens with SpamBayes installed. I install SpamBayes, set up the toolbar, etc Close Outlook, type mailto:blah at blah.com in a browser or click a mail link and it opens the Compose Mail window. Once I close this window, Outlook.exe ramains in the task list. If I click another mailto link I'll have 2 stuck open, then 3, etc If I have only 1 process loaded and it's the main Outlook window, when I click a mailto link it will work fine since it doesn't load a separate outlook.exe process. It only does this when the main outlook program isn't loaded. Once I uninstall SpamBayes or uncheck it in the COM Add-Ins area in Outlook, this problem goes away. As soon as I close a Compose Mail window, OUTLOOK.EXE terminates correctly. I've tried this on several PCs, some with fresh installs of XP/ Outlook, some with several months old installs and other applications, it's the same on each. Thanks ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-20 21:17 Message: Logged In: YES user_id=552329 Have you tried this without SpamBayes installed? I get the same behaviour without SpamBayes, which says to me it's an Outlook problem, not a SpamBayes one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 From noreply at sourceforge.net Sat Aug 8 22:56:42 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 08 Aug 2009 20:56:42 +0000 Subject: [spambayes-bugs] [ spambayes-Bugs-1103976 ] Outlook.exe will not terminate when launched via mailto Message-ID: Bugs item #1103976, was opened at 2005-01-17 09:56 Message generated for change (Comment added) made by montanaro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: 1.1.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: robert (elitemrp) Assigned to: Mark Hammond (mhammond) Summary: Outlook.exe will not terminate when launched via mailto Initial Comment: I first ran into this problem a few months ago at work. But at the time I thought it was related to a custom program we run here. But now I noticed I can easily reproduce the problem on any computer running SpamBayes+Outlook 2003 on Windows XP. Basically, I will open Outlook via the icon to read mail. I will then close Outlook, and if I have Task Manager open, I will see that Outlook.exe closes correctly. Now if I launch a mailto: link (or use a program that launches a new mail), where the Compose Mail window opens, but not the actual outlook program, the problem occurs. If I close the compose mail window, by either clicking Send, or closing it without sending, the OUTLOOK.EXE task will not exit. If I launch Outlook again, I'll now have multiple instances of OUTLOOK.EXE in task manager. Now the multiple instances is what caused the problem with our custom software at work, but that has nothing to do with the fact that Outlook does not exit correctly when running Spambayes and having a program/mailto link open the Compose Mail window. Yes I realize there have been 2 previous tickets about OUTLOOK.EXE closing, but none came to the conclusion that it's caused by a Compose Mail window. And both are closed without a solution. I have tested this on several computers and have tried multiple things to try to fix it (such as renaming extend.dat and other files) and nothing seems to work. ---------------------------------------------------------------------- >Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 15:56 Message: A couple things from the Microsoft support website: http://support.microsoft.com/kb/208332/ http://support.microsoft.com/kb/294867/ Those items are for OL 2000 and 2002. I could find no similar knowledge base article for OL 2003. As far as I can tell from reading the above articles and the Outlook add-in code, the add-in is doing what it's supposed to do. If someone finds an appropriate article which seems to related to OL 2003, please reference it here. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 13:30 Message: If someone has a SpamBayes log file from one of these Outlook-won't-exit occurrences, please attach it to this ticket. Thx, Skip ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-08-08 12:37 Message: I'm sorry you are frustrated with our free tool and free support. About all I can suggest is that you avoid using any such outlook plugins which give you this problem, including SpamBayes. You might also like to chat to the authors of some of those other plugins with the same issue so see if they can shed any light for us. ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-08 07:01 Message: It's frustrating to me that SB maintainers keep trying to make this an "Outlook" problem. Yes, obviously it's an Outlook(-related) problem - SB is used as an Outlook plugin!! We have to accept the buggy nature of the host we have chosen to live with. The real issue is as I stated previously- the problem can EASILY be demonstrated to go *completely* away when SB and other offending plugins (e.g. PGP) are disabled, and can EASILY be demonstrated to reappear, consistently, without any ambiguity, when SB and/or other offending plugins are enabled. I will try with SB 1.1a4 and report results again. However we tried 1.1a4 recently on our terminal server (which is the only place I have access to Outlook - I do not use it myself) and it caused some other problems which I don't remember, so I need to be a little cautious. It's a production environment. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 06:41 Message: Jeremy, can you try with SpamBayes 1.1a4? I'm not a Windows user so I can't investigate the problem in any way. I just ran through the entire chain of comments though. It seems that there are other non-SpamBayes ways that this can occur. Also, the fact that it occurs in Outlook 2003 but not Outlook XP suggests this is a bug in Outlook itself. OTOH, the text at the daveswebsite.com link reads, in part: Outlook is notorious for hanging around in the background when a user exits the application. The cause of this is partly a random behavior of Outlook itself and most often a user installed addin that does not release itself from Outlook correctly. Can someone investigate what it means for an addin to "not release itself from Outlook correctly?" ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-07 13:39 Message: This problem still exists in SB 1.0.4 using Outlook/Office 2003 on Windows 2000. It can easily be replicated using VB similar to that posted by fsnyder on 2005-2-25 What's confusing the issue is that the same problem is also caused by other outlook plugins, notably PGP. Running my MSAccess app, with all plugins disabled, the problem does not occur. Exit app, enable SB, try again, problem occurs. Exit app, disable SB, enable PGP, problem occurs. Exit app, disable PGP, disable SB, enable all other plugins, problem does not occur. This is more than a nuisance. Running in a Terminal Services environment, each open instance of Outlook consumes ~30MB of RAM which is the single scarce resource. If one user generates dozens of emails using a batch process, each of which open a copy of Outlook and consume ~30MB RAM, all other users on the server are hosed. I would be very happy to demonstrate this problem to anyone with the skills to correct it, which I do not have. I can supply log files, etc. as needed. ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2008-01-15 20:48 Message: Logged In: YES user_id=366391 Originator: NO Problem still exists... ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2007-07-23 20:43 Message: Logged In: YES user_id=44345 Originator: NO Mark, I'm reassigning this to you to see if you see an easy fix for this problem. -- Skip ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-07-23 19:59 Message: Logged In: YES user_id=366391 Originator: NO The unload problem occurs also while: - start outlook - connect PDA via USB/Active sync - let PDA turned On - close outlook Outlook stays open in background. Now turn off PDA. Normal behavior (without SpamBayes) - outlook closes Bad behavior (With SpamBayes) - outlook stays "hanging" on background This BUG is killing me, because I have to kill the outlook process... And that can cause a damage to the pst file. Problem exists in SpamBayes 1.1a3 and older. PLEASE FIX IT !!! ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-03-24 21:42 Message: Logged In: YES user_id=366391 Originator: NO Its 2007 and this is still not fixed ---------------------------------------------------------------------- Comment By: Sadie (sadie_187) Date: 2006-08-16 17:05 Message: Logged In: YES user_id=1577414 Problem: Outlook 2003 does not terminate the outlook.exe process at closing of the program. Possible Solution (worked for me) : Active sync for my outlook was causing the process to hang. Removed the calendar, contacts sink option; which I rarely use. ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2006-05-23 18:12 Message: Logged In: YES user_id=1369127 To be honest Outlook 2003 was fine for a bit after disabling the spam blocker and then it started with the refusing to shut down again. I finally gave up and paid $5 for an addin that makes sure the program is shut down (http://www.daveswebsite.com/software/olshutdown/ ). I truely do not believe it is SpamBayes causing the trouble as I have it without this program. I have found it often happens if I click on an email link in a browser when the program is not open. I do know I have had this problem for years and I don't use addons in my email as a general rule. ---------------------------------------------------------------------- Comment By: Christian Blackburn (seier) Date: 2006-05-23 16:04 Message: Logged In: YES user_id=561770 Hi NyteTears, > It seems that the spam filter in outlook is causing it to >hang. I wasn't able to reproduce this in Outlook 2003, which is where the problem is at for most people. Perhaps you'd like to tell us what version you're using and the exact steps you took to resolve this. As far as I can tell the problem the rest of us are experiencing is indeed related to SpamBayes' plugin and not outlook itself, although I'm sure in the past with all those security updates the scenario you've described must have been true at least once. Thanks, Christian Blackburn ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 03:24 Message: Logged In: YES user_id=552329 See also: [ 1336405 ] Add-In breaks MAPI control http://sourceforge.net/tracker/index.php?func=detail&aid=1336405&group_id=61702&atid=498104 ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2005-10-27 14:59 Message: Logged In: YES user_id=1369127 I had this problem on my computer and tried removing various different program to fix it. Nothing worked. I have found it is not related to any program outside of outlook. It is an outlook problem. It seems that the spam filter in outlook is causing it to hang. Once I turned off the spam filter that came with outlook I never had the program hang once. I could not tell you why it does this or a fix for it beyond turning the option off but that is the cause of outlook remaining open in the task manager. ---------------------------------------------------------------------- Comment By: Kip Cartwright (kcartwri) Date: 2005-03-29 18:26 Message: Logged In: YES user_id=192708 I have the same problem on Outlook 2003. No problem with Outlook XP (2002). ---------------------------------------------------------------------- Comment By: fsnyder (fsnyder) Date: 2005-02-25 16:00 Message: Logged In: YES user_id=1227716 This behavior of the Outlook.exe not being stopped properly can be duplicated using the following VBScript code. OPTION EXPLICIT On error Resume Next err.clear Dim oOutlookApp, oOutlookNS Set oOutlookApp = GetObject(,"Outlook.Application") if Err <> 0 then MsgBox "Outlook not currently running." & VbCrLf & "Creating New Outlook Application. I'll kill it when I'm done" set oOutlookApp = CreateObject ("Outlook.Application") else MsgBox "Outlook was running. I'll kill it anyway when I'm done." End If MsgBox oOutlookApp.name & " version# " & oOutlookApp.version MsgBox "Now I'll kill the Outlook.exe process the clean way" oOutlookApp.Quit set oOutlookNS = Nothing set oOutlookApp = Nothing MsgBox "END" Run it and watch the TaskManager for when the Outlook.exe process gets created, and killed (as long as the SpamBayes Add-In is NOT activated in Outlook) This should normally kill the process unless some other add- in or anti-virus code is not allowing Outlook to exit cleanly. Hope this Helps -fsnyder ---------------------------------------------------------------------- Comment By: Hal Smith (bpu_webguy) Date: 2005-02-03 12:00 Message: Logged In: YES user_id=842378 One other source of hanging OL up, with or without Spambayes is ActiveSync for your PDA, celll phone or whatever. AS does tend to work behind your back, a little bit. One of the reasons I love Process Explorer from System Internals... -h ---------------------------------------------------------------------- Comment By: Gil (spambayes411) Date: 2005-02-02 04:52 Message: Logged In: YES user_id=1210353 I've discovered this is not limited to the mailto function. I use a program called SynchPST to keep outlook sychronized between my home computer and my laptop. When SynchPST opens, I see it in the task manager and it opens Outlook as well. After I synch my PST files, I close SynchPST. It closes but Outlook remains in the task manager. If the Spambayes add-in is not loaded, then both SynchPST and Outlook quit as they should. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 17:22 Message: Logged In: YES user_id=552329 Thanks Kenny :) I don't really know what might be causing this, but I guess you could start by checking to see if the spambayes log gets to the "addin terminating" part. Let me know if I can help at all (though I don't have OL2003 anywhere). ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2005-01-24 10:23 Message: Logged In: YES user_id=859086 Yep, I was able to confirm this problem on Outlook 2003. If I activate a mailto link with SpamBayes loaded and enabled, OUTLOOK.EXE will not exit when I close the compose window. If I disable SpamBayes filtering from SpamBayes Manager, OUTLOOK.EXE still doesn't exit. If I completely disable loading of SpamBayes from the COM Add-ins dialog then OUTLOOK.EXE closes properly when I close the compose window. I'll look into this further when I get a chance. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-23 23:53 Message: Logged In: YES user_id=552329 Maybe this is specific to Outlook 2003 then? Kenny: you've got 2003, right? Can you try and replicate this? ---------------------------------------------------------------------- Comment By: robert (elitemrp) Date: 2005-01-21 05:49 Message: Logged In: YES user_id=1198932 Yes, it only happens with SpamBayes installed. I install SpamBayes, set up the toolbar, etc Close Outlook, type mailto:blah at blah.com in a browser or click a mail link and it opens the Compose Mail window. Once I close this window, Outlook.exe ramains in the task list. If I click another mailto link I'll have 2 stuck open, then 3, etc If I have only 1 process loaded and it's the main Outlook window, when I click a mailto link it will work fine since it doesn't load a separate outlook.exe process. It only does this when the main outlook program isn't loaded. Once I uninstall SpamBayes or uncheck it in the COM Add-Ins area in Outlook, this problem goes away. As soon as I close a Compose Mail window, OUTLOOK.EXE terminates correctly. I've tried this on several PCs, some with fresh installs of XP/ Outlook, some with several months old installs and other applications, it's the same on each. Thanks ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-20 21:17 Message: Logged In: YES user_id=552329 Have you tried this without SpamBayes installed? I get the same behaviour without SpamBayes, which says to me it's an Outlook problem, not a SpamBayes one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 From noreply at sourceforge.net Sun Aug 9 15:33:30 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 09 Aug 2009 13:33:30 +0000 Subject: [spambayes-bugs] [ spambayes-Bugs-1103976 ] Outlook.exe will not terminate when launched via mailto Message-ID: Bugs item #1103976, was opened at 2005-01-17 10:56 Message generated for change (Comment added) made by jeremydunn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: 1.1.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: robert (elitemrp) Assigned to: Mark Hammond (mhammond) Summary: Outlook.exe will not terminate when launched via mailto Initial Comment: I first ran into this problem a few months ago at work. But at the time I thought it was related to a custom program we run here. But now I noticed I can easily reproduce the problem on any computer running SpamBayes+Outlook 2003 on Windows XP. Basically, I will open Outlook via the icon to read mail. I will then close Outlook, and if I have Task Manager open, I will see that Outlook.exe closes correctly. Now if I launch a mailto: link (or use a program that launches a new mail), where the Compose Mail window opens, but not the actual outlook program, the problem occurs. If I close the compose mail window, by either clicking Send, or closing it without sending, the OUTLOOK.EXE task will not exit. If I launch Outlook again, I'll now have multiple instances of OUTLOOK.EXE in task manager. Now the multiple instances is what caused the problem with our custom software at work, but that has nothing to do with the fact that Outlook does not exit correctly when running Spambayes and having a program/mailto link open the Compose Mail window. Yes I realize there have been 2 previous tickets about OUTLOOK.EXE closing, but none came to the conclusion that it's caused by a Compose Mail window. And both are closed without a solution. I have tested this on several computers and have tried multiple things to try to fix it (such as renaming extend.dat and other files) and nothing seems to work. ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-09 09:33 Message: First, please accept my apologies for the irritated tone of my previous post. Actually I like SB very much! But this little problem is quite annoying, and my annoyance is proportional to how helpful SB is. If it wasn't helpful I would just get rid of it. So, thanks to everyone who is working on it - I appreciate that this is a labor of love and service. I've verified the problem still exists in SB 1.1a4-070629.exe release. (For some reason, after installing, this release reports version 1.1a3 in SB manager. Perhaps the version number wasn't updated in the build?). I didn't know the log levels so I arbitrarily set it to '10'. I will try to attach logs next. re: other clues, there is another Outlook plugin called "Redemption" that provides full access to the Extended MAPI COM object, and can be used to bypass security warnings when sending email throught Outlook using COM. http://www.dimastr.com/redemption/ I cannot give a direct link to the page since the URL does not change, but if you press "FAQ" at the top, then look at item #5, you will see "My code using Redemption is causing Outlook to stay in memory even after it is closed." The author of this plugin suggests "To fix the problem, call MAPIUtils.Cleanup or AddressEntry.Cleanup (or SafeCurrentUser.Cleanup); this will cause Redemption to release the Extended MAPI session." I tried this solution when calling SB but it did not help. But I'm wondering if this could be a clue to how SB must release its hold on Outlook so OL can exit. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 16:56 Message: A couple things from the Microsoft support website: http://support.microsoft.com/kb/208332/ http://support.microsoft.com/kb/294867/ Those items are for OL 2000 and 2002. I could find no similar knowledge base article for OL 2003. As far as I can tell from reading the above articles and the Outlook add-in code, the add-in is doing what it's supposed to do. If someone finds an appropriate article which seems to related to OL 2003, please reference it here. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 14:30 Message: If someone has a SpamBayes log file from one of these Outlook-won't-exit occurrences, please attach it to this ticket. Thx, Skip ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-08-08 13:37 Message: I'm sorry you are frustrated with our free tool and free support. About all I can suggest is that you avoid using any such outlook plugins which give you this problem, including SpamBayes. You might also like to chat to the authors of some of those other plugins with the same issue so see if they can shed any light for us. ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-08 08:01 Message: It's frustrating to me that SB maintainers keep trying to make this an "Outlook" problem. Yes, obviously it's an Outlook(-related) problem - SB is used as an Outlook plugin!! We have to accept the buggy nature of the host we have chosen to live with. The real issue is as I stated previously- the problem can EASILY be demonstrated to go *completely* away when SB and other offending plugins (e.g. PGP) are disabled, and can EASILY be demonstrated to reappear, consistently, without any ambiguity, when SB and/or other offending plugins are enabled. I will try with SB 1.1a4 and report results again. However we tried 1.1a4 recently on our terminal server (which is the only place I have access to Outlook - I do not use it myself) and it caused some other problems which I don't remember, so I need to be a little cautious. It's a production environment. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2009-08-08 07:41 Message: Jeremy, can you try with SpamBayes 1.1a4? I'm not a Windows user so I can't investigate the problem in any way. I just ran through the entire chain of comments though. It seems that there are other non-SpamBayes ways that this can occur. Also, the fact that it occurs in Outlook 2003 but not Outlook XP suggests this is a bug in Outlook itself. OTOH, the text at the daveswebsite.com link reads, in part: Outlook is notorious for hanging around in the background when a user exits the application. The cause of this is partly a random behavior of Outlook itself and most often a user installed addin that does not release itself from Outlook correctly. Can someone investigate what it means for an addin to "not release itself from Outlook correctly?" ---------------------------------------------------------------------- Comment By: Jeremy Dunn (jeremydunn) Date: 2009-08-07 14:39 Message: This problem still exists in SB 1.0.4 using Outlook/Office 2003 on Windows 2000. It can easily be replicated using VB similar to that posted by fsnyder on 2005-2-25 What's confusing the issue is that the same problem is also caused by other outlook plugins, notably PGP. Running my MSAccess app, with all plugins disabled, the problem does not occur. Exit app, enable SB, try again, problem occurs. Exit app, disable SB, enable PGP, problem occurs. Exit app, disable PGP, disable SB, enable all other plugins, problem does not occur. This is more than a nuisance. Running in a Terminal Services environment, each open instance of Outlook consumes ~30MB of RAM which is the single scarce resource. If one user generates dozens of emails using a batch process, each of which open a copy of Outlook and consume ~30MB RAM, all other users on the server are hosed. I would be very happy to demonstrate this problem to anyone with the skills to correct it, which I do not have. I can supply log files, etc. as needed. ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2008-01-15 21:48 Message: Logged In: YES user_id=366391 Originator: NO Problem still exists... ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2007-07-23 21:43 Message: Logged In: YES user_id=44345 Originator: NO Mark, I'm reassigning this to you to see if you see an easy fix for this problem. -- Skip ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-07-23 20:59 Message: Logged In: YES user_id=366391 Originator: NO The unload problem occurs also while: - start outlook - connect PDA via USB/Active sync - let PDA turned On - close outlook Outlook stays open in background. Now turn off PDA. Normal behavior (without SpamBayes) - outlook closes Bad behavior (With SpamBayes) - outlook stays "hanging" on background This BUG is killing me, because I have to kill the outlook process... And that can cause a damage to the pst file. Problem exists in SpamBayes 1.1a3 and older. PLEASE FIX IT !!! ---------------------------------------------------------------------- Comment By: SelfMan (selfman) Date: 2007-03-24 22:42 Message: Logged In: YES user_id=366391 Originator: NO Its 2007 and this is still not fixed ---------------------------------------------------------------------- Comment By: Sadie (sadie_187) Date: 2006-08-16 18:05 Message: Logged In: YES user_id=1577414 Problem: Outlook 2003 does not terminate the outlook.exe process at closing of the program. Possible Solution (worked for me) : Active sync for my outlook was causing the process to hang. Removed the calendar, contacts sink option; which I rarely use. ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2006-05-23 19:12 Message: Logged In: YES user_id=1369127 To be honest Outlook 2003 was fine for a bit after disabling the spam blocker and then it started with the refusing to shut down again. I finally gave up and paid $5 for an addin that makes sure the program is shut down (http://www.daveswebsite.com/software/olshutdown/ ). I truely do not believe it is SpamBayes causing the trouble as I have it without this program. I have found it often happens if I click on an email link in a browser when the program is not open. I do know I have had this problem for years and I don't use addons in my email as a general rule. ---------------------------------------------------------------------- Comment By: Christian Blackburn (seier) Date: 2006-05-23 17:04 Message: Logged In: YES user_id=561770 Hi NyteTears, > It seems that the spam filter in outlook is causing it to >hang. I wasn't able to reproduce this in Outlook 2003, which is where the problem is at for most people. Perhaps you'd like to tell us what version you're using and the exact steps you took to resolve this. As far as I can tell the problem the rest of us are experiencing is indeed related to SpamBayes' plugin and not outlook itself, although I'm sure in the past with all those security updates the scenario you've described must have been true at least once. Thanks, Christian Blackburn ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 04:24 Message: Logged In: YES user_id=552329 See also: [ 1336405 ] Add-In breaks MAPI control http://sourceforge.net/tracker/index.php?func=detail&aid=1336405&group_id=61702&atid=498104 ---------------------------------------------------------------------- Comment By: Nytetears (nytetears) Date: 2005-10-27 15:59 Message: Logged In: YES user_id=1369127 I had this problem on my computer and tried removing various different program to fix it. Nothing worked. I have found it is not related to any program outside of outlook. It is an outlook problem. It seems that the spam filter in outlook is causing it to hang. Once I turned off the spam filter that came with outlook I never had the program hang once. I could not tell you why it does this or a fix for it beyond turning the option off but that is the cause of outlook remaining open in the task manager. ---------------------------------------------------------------------- Comment By: Kip Cartwright (kcartwri) Date: 2005-03-29 19:26 Message: Logged In: YES user_id=192708 I have the same problem on Outlook 2003. No problem with Outlook XP (2002). ---------------------------------------------------------------------- Comment By: fsnyder (fsnyder) Date: 2005-02-25 17:00 Message: Logged In: YES user_id=1227716 This behavior of the Outlook.exe not being stopped properly can be duplicated using the following VBScript code. OPTION EXPLICIT On error Resume Next err.clear Dim oOutlookApp, oOutlookNS Set oOutlookApp = GetObject(,"Outlook.Application") if Err <> 0 then MsgBox "Outlook not currently running." & VbCrLf & "Creating New Outlook Application. I'll kill it when I'm done" set oOutlookApp = CreateObject ("Outlook.Application") else MsgBox "Outlook was running. I'll kill it anyway when I'm done." End If MsgBox oOutlookApp.name & " version# " & oOutlookApp.version MsgBox "Now I'll kill the Outlook.exe process the clean way" oOutlookApp.Quit set oOutlookNS = Nothing set oOutlookApp = Nothing MsgBox "END" Run it and watch the TaskManager for when the Outlook.exe process gets created, and killed (as long as the SpamBayes Add-In is NOT activated in Outlook) This should normally kill the process unless some other add- in or anti-virus code is not allowing Outlook to exit cleanly. Hope this Helps -fsnyder ---------------------------------------------------------------------- Comment By: Hal Smith (bpu_webguy) Date: 2005-02-03 13:00 Message: Logged In: YES user_id=842378 One other source of hanging OL up, with or without Spambayes is ActiveSync for your PDA, celll phone or whatever. AS does tend to work behind your back, a little bit. One of the reasons I love Process Explorer from System Internals... -h ---------------------------------------------------------------------- Comment By: Gil (spambayes411) Date: 2005-02-02 05:52 Message: Logged In: YES user_id=1210353 I've discovered this is not limited to the mailto function. I use a program called SynchPST to keep outlook sychronized between my home computer and my laptop. When SynchPST opens, I see it in the task manager and it opens Outlook as well. After I synch my PST files, I close SynchPST. It closes but Outlook remains in the task manager. If the Spambayes add-in is not loaded, then both SynchPST and Outlook quit as they should. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 18:22 Message: Logged In: YES user_id=552329 Thanks Kenny :) I don't really know what might be causing this, but I guess you could start by checking to see if the spambayes log gets to the "addin terminating" part. Let me know if I can help at all (though I don't have OL2003 anywhere). ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2005-01-24 11:23 Message: Logged In: YES user_id=859086 Yep, I was able to confirm this problem on Outlook 2003. If I activate a mailto link with SpamBayes loaded and enabled, OUTLOOK.EXE will not exit when I close the compose window. If I disable SpamBayes filtering from SpamBayes Manager, OUTLOOK.EXE still doesn't exit. If I completely disable loading of SpamBayes from the COM Add-ins dialog then OUTLOOK.EXE closes properly when I close the compose window. I'll look into this further when I get a chance. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-24 00:53 Message: Logged In: YES user_id=552329 Maybe this is specific to Outlook 2003 then? Kenny: you've got 2003, right? Can you try and replicate this? ---------------------------------------------------------------------- Comment By: robert (elitemrp) Date: 2005-01-21 06:49 Message: Logged In: YES user_id=1198932 Yes, it only happens with SpamBayes installed. I install SpamBayes, set up the toolbar, etc Close Outlook, type mailto:blah at blah.com in a browser or click a mail link and it opens the Compose Mail window. Once I close this window, Outlook.exe ramains in the task list. If I click another mailto link I'll have 2 stuck open, then 3, etc If I have only 1 process loaded and it's the main Outlook window, when I click a mailto link it will work fine since it doesn't load a separate outlook.exe process. It only does this when the main outlook program isn't loaded. Once I uninstall SpamBayes or uncheck it in the COM Add-Ins area in Outlook, this problem goes away. As soon as I close a Compose Mail window, OUTLOOK.EXE terminates correctly. I've tried this on several PCs, some with fresh installs of XP/ Outlook, some with several months old installs and other applications, it's the same on each. Thanks ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2005-01-20 22:17 Message: Logged In: YES user_id=552329 Have you tried this without SpamBayes installed? I get the same behaviour without SpamBayes, which says to me it's an Outlook problem, not a SpamBayes one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1103976&group_id=61702