Community Discussions and Support
Messages stuck in a "pending" state

Just clear Queue and Scratch directories before starting Mercury again. And make sure the file mercury.ini isn't damaged. If it appears to be damaged you can make a copy of mercury.bak and rename it to mercury.ini.

There is usually no need to reinstall Mercury unless you have had some bad kind of disk crash. If so you can download the Mercury installer and update Mercury without touching other parts of XAMPP.

/Rolf

<p>Just clear Queue and Scratch directories before starting Mercury again. And make sure the file mercury.ini isn't damaged. If it appears to be damaged you can make a copy of mercury.bak and rename it to mercury.ini.</p><p>There is usually no need to reinstall Mercury unless you have had some bad kind of disk crash. If so you can download the Mercury installer and update Mercury without touching other parts of XAMPP. </p><p>/Rolf </p>

I downloaded Mercury (v4.62) as a part of the XAMPP with LimeSurvey and am trying to use it to programmatically send e-mails via SMTP.

For some reason every e-mail that I try to send gets stuck in a "pending" state in Mercury - according to the "Mercury Core Process" log that I am seeing.

I am not getting any indication as to WHY this is the case, however so I don't know how to go about fixing the problem.

Any suggestions would be much appreciated.

Thanks,

Alex

<P>I downloaded Mercury (v4.62) as a part of the XAMPP with LimeSurvey and am trying to use it to programmatically send e-mails via SMTP.</P> <P>For some reason every e-mail that I try to send gets stuck in a "pending" state in Mercury - according to the "Mercury Core Process" log that I am seeing.</P> <P>I am not getting any indication as to WHY this is the case, however so I don't know how to go about fixing the problem.</P> <P>Any suggestions would be much appreciated.</P> <P>Thanks,</P> <P>Alex</P>

How are you trying to sending them - MercuryC or MercuryE?  It sounds as if that's not configured properly.

If you can't sort it, post your Mercury.ini file and/or the output session log.

<P>How are you trying to sending them - MercuryC or MercuryE?  It sounds as if that's not configured properly.</P> <P>If you can't sort it, post your Mercury.ini file and/or the output session log.</P>

I am unaware of MercuryC or MercuryE?

I am trying to send them via LimeSurvey. It is an open source PHP based app that runs on XAMPP.

They have a config-defaults.php file that we edit to direct us towards a particular SMTP server.

We figured that since we're already running on top of XAMPP why not use the SMTP server in XAMPP ... i.e. Mercury.

No configuration was done at all that I am aware of.

 I don't know which "output session log" is appropriate.

Here is the "Mercury Core Process" window's log ... 

Mercury Mail Transport System v4.62,
Copyright (c) 1993-2008, David Harris, All Rights Reserved
Web: http://www.pmail.com, E-mail: support@pmail.gen.nz

Thu 06, 16:26:42: Mercury MTS Core processing thread running.

Thu 06, 16:30:45: Job MG000003: from alexander.ryan@unisys.com (non-local)
   Created outgoing job with ID MO000004
   To: alexander.ryan@unisys.com (non-local) -OK
Thu 06, 16:31:40: Job MG000006: from alexander.ryan@unisys.com (non-local)
   Created outgoing job with ID MO000007
   To: alexander.j.ryan@gmail.com (non-local) -OK
Thu 06, 17:10:54: Job MG000009: from alexander.ryan@unisys.com (non-local)
   Created outgoing job with ID MO00000A
   To: alexander.ryan@unisys.com (non-local) -OK
Fri 07, 8:25:39: Job MO000021: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:39: Job MO000022: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:39: Job MO000023: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MG00000C: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:25:50: Job MG00000D: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:25:50: Job MG00000B: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:25:50: Job MO000024: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000025: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000026: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000027: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000028: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000029: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00002A: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00002B: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00002C: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00002D: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00002E: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00002F: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000030: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000031: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000032: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000033: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000034: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000035: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000036: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000037: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000038: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000039: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00003A: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00003B: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00003C: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00003D: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO00003E: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:25:50: Job MO000040: Processing failed deliveries and generating notifications
   postmaster@localhost - Notification discarded - potential loop.
