I'm not aware of any of the developers that have access to
that configuration.
Have you tried setting up SpamBayes in that environment? If
it didn't work, did you get any particular error messages?
Can you send the SpamBayes logs?
SpamBayes uses standard Outlook mechanisms to detect and
process new mail. Because of this, it works with all of the
standard access methods that Outlook supports (POP3, IMAP,
Exchange, Hotmail). If Oracle places new messages into an
Outlook folder, SpamBayes should be able to process them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could get rid of the problem with the spam field by
turning writing to that off. However, the invalid entry id
problem will probably still be there. If that's something
specifically related to Oracle, then I don't know whether
there's anything we can do about that (since, as Kenny said,
I don't believe any of us have access to that configuration).
OTOH, there are other people with invalid entry id problems,
so maybe there will be a common solution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=859086
I'm not aware of any of the developers that have access to
that configuration.
Have you tried setting up SpamBayes in that environment? If
it didn't work, did you get any particular error messages?
Can you send the SpamBayes logs?
SpamBayes uses standard Outlook mechanisms to detect and
process new mail. Because of this, it works with all of the
standard access methods that Outlook supports (POP3, IMAP,
Exchange, Hotmail). If Oracle places new messages into an
Outlook folder, SpamBayes should be able to process them.
SPamBaayes log file
Logged In: YES
user_id=1203728
Sorry for the delay... I've had to rely on an IT guy to get
the log files created.
Thanks!
Patrick
Logged In: YES
user_id=552329
You could get rid of the problem with the spam field by
turning writing to that off. However, the invalid entry id
problem will probably still be there. If that's something
specifically related to Oracle, then I don't know whether
there's anything we can do about that (since, as Kenny said,
I don't believe any of us have access to that configuration).
OTOH, there are other people with invalid entry id problems,
so maybe there will be a common solution.