[spambayes-bugs] [ spambayes-Bugs-961019 ] Outlook2K3 spews warnings as it fails to create spam field

[SourceForge.net]

Bugs item #961019, was opened at 2004-05-27 04:28
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=961019&group_id=61702

Category: Outlook
Group: Binary 1.0rc1
Status: Open
Resolution: None
>Priority: 4
Submitted By: Andy Neil (andyneil)
Assigned to: Mark Hammond (mhammond)
>Summary: Outlook2K3 spews warnings as it fails to create spam field

Initial Comment:
New Inbox messages get a spam rating of 100% but are 
not moved to "__Spam" folder as expected

Key symptom from log (attached) seems to be "Eeek - 
only expecting one row from IPC.MS.REN.USERFIELDS"
and then "WARNING: We just created the user field in 
folder Mailbox - Andy Neil/IPM_SUBTREE/Inbox, but it 
appears to not exist.  Something is probably wrong with 
DoesFolderHaveOutlookField()"

Config details:
WinXPSP1, user account has local administrator 
privileges.
Outlook 2003 (11.5608.5703) (with full Office 2003 Pro 
install).
NewsGator 2.0.
All Outlook rules have been turned off.
Outlook "Junk E-mail Filtering" set to "No automatic 
filtering".

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2004-06-29 11:30

Message:
Logged In: YES 
user_id=14198

That error is is very interesting, but I don't believe it is
related to spam not being moved.  That error relates to our
attempt at determining if the 'Spam' field exists in the
folder, but should not affect the normal filtering.  You
will see this message once each time SpamBayes starts, and
each time the config dialog is closed.

Your log indicates everything is going normally.  Can you
please go to the SB manager, Advanced->Diagnostics, and set
the log level to "2".  Then restart spambayes, and wait for
the next spam correctly classified, but not moved.  Could
you then please create a *new* bug for that specific issue,
and attach the log.  I want to take over this bug for that
error message you see - but as I mentioned, I'm not
convinced they are related.  I'm lowering the priority on
this, as I also don't believe it will affect normal operation.

Thanks!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=498103&aid=961019&group_id=61702