> Thanks. First, I assume the hgh bits problem can be coded into an error rather than a crash. If so, can we add that to a list?  Second,
> is the address reported in the crash notice of any interest for narrowing down the cause?

Generally the problem is the high-bit stuff will generate a command since Mercury really does not care all that much what the data being sent looks like.  Of course in this case there is nothing Mercury can do when the data stream turns into a TCP/IP command.

I am getting periodic crashes of Mercury on my Windows XP. Mercury is the only application on this computer. They occur once or twice a week at seemingly random intervals. This began happening in the prior version and continues with the lasest version.

How can I figure out why?

> I am getting periodic crashes of Mercury on my Windows XP. Mercury is
> the only application on this computer. They occur once or twice a week
> at seemingly random intervals. This began happening in the prior version
> and continues with the lasest version. How can I figure out why?

Probable causes:

1.  Some program other than a program under the control of Mercury is accessing
    files when Mercury is trying to process them.  Most common is anti-virus software.
    Use Clamwall instead.

2.  You have a bad temp directory or the path is to a remote directory and it is
    failing.

3.  You are running Mercury from a LAN location and the LAN is flaky.

4.  You are receiving mail containing improperly encoded high-bit characters that
    crash the program.

Looks like from what you are saying it's item #1 or 4.

Thanks. First, I assume the hgh bits problem can be coded into an error rather than a crash. If so, can we add that to a list?  Second, is the address reported in the crash notice of any interest for narrowing down the cause?

There is usually not much chance to find the reason for a crash from the reported offending address, at least not without supplemental information about setup and from logs.

Two more things to check:

- If you use IMAP try testing folder integrity with the mbxmaint tool (it's included in the install in Mercury 4.73).

- If you use any daemons, make sure you have the latest versions.

/Rolf