Fri 07, 8:26:01: Job MG000026: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000027: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000028: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000029: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000025: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000024: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000023: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000021: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG00001F: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000020: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:01: Job MG000022: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG00001E: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG00001B: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG00001A: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG00001C: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG00001D: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000019: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000016: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000017: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000018: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000015: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000014: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000011: from postmaster@localhost (local)
   To: Admin (local) -OK
Fri 07, 8:26:02: Job MG000010: from postmaster@localhost (local)

<P>I am unaware of MercuryC or MercuryE?</P> <P>I am trying to send them via LimeSurvey. It is an open source PHP based app that runs on XAMPP.</P> <P>They have a config-defaults.php file that we edit to direct us towards a particular SMTP server.</P> <P>We figured that since we're already running on top of XAMPP why not use the SMTP server in XAMPP ... i.e. Mercury.</P> <P>No configuration was done at all that I am aware of.</P> <P> I don't know which "output session log" is appropriate.</P> <P>Here is the "Mercury Core Process" window's log ... </P> <P>Mercury Mail Transport System v4.62, Copyright (c) 1993-2008, David Harris, All Rights Reserved Web: <A href="http://www.pmail.com/">http://www.pmail.com</A>, E-mail: <A href="mailto:support@pmail.gen.nz">support@pmail.gen.nz</A></P> <P>Thu 06, 16:26:42: Mercury MTS Core processing thread running.</P> <P>Thu 06, 16:30:45: Job MG000003: from <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local)    Created outgoing job with ID MO000004    To: <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local) -OK Thu 06, 16:31:40: Job MG000006: from <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local)    Created outgoing job with ID MO000007    To: <A href="mailto:alexander.j.ryan@gmail.com">alexander.j.ryan@gmail.com</A> (non-local) -OK Thu 06, 17:10:54: Job MG000009: from <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local)    Created outgoing job with ID MO00000A    To: <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local) -OK Fri 07, 8:25:39: Job MO000021: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:39: Job MO000022: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:39: Job MO000023: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MG00000C: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:25:50: Job MG00000D: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:25:50: Job MG00000B: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:25:50: Job MO000024: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000025: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000026: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000027: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000028: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000029: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00002A: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00002B: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00002C: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00002D: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00002E: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00002F: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000030: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000031: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000032: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000033: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000034: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000035: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000036: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000037: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000038: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000039: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00003A: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00003B: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00003C: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00003D: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO00003E: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:25:50: Job MO000040: Processing failed deliveries and generating notifications    <A href="mailto:postmaster@localhost">postmaster@localhost</A> - Notification discarded - potential loop. Fri 07, 8:26:01: Job MG000026: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000027: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000028: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000029: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000025: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000024: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000023: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000021: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG00001F: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000020: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:01: Job MG000022: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG00001E: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG00001B: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG00001A: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG00001C: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG00001D: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000019: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000016: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000017: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000018: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000015: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000014: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000011: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local)    To: Admin (local) -OK Fri 07, 8:26:02: Job MG000010: from <A href="mailto:postmaster@localhost">postmaster@localhost</A> (local) </P>

The Mercury.ini has not been altered.

Here is how the one distributed with XAMPP looks:

#  MERCURY.INI generated by Mercury Setup
#
#
#  Sample Bindery Mode MERCURY.INI file (in fact, the one I use on
#  my production server). This one implements most of the possible
#  switches for each module, but you can edit it to do less if you
#  wish. All the fields shown below are described in the file
#  MGUIDE.HLP which is supplied in the Mercury archive.
#
#  Anything after a '#' to the end of the line is a comment and
#  is stripped out before parsing. Trailing and leading whitespace
#  is also stripped before parsing. Many sample commands have been
#  left in this file commented out for reference purposes.
#

