> -----Original Message----- > From: Coe, Bob [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 12, 2007 10:34 AM > > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Coe, Bob > > Sent: Monday, June 11, 2007 4:49 PM > > To: [EMAIL PROTECTED] > >
> > At the time, I didn't think my problem was related to > > Spambayes, but conceivably it was. If I remember more about > > it (or, God forbid, it happens to me again), I'll post a message. > > > > Bob > > I now think I recall that the solution is to substitute a new "Outlook > profile"; indeed, there may even be a Microsoft paper dealing with the > issue. (N.B.: A user's Outlook profile is not the same as his Windows > roaming profile or any of the other profiles one commonly sees > mentioned. At least pre-Vista, "profile" is the most > overloaded word in > the Microsoft argot.) Creating a new Outlook profile (and persuading > Outlook to use it) is not exactly trivial, and a discussion > of how to do > it (even if I thought I could explain it adequately) is > beyond the scope > of this mailing list. But I'm almost certain that there *is* > a Microsoft > paper that describes how to do that. > > Assuming I'm remembering correctly, note that the solution is > independent of whether Spambayes had a role in creating the probem. > > Bob Profiles weren't a good choice for me. Either didn't work or trashes lots of stuff in the process. Microsoft suggested a way to do surgery to OutLook in the Registry by simply removing the "stuck" PST files from the collection. That was quick and clean, but an error might be dangerous. I found that SpamBayes is not the only way to corrupt these PST bindings, but it is an assured and conspicuous way to do so. Chuck _______________________________________________ [email protected] http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
