[spambayes-bugs] [ spambayes-Feature Requests-1122512 ] If registry
write fails, report to user
SourceForge.net
noreply at sourceforge.net
Wed Mar 16 03:05:07 CET 2005
Feature Requests item #1122512, was opened at 2005-02-15 06:02
Message generated for change (Comment added) made by anadelonbrin
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498106&aid=1122512&group_id=61702
>Category: Outlook
Group: None
Status: Open
Priority: 5
Submitted By: i_am_andy_k (i_am_andy_k)
>Assigned to: Tony Meyer (anadelonbrin)
>Summary: If registry write fails, report to user
Initial Comment:
I used SpamBayes for a few weeks at work on Win2000.
No problems - I even enabled spam column per
instructions. Great program.
I used version 1.0.3.exe, but I don't see that on the
Group pulldown.
Got a new PC at work - now have no write permissions
in Program Files (completely locked down). Maybe the
Registry is similarly locked down.
Here is the log file contents:
Traceback (most recent call last):
File "addin.py", line 1546, in ?
File "win32com\server\register.pyc", line 483, in
UseCommandLine
File "win32com\server\register.pyc", line 413, in
RegisterClasses
File "win32com\server\register.pyc", line 181, in
RegisterServer
File "win32com\server\register.pyc", line 32, in
_set_string
pywintypes.error: (5, 'RegSetValue', 'Access is denied.')
Any tips to work-around this issue appreciated !
I miss my SpamBayes filtering !
----------------------------------------------------------------------
>Comment By: Tony Meyer (anadelonbrin)
Date: 2005-03-16 15:05
Message:
Logged In: YES
user_id=552329
We should certainly report this as an error if we can, so
changing to a feature request.
If we don't remove this requirement (see other tracker) then
we should mention the requirement somewhere, too.
----------------------------------------------------------------------
Comment By: i_am_andy_k (i_am_andy_k)
Date: 2005-02-16 03:00
Message:
Logged In: YES
user_id=1219094
I suggest 2 changes:
1) change installer to not claim success if this happens
2) mention write permissions to registry as a requirement
Also - add 1.0.3 to SourceForge group list (but this registry
issue likely applies to all versions)
----------------------------------------------------------------------
Comment By: i_am_andy_k (i_am_andy_k)
Date: 2005-02-16 03:00
Message:
Logged In: YES
user_id=1219094
We haven't heard from the original reporter of the bug for some
time. Without the requested information, there really isn't much
we can do. If anyone does provide further information, please
also change the bug status back to "Open".
----------------------------------------------------------------------
Comment By: Tony Meyer (anadelonbrin)
Date: 2005-02-15 12:45
Message:
Logged In: YES
user_id=552329
It does look like you don't have access to the registry.
Unfortunately, there's no way to let Outlook know about the
plug-in without putting information in the registry, so
unless you can get permission to do that, nothing can be done.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=498106&aid=1122512&group_id=61702
More information about the Spambayes-bugs
mailing list