[General]
myname:          localhost    # 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:\XAMPP\MERCURYMAIL\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\XAMPP\MERCURYMAIL\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\XAMPP\MERCURYMAIL\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
C:\xampp\MERCURYMAIL\mercurys.dll
C:\xampp\MERCURYMAIL\mercurye.dll
C:\xampp\MERCURYMAIL\mercuryp.dll
C:\xampp\MERCURYMAIL\mercuryd.dll
C:\xampp\MERCURYMAIL\mercuryx.dll
C:\xampp\MERCURYMAIL\mercuryf.dll
C:\xampp\MERCURYMAIL\mercuryh.dll
C:\xampp\MERCURYMAIL\mercuryw.dll
C:\xampp\MERCURYMAIL\mercuryi.dll
C:\xampp\MERCURYMAIL\mercuryb.dll


[Mercury]
failfile:      C:\xampp\MERCURYMAIL\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   C:\xampp\MERCURYMAIL\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     C:\xampp\MERCURYMAIL\Mercury\ALIAS.MER    # System-wide alias file
synfile:       C:\xampp\MERCURYMAIL\Mercury\SYNONYM.MER    # User synonym database
listfile:      C:\xampp\MERCURYMAIL\Mercury\LISTS.MER    # List of lists
logwidth:      30    # Width of address fields in logfile
retpath:       1    # Do/Don't use 'return-path' for errors
maxhops:       30    # Used to detect mailing loops
gullible:      0    # If NZ, don't validate 'From' fields
bitnethost:    cunyvm.cuny.edu    # Relay host for '.bitnet' rewrites
poll:          10   # Seconds between queue polling cycles
scratch:       C:\xampp\MERCURYMAIL\Scratch    # Where we can write temp files
returnlines:   15    # How many lines of failed messages to return
postmaster:    Admin    # NetWare UIC of postmaster
broadcast:     1    # Yes, we want broadcast notifications, but
receipts:      0    # ... no broadcasts for receipt confirmations
PM_notify:     1    # Do/Don't send errors to the postmaster
change_owner:  1    # Change message ownership to recipient
auto_tzone:    1    # If NZ, obtain timezone information from OS
LogLevel:      15    # System message reporting level
LogMax:        100    # Maximum number of system messages to store
RetryPeriod:   30    # Period between job retries (minutes)
MaxRetries:    16    # Maximum number of times a job can fail
TwoPasses:     1    # If NZ, process submission queue in 2 passes
Autoaddress:   0    # If NZ, auto-generate user addresses based on name
Daily_exit:    0    # If NZ, auto-restart each day after maintenance
No_Areply:     0    # If NZ, disable automatic replies system-wide
Alt_Forward:   0    # If NZ, allow alternate forwarding specification
Maint_hour:    2    # Hour for daily maintenance (24-hour clock)
Maint_min:     0    # Minute for daily maintenance
Retry_Mode:    0    # If NZ, use progressive backoff for queue retries
Local_DSNs:    1    # If NZ generate Delivery Status for local users only
DSN_time1:     10800    # Seconds deferred before first DSN is sent
DSN_time2:     86400    # Seconds deferred before second DSN is sent
DSN_time3:     259200    # Seconds deferred before third DSN is sent
Host_in_title: 0    # If NZ, show hostname in system tray and taskbar
Lingering:     0    # Enable or disable 'lingering mailboxes'
Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down
Alert_Host:    notify.pmail.com    # Host to check for licensee advisories
Alert_Interval: 720   # Frequency in minutes (min 240) for checks
Alert_Flags:   3    # Flags controlling advisory checks

[MercuryC]
# Session_logging:  G:\           # Directory to write session transcripts
host:             # mail mail host which relays for us
scratch:     C:\xampp\MERCURYMAIL\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:\xampp\MERCURYMAIL\Mercury\FAILURE.MER  # Delivery failure template
esmtp:       1                    # Yes, we want to use ESMTP extensions

[MercuryE]
Poll : 15
Timeout : 60
# Session_logging : o:\mail\mercury\melogs
# Session_logmode : 1
# Nameservers : 139.80.64.1

[MercuryD]
scratch              :     C:\xampp\MERCURYMAIL\Mercury
# Timeout : 30
# Poll : 120               # How often to check hosts for new mail (seconds)

[MercuryS]
Debug : 1
Logfile : C:\xampp\MERCURYMAIL\Logs\MERCURYS.LOG
Timeout : 30
Relay : 1
Strict_Relay : 0
Allow_Illegals : 0
SMTP_Authentication : 0
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 288
No_VRFY : 0
SMTP_ConnFlags : 0

