I just started using eMailCRX with Outlook 2000. However, twice now, after downloading about dozen messages, eMailCRX appears to just hang. It is consuming between 92 and 98% of the processing cycles, but takes so long, finally kill it. (More than 15 minutes to rate a dozen messages seems excessive.)

Anyone else experiencing anything similar? What's up with it?

Can you please try running it with the log (Control, Generate Log)?

I suspect that this might be DNS related.

From a Command Prompt, can you run the utility NSLookup?
e.g.
c:>nslookup -type=ptr 72.4.161.210

Also, do you have access to port 53 (DNS), and port 43 (WhoIs)?

The contents of the log will tell you exactly what Em@ilCRX is trying to do when it starts looping.

I had this happen to me a lot when I first began using Em@ilCRX. I think at least one cause of the problem was not putting "80" in the HTTP port box in Settings. But I think you have taken care of this in newer versions, haven't you, Jeff?

CRX *does* often slow down, especially when I am changing SPAM to RELE or sometimes even when I am switching applications to bring it up. It also seems to like it's database being massaged regularly.

Good observation Paul! You definitely need to make sure that port 80 is defined as your HTTP port (or whatever port you are using for HTTP).

Yeah, I noticed the database slow down sometimes also. Running the database admin tasks, and restarting the app usually clears this up.

While developing CRX, I think that I should have paid more attention to "concurrent database access" issues. These have been addressed in Purify.