> Hi Clive, >
> you have to implement a tri-state logic, so you can
> differentiate between ham, spam and a message that wasn't
> scanned due to SA outages.
>
> You can achieve this with something like this:
>
[snip]
Patrick,
that's exactly what we needed and seems to work fine.
> About the behaviour you see: Ask yourself, what happens in
> this timeframe, when connections to SA timeout. Probably SA
> is busy, as I don't expect that you get more spam in this
> timeframe than in any other.
> For example, are you training your bayes database in this timeframe?
> Questions like this one should put you on the right track.
We've checked all those things but there's nothing obvious to suggest why this is happening. Anyway, the state checking above
should minimise the effects.
Thanks,
Clive McDowell
Information Services
The Queen's University of Belfast