[MercuryP]
Scratch : C:\xampp\MERCURYMAIL\Mercury
Stack : 32768
Mark_Read : 1
SSL_Mode : 0
Login_Disabled : 0
Timeout : 60

[MercuryX]
# Cmd_Delay: 10
# Cmd_Wait: 1
# IE4_Dialling: 0
# Use_ETRN: 1
# Clients_only: 1
# Sunday: 0800,1800,3,15,30,60
# Monday: 0830,2100,5,15,60,60
# Tuesday: 0830,2100,5,15,60,60
# Wednesday: 1500,1900,2,30,5,30
# Thursday: 0900,1900,2,30,0,0
# Friday: 0830,2100,5,15,60,60
# Saturday: 1031,1035,2,45,-1,0

# [Groups]
# testgroup            :     TESTGRP

[Domains]
localhost: localhost
localhost: localhost.net
localhost: localhost.org
localhost: localhost.com

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        C:\xampp\MERCURYMAIL\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\xampp\MERCURYMAIL\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\xampp\MERCURYMAIL\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         C:\xampp\MERCURYMAIL\Logs\MAISER.LOG   # Mail server log file
Notify:          C:\xampp\MERCURYMAIL\Mercury\TMP   # Dir. for pending 'notify' commands
NoList:          N   # If 'Y', disable the 'list' command
Local_only:      Y   # If 'Y', local 'notify' commands only

[MercuryH]
Logfile              :     C:\xampp\MERCURYMAIL\Logs\MERCURYH.LOG
# Addressbook : \\CLIO\SYS\SYSTEM\MERCURY\PH.PMR
# MOTD : \\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT
# Administrator : postmaster@clio.pmail.gen.nz
Timeout : 30

[MercuryI]
Scratch : C:\xampp\MERCURYMAIL\SCRATCH
Timeout : 120
Server_Port : 143
Idle_Timeout : 1800
SSL_Mode : 0
Login_Disabled : 0

[MercuryB]
Scratch : C:\xampp\MERCURYMAIL\SCRATCH
# Logfile : o:\mail\tmp\mercuryb.log
Timeout : 120
Server_Port : 2224
# Session_logging : o:\mail\mercury\mblogs
# Session_logmode : 0
Idle_Timeout : 1800
# URL_Base : enter_your_domain_here
[Groups]

[Rewrite]

[Statistics]
StatFlags:    0  # Statistical reporting settings
STF_Hours:    24  # How often to write stat log files
STM_Hours:    24  # How often to e-mail stat log files

 

