I've reinstalled Windows XP and am reinstalling Pmail and Mercury as a stand alone system as I had before. Pmail and its assorted user mailboxes work fine and out-mail goes into C:\PMAIL\OUT as .101 files as I've seen before. Mercury downloads mail from several sources and splits it among the various maliboxes as before. However it completely ignores the .101 files in the aforementioned OUT directory. I can run the Core module and it shares out the incoming mail but doesn't process the outgoing. Is there something I've accidentally changed which makes the Core module look for a different file extension? My old computer runs Mercury 3.31 and I've compared the Mercury.ini files and can see nothing different. Pconfig looks the same as well. Here are some sections of the new .ini:
[General]
myname: lakedistrictwalks.com # Canonical name for this server
timezone: +0000 # Time Zone to add to date fields
file_api: 1 # Use the file api instead of queues
mailqueue: C:\PMAIL\OUT # Where mail should be put for delivery
smtpqueue: C:\PMAIL\OUT # Where the SMTP client should look for mail
newmail_path: C:\PMAIL\MAIL\~8 # Where to find the users' WinPMail mailboxes.
secondary_queue: C:\PMAIL\OUT
The mail doesn't seem to get as far as the SMTP client but here is:
[MercuryC]
# Session_logging: G:\ # Directory to write session transcripts
host: smtp.dsl.pipex.com # mail mail host which relays for us
scratch: C:\MERCURY\Mercury # Where we can write temp files
poll: 30 # Seconds between queue polling cycles
returnlines: 15 # How many lines of failed messages to return
failfile: C:\MERCURY\Mercury\FAILURE.MER # Delivery failure template
esmtp: 1 # Yes, we want to use ESMTP extensions
<p>I've reinstalled Windows XP and am reinstalling Pmail and Mercury as a stand alone system as I had before. Pmail and its assorted user mailboxes work fine and out-mail goes into C:\PMAIL\OUT as .101 files as I've seen before. Mercury downloads mail from several sources and splits it among the various maliboxes as before. However it completely ignores the .101 files in the aforementioned OUT directory. I can run the Core module and it shares out the incoming mail but doesn't process the outgoing. Is there something I've accidentally changed which makes the Core module look for a different file extension? My old computer runs Mercury 3.31 and I've compared the Mercury.ini files and can see nothing different. Pconfig looks the same as well. Here are some sections of the new .ini:</p><p>[General]
myname:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; lakedistrictwalks.com&nbsp;&nbsp;&nbsp; # Canonical name for this server
timezone:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +0000&nbsp;&nbsp;&nbsp; # Time Zone to add to date fields
file_api:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Use the file api instead of queues
mailqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\PMAIL\OUT&nbsp;&nbsp;&nbsp; # Where mail should be put for delivery
smtpqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\PMAIL\OUT&nbsp;&nbsp;&nbsp; # Where the SMTP client should look for mail
newmail_path:&nbsp;&nbsp;&nbsp; C:\PMAIL\MAIL\~8&nbsp;&nbsp;&nbsp; # Where to find the users' WinPMail mailboxes.
secondary_queue: C:\PMAIL\OUT</p><p>The mail doesn't seem to get as far as the SMTP client but here is:
</p><p>[MercuryC]
# Session_logging:&nbsp; G:\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # Directory to write session transcripts
host:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; smtp.dsl.pipex.com&nbsp;&nbsp;&nbsp;&nbsp; # mail mail host which relays for us
scratch:&nbsp;&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury&nbsp;&nbsp; # Where we can write temp files
poll:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # Seconds between queue polling cycles
returnlines: 15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # How many lines of failed messages to return
failfile:&nbsp;&nbsp;&nbsp; C:\MERCURY\Mercury\FAILURE.MER&nbsp; # Delivery failure template
esmtp:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # Yes, we want to use ESMTP extensions
&nbsp;</p>