Hi
list,
Following from the
"Spambayes crashes my Outlook" thread, I thought I would post more details
on my experience with a similar Outlook crash / crippled Outlook issue
which I was able to workaround with a small change in source. This problem
occurs in Outlook 2000 and 2003 (maybe others), with CommuniGate MAPI
Intel 1.2.1, 1.2.2
Problem:
SpamBayes'
logic on startup of the configuration wizard is to loop
through all entries in the Message Stores Table, then ask each one for a receive
folder (ie Inbox). The Communigate MAPI connector returns multiple
entries from this call, the first of which responds with the proper "Inbox"
folder when asked for the Receive Folder. It then causes an access
violation when the next store entry is asked for it's Receive Folder. Not
sure why a second store entry even exists.
Workaround:
Modify a single line of code to eliminate the multi-store loop. The
assumption here is that you only need one store (probably true if you're running
a CommuniGate server).
Source file:
spambayes/Outlook2000/msgstore.py
In the
YieldReceiveFolders function, comment out the "for row in rows:" line and
replace with "if True:"
Thanks to the well
written code by the contributors, and good development documentation, this
did not take long to find, modify, and re-package for our internal
needs.
If someone is so
inclined to work a permanent solution around this such as an installation
option to only allow a single message store, or to coach me on how to do this
quickly, it may help others with other similar Outlook environment
issues.
thanks,
Roland;
_______________________________________________ [email protected] http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