<P>The Mercury.ini has not been altered.</P> <P>Here is how the one distributed with XAMPP looks:</P> <P>#  MERCURY.INI generated by Mercury Setup # # #  Sample Bindery Mode MERCURY.INI file (in fact, the one I use on #  my production server). This one implements most of the possible #  switches for each module, but you can edit it to do less if you #  wish. All the fields shown below are described in the file #  MGUIDE.HLP which is supplied in the Mercury archive. # #  Anything after a '#' to the end of the line is a comment and #  is stripped out before parsing. Trailing and leading whitespace #  is also stripped before parsing. Many sample commands have been #  left in this file commented out for reference purposes. #</P> <P>[General] myname:          localhost    # 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:\XAMPP\MERCURYMAIL\QUEUE    # Where mail should be put for delivery smtpqueue:       C:\XAMPP\MERCURYMAIL\QUEUE    # Where the SMTP client should look for mail newmail_path:    C:\XAMPP\MERCURYMAIL\MAIL\~N    # Where to find the users' WinPMail mailboxes.</P> <P>[Protocols] C:\xampp\MERCURYMAIL\mercurys.dll C:\xampp\MERCURYMAIL\mercurye.dll C:\xampp\MERCURYMAIL\mercuryp.dll C:\xampp\MERCURYMAIL\mercuryd.dll C:\xampp\MERCURYMAIL\mercuryx.dll C:\xampp\MERCURYMAIL\mercuryf.dll C:\xampp\MERCURYMAIL\mercuryh.dll C:\xampp\MERCURYMAIL\mercuryw.dll C:\xampp\MERCURYMAIL\mercuryi.dll C:\xampp\MERCURYMAIL\mercuryb.dll</P> <P> [Mercury] failfile:      C:\xampp\MERCURYMAIL\Mercury\FAILURE.MER    # Delivery failure notification template confirmfile:   C:\xampp\MERCURYMAIL\Mercury\CONFIRM.MER    # Delivery confirmation template aliasfile:     C:\xampp\MERCURYMAIL\Mercury\ALIAS.MER    # System-wide alias file synfile:       C:\xampp\MERCURYMAIL\Mercury\SYNONYM.MER    # User synonym database listfile:      C:\xampp\MERCURYMAIL\Mercury\LISTS.MER    # List of lists logwidth:      30    # Width of address fields in logfile retpath:       1    # Do/Don't use 'return-path' for errors maxhops:       30    # Used to detect mailing loops gullible:      0    # If NZ, don't validate 'From' fields bitnethost:    cunyvm.cuny.edu    # Relay host for '.bitnet' rewrites poll:          10   # Seconds between queue polling cycles scratch:       C:\xampp\MERCURYMAIL\Scratch    # Where we can write temp files returnlines:   15    # How many lines of failed messages to return postmaster:    Admin    # NetWare UIC of postmaster broadcast:     1    # Yes, we want broadcast notifications, but receipts:      0    # ... no broadcasts for receipt confirmations PM_notify:     1    # Do/Don't send errors to the postmaster change_owner:  1    # Change message ownership to recipient auto_tzone:    1    # If NZ, obtain timezone information from OS LogLevel:      15    # System message reporting level LogMax:        100    # Maximum number of system messages to store RetryPeriod:   30    # Period between job retries (minutes) MaxRetries:    16    # Maximum number of times a job can fail TwoPasses:     1    # If NZ, process submission queue in 2 passes Autoaddress:   0    # If NZ, auto-generate user addresses based on name Daily_exit:    0    # If NZ, auto-restart each day after maintenance No_Areply:     0    # If NZ, disable automatic replies system-wide Alt_Forward:   0    # If NZ, allow alternate forwarding specification Maint_hour:    2    # Hour for daily maintenance (24-hour clock) Maint_min:     0    # Minute for daily maintenance Retry_Mode:    0    # If NZ, use progressive backoff for queue retries Local_DSNs:    1    # If NZ generate Delivery Status for local users only DSN_time1:     10800    # Seconds deferred before first DSN is sent DSN_time2:     86400    # Seconds deferred before second DSN is sent DSN_time3:     259200    # Seconds deferred before third DSN is sent Host_in_title: 0    # If NZ, show hostname in system tray and taskbar Lingering:     0    # Enable or disable 'lingering mailboxes' Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down Alert_Host:    notify.pmail.com    # Host to check for licensee advisories Alert_Interval: 720   # Frequency in minutes (min 240) for checks Alert_Flags:   3    # Flags controlling advisory checks</P> <P>[MercuryC] # Session_logging:  G:\           # Directory to write session transcripts host:             # mail mail host which relays for us scratch:     C:\xampp\MERCURYMAIL\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:\xampp\MERCURYMAIL\Mercury\FAILURE.MER  # Delivery failure template esmtp:       1                    # Yes, we want to use ESMTP extensions</P> <P>[MercuryE] Poll : 15 Timeout : 60 # Session_logging : o:\mail\mercury\melogs # Session_logmode : 1 # Nameservers : 139.80.64.1</P> <P>[MercuryD] scratch              :     C:\xampp\MERCURYMAIL\Mercury # Timeout : 30 # Poll : 120               # How often to check hosts for new mail (seconds)</P> <P>[MercuryS] Debug : 1 Logfile : C:\xampp\MERCURYMAIL\Logs\MERCURYS.LOG Timeout : 30 Relay : 1 Strict_Relay : 0 Allow_Illegals : 0 SMTP_Authentication : 0 Compliance_Settings : 0 Maximum_Failed_Rcpts : 4 Max_Relay_Attempts : 4 SSL_Mode : 0 ST_Blacklisting : 288 No_VRFY : 0 SMTP_ConnFlags : 0</P> <P>[MercuryP] Scratch : C:\xampp\MERCURYMAIL\Mercury Stack : 32768 Mark_Read : 1 SSL_Mode : 0 Login_Disabled : 0 Timeout : 60</P> <P>[MercuryX] # Cmd_Delay: 10 # Cmd_Wait: 1 # IE4_Dialling: 0 # Use_ETRN: 1 # Clients_only: 1 # Sunday: 0800,1800,3,15,30,60 # Monday: 0830,2100,5,15,60,60 # Tuesday: 0830,2100,5,15,60,60 # Wednesday: 1500,1900,2,30,5,30 # Thursday: 0900,1900,2,30,0,0 # Friday: 0830,2100,5,15,60,60 # Saturday: 1031,1035,2,45,-1,0</P> <P># [Groups] # testgroup            :     TESTGRP</P> <P>[Domains] localhost: localhost localhost: localhost.net localhost: localhost.org localhost: localhost.com</P> <P>[Maiser] Maiser:          Maiser   # 'Username' of mail server account Helpfile:        C:\xampp\MERCURYMAIL\Mercury\MAISER.HLP   # Help sent on failed maiser requests Lookupfile:      C:\xampp\MERCURYMAIL\Mercury\MAISER.LKP   # Format file for the 'lookup' command Send_dir:        C:\xampp\MERCURYMAIL\Mercury\SENDABLE   # Directory for the 'send' command Logfile:         C:\xampp\MERCURYMAIL\Logs\MAISER.LOG   # Mail server log file Notify:          C:\xampp\MERCURYMAIL\Mercury\TMP   # Dir. for pending 'notify' commands NoList:          N   # If 'Y', disable the 'list' command Local_only:      Y   # If 'Y', local 'notify' commands only</P> <P>[MercuryH] Logfile              :     C:\xampp\MERCURYMAIL\Logs\MERCURYH.LOG # Addressbook : <A href="file://clio/SYS/SYSTEM/MERCURY/PH.PMR">\\CLIO\SYS\SYSTEM\MERCURY\PH.PMR</A> # MOTD : <A href="file://clio/SYS/SYSTEM/MERCURY/PH-MOTD.TXT">\\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT</A> # Administrator : <A href="mailto:postmaster@clio.pmail.gen.nz">postmaster@clio.pmail.gen.nz</A> Timeout : 30</P> <P>[MercuryI] Scratch : C:\xampp\MERCURYMAIL\SCRATCH Timeout : 120 Server_Port : 143 Idle_Timeout : 1800 SSL_Mode : 0 Login_Disabled : 0</P> <P>[MercuryB] Scratch : C:\xampp\MERCURYMAIL\SCRATCH # Logfile : o:\mail\tmp\mercuryb.log Timeout : 120 Server_Port : 2224 # Session_logging : o:\mail\mercury\mblogs # Session_logmode : 0 Idle_Timeout : 1800 # URL_Base : enter_your_domain_here [Groups]</P> <P>[Rewrite]</P> <P>[Statistics] StatFlags:    0  # Statistical reporting settings STF_Hours:    24  # How often to write stat log files STM_Hours:    24  # How often to e-mail stat log files</P> <P mce_keep="true"> </P>

