Hi Jeff,

I've just noticed that my reporting has failed for the past 2 or 3 days. Happens to correspond with Apple's update from 10.6.1 to 10.6.2, so wondering whether you might need to shoot out a new release to fix something .. ??

Whilst I don't understand this stuff, I imagine it is conceivable that there's a problem somewhere. A couple of Mail.app bundles I use have had to be updated to work with 10.6.2. So maybe ...

Oy Lance. If you run reporting with logging on, it will tell you exactly what it doesn't like about your reporting setup. If it's something interesting, please let me know.

Log spits out line after line:

Also Purify gives me a popup error message on the screen a few seconds after attempting to report:

This reads like one of your database files has been deleted, or your DNS port is blocked?
This was working before? Filtering still working? This error only shows up only when reporting?

Looks like it was all a case of one message timing out and blocking all the following messages being reported. I've forwarded said message to you for a look ...

Jeff,

Thanks for your reply to my direct e-mail:


That may be right. But the bigger issue is that with that message at the top of the reporting list I wasn't able to report any of the following items either (until I deleted that one). So my question now is whether that constitutes a bug in Purify - it should surely be possible for Purify to skip the message it can't understand and go on to report those that follow.

Yeah, I think so. Do you have the message in question? If so, would it be possible to forward it as a .zipped attachment?