[spambayes-bugs] [ spambayes-Bugs-836018 ] MAPI_E_NOT_ENOUGH_MEMORY
when filtering lots of spam
SourceForge.net
noreply at sourceforge.net
Sat Jan 3 12:41:19 EST 2004
Bugs item #836018, was opened at 2003-11-04 15:23
Message generated for change (Comment added) made by tagrobicki
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=836018&group_id=61702
Category: Outlook
Group: Outlook 008
Status: Open
Resolution: None
Priority: 5
Submitted By: Thomas A. Grobicki (tagrobicki)
Assigned to: Mark Hammond (mhammond)
Summary: MAPI_E_NOT_ENOUGH_MEMORY when filtering lots of spam
Initial Comment:
I recieve the following error when filtering approximately
1247 spam messages:
Moving a message failed due to an unexpected Outlook
error. Exception 0x8007000e
(MAPI_E_NOT_ENOUGH_MEMORY): Not enough storage
is available to complete this operation.
At which point, it appears that SpamBayes stops
working. Outlook continues to work, but the dialog
recommends restarting it. This happened in version 0.81
running on WinXP Pro with all patches using Outlook
2002 (10.4712.4219) SP2.
----------------------------------------------------------------------
>Comment By: Thomas A. Grobicki (tagrobicki)
Date: 2004-01-03 12:41
Message:
Logged In: YES
user_id=901893
Another quick note on this one. It happened again after 24-
36 hours of continuous operation filtering messages. After it
happened, I acknowledged the error and then ran a bulk filter
on approximately 500 messages that had accumulated.
SpamBayes continued to operate fine as did Outlook without
the exit. I then let Outloook continue running without exiting,
and SpamBayes continued to do filtering.
----------------------------------------------------------------------
Comment By: Thomas A. Grobicki (tagrobicki)
Date: 2003-12-29 23:19
Message:
Logged In: YES
user_id=901893
In response to the various questions: (1) It does tend to
happen after the system has been up for many hours to
possibly many days (2) I do not have PGP installed, (3) I was
doing normal filtering but of a "spam" account we have on our
mail server which receives 1000-2000 messages, the purpose
is to catch false positives from the mail server (4) The mail
server is not MS Exchange, I did look at MSDN before
reporting this and didn't see anything that applied to my
situation (5) Outlook appears to continue working, in fact, it
continues downloading the remaining spam messages but it
doesn't do any SpamBayes filtering until I exit and re-enter at
which point is filters out spam messages.
I have not looked at the message preceeding the error, but I
will the next time it comes up. I do have Norton ISS
installed, but its spam filter is disabled. I also have a few
Outlook filtering rules to move specific messages into some
folders. However, the dialog clearly says that it is SpamBayes
that is having issue possibly due to underlying Outlook
problems.
----------------------------------------------------------------------
Comment By: Mark Hammond (mhammond)
Date: 2003-12-29 19:58
Message:
Logged In: YES
user_id=14198
I have previously seen tracebacks similar to the one posted
when filtering single incoming messages. IIRC, this was
when I used the PGP plugin, but it had nothing to do with
SpamBayes - Outlook itself was also screwed, and almost all
Outlook operations would also fail, with Outlook displaying
a dialog saying it too was out of memory. This happened
after only 24 hours or so of uptime when PGP was enabled,
and has never once happened when disabled.
tagrobicki - is the error in the log you posted a result of
doing a "bulk score" of a folder, or simply after normal
filtering of (many) new incoming messages? If the latter,
did Outlook itself also appear to be dead after you saw this
message? If so, do you have any other addins loaded? If
you do have the PGP plugin installed, please close this bug
as "wont fix" (only as there is a 'can't fix' :)
I'm reluctant to say that this is a simple memory leak in
SpamBayes, else I would expect far more users to see it. My
outlook shows no evidence of leaks after many many hours and
messages.
----------------------------------------------------------------------
Comment By: Tony Meyer (anadelonbrin)
Date: 2003-12-29 19:41
Message:
Logged In: YES
user_id=552329
Are you using Exchange? Microsoft's support stuff has info
saying that this can be something that Exchange can do (if I
read it right). (It also said that this happened with copying
messages with a lot of attachments, but only with NT4, so I
presume that isn't relevant here).
Are you able to find the 'discounted Rx Xanax segundo'
message and see if there's anything unusual about it?
----------------------------------------------------------------------
Comment By: Thomas A. Grobicki (tagrobicki)
Date: 2003-12-29 08:16
Message:
Logged In: YES
user_id=901893
I have uploaded a log file (minus some "Message" lines to get
it below size restrictions on uploads). The error appears at
the bottom. I've added it here just so you don't have to
download the file.
Message 'discounted Rx Xanax segundo' had a Spam
classification of 'Yes'
ERROR: 'Moving a message failed due to an unexpected
Outlook error.\r\nException 0x8007000e
(MAPI_E_NOT_ENOUGH_MEMORY): Not enough storage is
available to complete this operation.\r\n\r\nIt is
recommended you restart Outlook at the earliest
opportunity\r\n\r\nThis message will not be reported again
until SpamBayes\r\nis restarted.'
Traceback (most recent call last):
File "out1.pyz/msgstore", line 1075, in MoveToReportingError
File "out1.pyz/msgstore", line 1062, in MoveTo
File "out1.pyz/msgstore", line 1059, in _DoCopyMove
MsgStoreException: MsgStoreException: Exception
0x8007000e (MAPI_E_NOT_ENOUGH_MEMORY): Not enough
storage is available to complete this operation.
ERROR: 'Moving a message failed due to an unexpected
Outlook error.\r\nException 0x8007000e
(MAPI_E_NOT_ENOUGH_MEMORY): Not enough storage is
available to complete this operation.\r\n\r\nIt is
recommended you restart Outlook at the earliest
opportunity\r\n\r\nThis message will not be reported again
until SpamBayes\r\nis restarted.'
Traceback (most recent call last):
File "out1.pyz/msgstore", line 1075, in MoveToReportingError
File "out1.pyz/msgstore", line 1062, in MoveTo
File "out1.pyz/msgstore", line 1059, in _DoCopyMove
MsgStoreException: MsgStoreException: Exception
0x8007000e (MAPI_E_NOT_ENOUGH_MEMORY): Not enough
storage is available to complete this operation.
Message 'weekend entertainment' had a Spam classification
of 'Yes'
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2003-12-18 23:44
Message:
Logged In: YES
user_id=31435
Me too (I routinely filter thousands more msgs than that).
It's more likely a specific single message that's causing a
problem. OTOH, we're simply moving a message (according to
the error msg), and it's hard to imagine how that could
provoke an out-of-memory response.
----------------------------------------------------------------------
Comment By: Mark Hammond (mhammond)
Date: 2003-12-18 23:21
Message:
Logged In: YES
user_id=14198
I'm sure I followed this up earlier, but it seems to have
got lost :( I've seen SpamBayes successfully score far more
messages than that without an error. Could you please
attach a log for the session.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=836018&group_id=61702
More information about the Spambayes-bugs
mailing list