Something similar happened to my server a year or two ago, but Mercury was not to blame. It turned out to be an OS / hardware issue. On Win2k3 server I scheduled a disk check and restarted the server. Several drive errors were detected and repaired and I had to restore the mailing list files from backup.

The MLF files cannot be read-only, as fields such as Last Submission Date and Status Flags need to be updated when messages go to list members.

 Be careful about changing file permissions, because Mercury EXPECTS to be able to write to certain files. Corruptions and other unstable behavior can result when it cannot do as it expects. (Hey, I am not saying that David doesn't have proper error traps in place, but he cannot be expected to anticipate every possible senario.)

Mercury seems to be corrupting the files that contain my mailing lists (*.mlf). This morning it wrote 62GB to what once was a 4kb list file. Some of my list files have had their contents removed and replaced with the body of an email. I have rebuilt the server and installed the newest version of Mercury. It seems that Mercury needs to write to these files when it sends mail to them. I found that out when setting the mlf files to read only and all mail from the lists halted.

Any ideas?<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />