<p>.QCL files are no longer used in Mercury/32 v4.5; once you have upgraded to v4.5, you can delete any of these files that might have been left lying around by older versions of the program. .QJD files are <i>Job-wide Diagnostic</i> files - they are created to contain diagnostic or error report information applying to the job as a whole, as opposed to information specific to a particular address element in the job. Unlike .QIF files, which will almost always have a filename part different from the job they belong to, .QJD files will always have the same base filename part as the .QCF and .QDF files. Peter's comment about deleting files needs some amplification: you must <b>always</b> shut down Mercury before attempting to delete any files in the queue directory - but in fact you should avoid doing this altogether unless you are very sure of what you are doing. The Mercury queue was never intended to be manually manipulated, and if you get it wrong, the consequences can be quite unappealing. -- David -- </p>

<TABLE class=inlinetable border=1 frame=border class="inlinetable"> <TBODY> <TR> <TD class="">.101</TD> <TD class="">Outgoing SMTP message files created by Pegasus Mail. Mercury processes these and converts each one into a .QCF control file and .QDF data file.</TD></TR> <TR> <TD class="">.QCF</TD> <TD class="">Control file for a mail message job (contains status information, sender, and recipient information, as well as the filename of the corresponding .QDF data file and any .QIF error files).</TD></TR> <TR> <TD class="">.QDF</TD> <TD class="">Data file for a mail message job (contains the actual RFC822 SMTP e-mail message). There should normally be a matching .QCF and .QDF file for every e-mail message, although it is possible that the .QCF and .QDF filenames may be different (which isn't a problem since the corresponding .QDF file's filename is referenced in the .QCF file).</TD></TR> <TR> <TD class="">.QCL</TD> <TD class="">Mercury lock file so that Mercury knows when another thread/module within Mercury is already processing this file so that it doesn't get processed multiple times by different threads/modules. This file contains the filename of the corresponding .QCF file that is being processed and will normally have the same filename as the corresponding .QCF file.</TD></TR> <TR> <TD class="">.QIF</TD> <TD class="">Mercury error message file. For each recipient listed in a .QCL file, a .QIF error file may be generated if there are problems delivering the message (whether a local recipient or remote/external address).</TD></TR> <TR> <TD class="">.QJD</TD> <TD class="">These files are currently undocumented. Occassionally, Mercury will generate these files due to weird unexpected job errors when communicating with a remote host (e.g. "Out of Memory" errors, etc.).</TD></TR></TBODY></TABLE> <P>Before deleting files, it is best to shut down Mercury/32 first. Delete any orphaned .QCF and .QDF files that do not contain their corresponding partner file (view the .QCF file in order to determine the corresponding .QDF file's filename--it may not always be the same filename as the .QCF file, but this case is highly unusual). Delete any .QIF files that are not referenced in any of the .QCF files. The .QJD files can usually be deleted outright. Delete all .QCL lock files outright. Restart Mercury/32.</P> <P>Occassionally, there may be some corruption of the .QCL control files. Usually this is manifested by either the FR: line being appended to the end of the ST: line at the top of the file or parts of the beginning of an RI: line being cropped off. (e.g. "I:", ":", or no tagged header at all). You can manually fix these using Windows WordPad or Notepad while Mercury is shut down and then restart Mercury afterwards.</P>