Community Discussions and Support
Mercury 4.5 Ignores .101 files in PMAIL\OUT Directory

You are right. I'd inadvertently changed to no formatting. Don't know how. Thanks for your help.

 Regards

 
John D.


 

<p>You are right. I'd inadvertently changed to no formatting. Don't know how. Thanks for your help.</p><p> Regards</p><p>  John D.</p><p>  </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:

[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:          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</p><p>The mail doesn't seem to get as far as the SMTP client but here is: </p><p>[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>

Check out those *.101 files. I suspect they are not in the proper"Glue headers" format.  If they are not use pconfig.exe from the program directory to midify the MERCURY UDG.

Check out those *.101 files. I suspect they are not in the proper"Glue headers" format.  If they are not use pconfig.exe from the program directory to midify the MERCURY UDG.
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft