Hal  wrote on 02/06/2008 01:04:11 PM:

> Let's see, now: You realize that SA is not reporting the spam scores,
and
> you left out the content of the message. That doesn't give them much
data to
> work with.

Realistically, only the folks that run the server (LSoft) are likely to be
able to tell why SA triggered on this message.  Hopefully they can review
the logs and find the answer.  Sitting on the outside, none of us have any
idea why...

It may not have been a change at the sender's ISP, it could have been a
change in the SA rules applied, or there could have been something in the
message that triggered it.  Was there a URL list on one of the URIBLs?