On 6/01/2010 4:06 PM, Ocean wrote:
There are no log files. Keep in mind that I run from source - I
believe even the application points out that there won't be log files, but
needs the Trace Collector.
Perhaps you could try the most recent binary? It doesn't sound like you
need, or even want, to run from sources.
If you want a log of what happens when a new message comes in, I can
try to get that for you from the Trace Collector. However, if you want a
log of what's happening when Outlook starts up and fails to load SpamBayes
in the first place, you'll have to tell me how to get it - since the only
way I've been able to get info from the Trace Collector is to run it from
SpamBayes Manager once Outlook is already loaded.
I'm a little confused - if there are errors when a new message comes in,
doesn't that mean spambayes is already loaded?
I admit I haven't been following as closely as I could - I'm really just
after the complete copy of any relevant errors - your last email had
both partial errors, and seemed to include some references to the test
suite having been run. Anything you can do to achieve that goal (ie,
relevant errors in their entirety) would be good.
From your most recent message:
Just to clarify, I've tried running the Trace Collector through
Pythonwin as well as through win32traceutil.py, but nothing shows up when I
start Outlook. I only get data when I launch it through SpamBayes.
This sounds like an issue introduced with Vista. If you start a
cmd-prompt or pythonwin with admin permissions (ie, "run as
administrator") before starting outlook it should work OK. As mentioned
above though, unless you plan to hack on the sources, using a binary
build is probably best.
Cheers,
Mark
_______________________________________________
SpamBayes@python.org
http://mail.python.org/mailman/listinfo/spambayes
Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes
Check the FAQ before asking: http://spambayes.sf.net/faq.html