[General]
myname:          localhost    # Canonical name for this server

[Protocols]
C:\xampp\MERCURYMAIL\mercurys.dll
C:\xampp\MERCURYMAIL\mercurye.dll
C:\xampp\MERCURYMAIL\mercuryp.dll
C:\xampp\MERCURYMAIL\mercuryd.dll
C:\xampp\MERCURYMAIL\mercuryx.dll
C:\xampp\MERCURYMAIL\mercuryf.dll
C:\xampp\MERCURYMAIL\mercuryh.dll
C:\xampp\MERCURYMAIL\mercuryw.dll
C:\xampp\MERCURYMAIL\mercuryi.dll
C:\xampp\MERCURYMAIL\mercuryb.dll

You are sending using MercuryE and you are using a host name of "localhost".  You probably also have a dynamic IP address.  This will be bounced as spam by most mail servers nowadays. To verify this use MercuryE session logging.

You need to go to Configuration | Protocols and convert to MercuryC and send through your ISPs mail server as the relay host.  If you really do have a fixed IP address then you need to use the real host name in the Mercury/32 for the name of the system and the domains section.  In addition, use the IP address of the name servers(s) in the MercuryE setup.

 

 

<blockquote><p>[General] myname:          localhost    # Canonical name for this server </p><p>[Protocols] C:\xampp\MERCURYMAIL\mercurys.dll C:\xampp\MERCURYMAIL\mercurye.dll C:\xampp\MERCURYMAIL\mercuryp.dll C:\xampp\MERCURYMAIL\mercuryd.dll C:\xampp\MERCURYMAIL\mercuryx.dll C:\xampp\MERCURYMAIL\mercuryf.dll C:\xampp\MERCURYMAIL\mercuryh.dll C:\xampp\MERCURYMAIL\mercuryw.dll C:\xampp\MERCURYMAIL\mercuryi.dll C:\xampp\MERCURYMAIL\mercuryb.dll</p></blockquote><p>You are sending using MercuryE and you are using a host name of "localhost".  You probably also have a dynamic IP address.  This will be bounced as spam by most mail servers nowadays. To verify this use MercuryE session logging. </p><p>You need to go to Configuration | Protocols and convert to MercuryC and send through your ISPs mail server as the relay host.  If you really do have a fixed IP address then you need to use the real host name in the Mercury/32 for the name of the system and the domains section.  In addition, use the IP address of the name servers(s) in the MercuryE setup. </p><p> </p><p> </p>

