#910 issues with installing spambayes to outlook2010 Porf plus from sourcecode 1.1a6

[Anonymous]

I am trying to install spambayes-1.1a6 from source code. after installing python package, I install setup.py on command prompt which runs fine, then I install addin.py from outlook200 folder. But when I go to Outlook Professional Plus 2010 , it does not show addin at all. I have been trying this for over a month with different versiosn of python and win32 com extensions (pywin32-218.win-amd64-py2.7 and pywin32-219.win-amd64-py2.7) but nothign is working

This is so frustrating...pls help!!! Thanks

[Anonymous]

while installing win32 com extension , it gives this error msg on the last screen (see attachement). could it have something to do with this?

[Anonymous]

however, It also completes the registration of addin successfulyl as per the attachment but addin is blank in Outlook Professional Plus 2010 :(

Any advise???

[Mark Hammond]

Spambayes is largely dead these days, but you could try installing the 32bit version of Python and pywin32 to see if that helps.

[Anonymous]

Thanks

Do you think you could advise something on this below??

I am using Outlook 2010 in Windows 7 Enterprise. I tried to install SpamBayes Add-in for my Outlook 2010. I first tried the exe installer file (1.1a6), it worked fine. I then removed the Outlook add-in from my Outlook 2010 and tried to install the add-in from Python sources. I downloaded the zip file spambayes-1.1a6.zip. Before I ran the addin.py script, I installed Python 2.3 and Python Extension 2.3 (exactly as described in the README file). I went to the outlook2000 folder and fired up addin.py. I opened Outlook 2010, but the Spambayes add-in could not be loaded. I opened my Outlook Options to check the Add-ins. The Add-in name (SpamBayes) was there, but the Location for the Add-in seemed incorrect (shown as pythoncom23.dll, file name only. No path at all). I would like to see something like Outlook-addin.dll. To check the error message, I ran win32traceutil.py (from the win32all extensions console) but no error messages were found.

I was wondering if spambayes-1.1a6.zip works with Outlook 2010, or it only works with Outlook 2000?

[Mark Hammond]

That all points to needing the 32bit version of Python and pywin32 rather than the 64bit version you are trying - or just use the binary that you said works.

[Anonymous]

Thanks, I am using 32bit version of Python and pywin32 , still not working. I want to use the source code version rather than .exe as I am trying to do some experimentation with it. Could you pls suggest what else could we try? Pls advise Thanks

[Mark Hammond]

You said you were using pywin32-219.win-amd64-py2.7, which is a 64bit version. You must also have Python installed "for all users", so pythoncomxx.dll should appear in your c:\windows\syswow64 directory. Given win32traceutil shows no output, the problem is that outlook itself is refusing to load it - I'm not sure why it might do that, but looking for general solutions to outlook not loading addons and how to debug or diagnose that might be worthwhile.

[Anonymous]

Then I had used python-2.3 and pywin32-216.win32-py2.3.

I believe Outlook works fine, as it can load SpamBayes add-in generated by the exe installer. Or ???

What else can I try?

[Anonymous]

Also could I pls ask where the add-in (generated by Python script) is supposed to be? We can try and see if we can load it manually.

[Mark Hammond]

I'm not sure what you mean by the "add-in" is - the add-in is a Python COM object, which is loaded by pythoncomxx.dll - the registry entry for the COM object points to this DLL but also has additional metadata used when pythoncom is loaded so it knows the python script to load (addin.py in this case)

I no longer have access to Outlook, so I can't really offer much more debugging advice. However, you could see if something like cscript or vbscript are able to create the COM object "SpamBayes.OutlookAddin", and also check the other registry entries added at the end of addin.py have been created correctly.

[Anonymous]

The add-in here is SpamBayes add-in for Outlook. In Outlook, it has file name outlook_addin.dll. We would like to know where this file is generated when we run addin.py script.

[Mark Hammond]

That DLL is generated by the py2exe tool we use to make the binary package.

[Anonymous]

Yes, that’s right. We have no problems with SpamBayes binary.

But if we run SpamBayes from source codes, the script should generate similar DLL file for Outlook to load (as an add-in). We just want to know where the DLL file is located if it is generated successfully by script addin.py.

Alternatively if you could pls share the sourec code you used to generate the binary package, that would help. Thanks

[Mark Hammond]

But if we run SpamBayes from source codes, the script should generate similar DLL file for
Outlook to load (as an add-in).

No it shouldn't - running from source code registers the source-code version by registering pythoncomxx.dll as the implementation, as I explained above.

The binaries are generated by the spambayes/windows/py2exe/setup_all.py script, which relies on py2exe.

[Anonymous]

Thanks

I still believe that there may be bugs with the sources we downloaded from SpamBayes website. This time I tried something different. I didn’t use Outlook at all. I used the latest py2exe and tried to generate binary from the source for 1.1a6. It did create a folder ../dist/bin, but there is no files created in the ../dist/bin folder.Could you pls comment on this? :(

Thanks

[Mark Hammond]

You might want to find an older py2exe from around the time the spambayes binary was initially created. I use neither spambayes nor py2exe now, so I doubt I can help more.

[Erik Brown]

Did you ever get this to work? I'm also trying to run Spamayes from source to fix the broken "Show spam clues" button in the Outlook addin. Any help will be greatly appreciated and thank you!