Thank you Thomas. 

I switched to Mercury C as you suggested.

I also tried sending through my company's Microsoft exchange server by replacing the localhost entry in the MERCURY.INI file thusly ...

[General]
myname:          USEA-EXCH7.na.uis.unisys.com    # Canonical name for this server

However, the result was the same.

I now just have more messages in a "pending" state.

i.e. The "Mercury Core Process" windows says "Queue Status / Outgoing Jobs / Pending = 7" 

Fri 07, 14:54:23: Job MG00003A: from alexander.ryan@unisys.com (non-local)
   Created outgoing job with ID MO00003B
   To: alexander.ryan@unisys.com (non-local) -OK
Fri 07, 14:54:34: Job MG00003D: from alexander.ryan@unisys.com (non-local)
   Created outgoing job with ID MO00003E
   To: alexander.j.ryan@gmail.com (non-local) -OK
 

Dumb question:

Does "pending" mean that Mercury has not sent them yet?

If so, it wouldn't matter if other mail servers would treat them as spam or not right?

 

 

<P>Thank you Thomas. </P> <P>I switched to Mercury C as you suggested.</P> <P>I also tried sending through my company's Microsoft exchange server by replacing the localhost entry in the MERCURY.INI file thusly ...</P> <P>[General] myname:          USEA-EXCH7.na.uis.unisys.com    # Canonical name for this server</P> <P>However, the result was the same.</P> <P>I now just have more messages in a "pending" state.</P> <P>i.e. The "Mercury Core Process" windows says "Queue Status / Outgoing Jobs / Pending = 7" </P> <P>Fri 07, 14:54:23: Job MG00003A: from <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local)    Created outgoing job with ID MO00003B    To: <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local) -OK Fri 07, 14:54:34: Job MG00003D: from <A href="mailto:alexander.ryan@unisys.com">alexander.ryan@unisys.com</A> (non-local)    Created outgoing job with ID MO00003E    To: <A href="mailto:alexander.j.ryan@gmail.com">alexander.j.ryan@gmail.com</A> (non-local) -OK  </P> <P>Dumb question:</P> <P>Does "pending" mean that Mercury has not sent them yet?</P> <P>If so, it wouldn't matter if other mail servers would treat them as spam or not right?</P> <P mce_keep="true"> </P> <P mce_keep="true"> </P>

> I switched to Mercury C as you suggested.
>
> I also tried sending through my company's Microsoft exchange server by
> replacing the localhost entry in the MERCURY.INI file thusly ...
>
> [General]
> myname:          USEA-EXCH7.na.uis.unisys.com    # Canonical name for this server
>
> However, the result was the same.
>
> I now just have more messages in a "pending" state.
>
> i.e. The "Mercury Core Process" windows says "Queue Status / Outgoing Jobs / Pending = 7"

What is in the mail queue directory?  If there are MO*.QDF/QCF file pairs in the queue then this means that MercuryC is failing to process the outbound jobs.  

Turn on session logging in MercuryC and then provide us with a copy of one of the *.MC files in the MercuryC session logging directory.


>
> Fri 07, 14:54:23: Job MG00003A: from alexander.ryan@unisys.com (non-local)
>    Created outgoing job with ID MO00003B
>    To: alexander.ryan@unisys.com (non-local) -OK
> Fri 07, 14:54:34: Job MG00003D: from alexander.ryan@unisys.com (non-local)
>    Created outgoing job with ID MO00003E
>    To: alexander.j.ryan@gmail.com (non-local) -OK
>  
>
> Dumb question:
>
> Does "pending" mean that Mercury has not sent them yet?

Not yet processed.  The reason depends a lot on the file type in the queue.  The MG*.QCF/QDF files are to be processed by core, the MO*.QCF/QDF are to be processed by the outbound client.

>
> If so, it wouldn't matter if other mail servers would treat them as spam or not right?

If the receiving server is not providing a 500 series fatal error message then they will continue to be tried until the limit is reached.  The default is every 30 minutes and 16 retries.

 

<p>> I switched to Mercury C as you suggested. > > I also tried sending through my company's Microsoft exchange server by > replacing the localhost entry in the MERCURY.INI file thusly ... > > [General] > myname:          USEA-EXCH7.na.uis.unisys.com    # Canonical name for this server > > However, the result was the same. > > I now just have more messages in a "pending" state. > > i.e. The "Mercury Core Process" windows says "Queue Status / Outgoing Jobs / Pending = 7" What is in the mail queue directory?  If there are MO*.QDF/QCF file pairs in the queue then this means that MercuryC is failing to process the outbound jobs.   Turn on session logging in MercuryC and then provide us with a copy of one of the *.MC files in the MercuryC session logging directory. > > Fri 07, 14:54:23: Job MG00003A: from alexander.ryan@unisys.com (non-local) >    Created outgoing job with ID MO00003B >    To: alexander.ryan@unisys.com (non-local) -OK > Fri 07, 14:54:34: Job MG00003D: from alexander.ryan@unisys.com (non-local) >    Created outgoing job with ID MO00003E >    To: alexander.j.ryan@gmail.com (non-local) -OK >   > > Dumb question: > > Does "pending" mean that Mercury has not sent them yet? Not yet processed.  The reason depends a lot on the file type in the queue.  The MG*.QCF/QDF files are to be processed by core, the MO*.QCF/QDF are to be processed by the outbound client. > > If so, it wouldn't matter if other mail servers would treat them as spam or not right? If the receiving server is not providing a 500 series fatal error message then they will continue to be tried until the limit is reached.  The default is every 30 minutes and 16 retries.</p><p> </p>

Thank you for the suggestion.

Unfortunately after turning on logging Mercury crashes every time I try to start it.

"Mercury/32 Core Processing Module v4.62 has encountered a problem and needs to close."

Since there's no way to undo the changes I guess I have to re-install Mercury right?

That means that I'll have to re-install all of XAMPP.

GRRRRRR!!!!

I'm thinking that sending e-mails should be easier than this. :)

<P>Thank you for the suggestion.</P> <P>Unfortunately after turning on logging Mercury crashes every time I try to start it.</P> <P>"Mercury/32 Core Processing Module v4.62 has encountered a problem and needs to close."</P> <P>Since there's no way to undo the changes I guess I have to re-install Mercury right?</P> <P>That means that I'll have to re-install all of XAMPP.</P> <P>GRRRRRR!!!!</P> <P>I'm thinking that sending e-mails should be easier than this. :)</P>
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