Community Discussions and Support
AW: cannot run Mercury - app window vanishes

Incoming messages will be handled by MercuryS, the SMTP server module. You will need one of the SMTP client modules, MercuryE or MercuryC, if you want to be able to send out messages through Mercury. If it's only for receiving from the Lotus Notes client both those modules can be disabled.

/Rolf

 

<p>Incoming messages will be handled by MercuryS, the SMTP server module. You will need one of the SMTP client modules, MercuryE or MercuryC, if you want to be able to send out messages through Mercury. If it's only for receiving from the Lotus Notes client both those modules can be disabled.</p><p>/Rolf </p><p> </p>

Hello, all. I just downloaded and installed the latest version of Mercury from pmail.com. Installation was uneventful. But I cannot get the program to run.

When I launch the Mercurcy application, the Mercury window briefly appears -- for a fraction of a second -- and then it disappears completely (and its PID disappears from the Task Manager). If I run the "Mercury Launcher" application instead, Mercury continually loads and disappears, loads and disappears, endlessly, until I kill the Launcher using Task Manager.

No log files appear anywhere in any of the Mercury log folders (all those folders are empty). And no messages appear in any of my antivirus logs.

I tried killing all nonessential processes on my computer (including antivirus processes), but doing so had no effect -- Mercury continues to vanish a split-second after its window appears.

I would be grateful for any suggestion on how to track down the source of the problem (I have searched these boards without success), or if the problem is known, to work around the problem.

Thanks for your help!

 

<p>Hello, all. I just downloaded and installed the latest version of Mercury from pmail.com. Installation was uneventful. But I cannot get the program to run. </p><p>When I launch the Mercurcy application, the Mercury window briefly appears -- for a fraction of a second -- and then it disappears completely (and its PID disappears from the Task Manager). If I run the "Mercury Launcher" application instead, Mercury continually loads and disappears, loads and disappears, endlessly, until I kill the Launcher using Task Manager.</p><p>No log files appear anywhere in any of the Mercury log folders (all those folders are empty). And no messages appear in any of my antivirus logs.</p><p>I tried killing all nonessential processes on my computer (including antivirus processes), but doing so had no effect -- Mercury continues to vanish a split-second after its window appears. </p><p>I would be grateful for any suggestion on how to track down the source of the problem (I have searched these boards without success), or if the problem is known, to work around the problem.</p><p>Thanks for your help! </p><p> </p>

The only thing that has been known to give effects like that is if the mercury.ini file in the Mercury directory is damaged, but if it's a totally new installation that's not very likely.

It might be helpful with some information about the environment. What Windows version do you run, and what kind of processor is it?

Did you check Windows event logs for entries that could be releated to this?

As a general rule Mercury will expect to have uninterrupted disk access to all it's directories, so any program that interferes with this can cause problems. Shutting down the main processes may not always remove this behavior as there can be hooks of different kinds created at system start-up.

/Rolf 

<p>The only thing that has been known to give effects like that is if the mercury.ini file in the Mercury directory is damaged, but if it's a totally new installation that's not very likely.</p><p>It might be helpful with some information about the environment. What Windows version do you run, and what kind of processor is it?</p><p>Did you check Windows event logs for entries that could be releated to this?</p><p>As a general rule Mercury will expect to have uninterrupted disk access to all it's directories, so any program that interferes with this can cause problems. Shutting down the main processes may not always remove this behavior as there can be hooks of different kinds created at system start-up.</p><p>/Rolf </p>

I'm on WinXP SP 2, Intel Core2 Duo.

To try working around possible disk access issues, I tried uninstalling Mercury from my C partition, then reinstalling it on the D partition -- but the app window continues to vanish as before.

Window event manager shows a single error:

Event Type:    Error
Event Source:    Application Error
Event Category:    None
Description: Faulting application mercury.exe, version 4.7.2.0, faulting module mercurye.dll, version 4.7.2.0, fault address 0x00017960.

Is the fault address helpful?

 

 

<p>I'm on WinXP SP 2, Intel Core2 Duo.</p><p>To try working around possible disk access issues, I tried uninstalling Mercury from my C partition, then reinstalling it on the D partition -- but the app window continues to vanish as before. </p><p>Window event manager shows a single error:</p><p>Event Type:    Error Event Source:    Application Error Event Category:    None Description: Faulting application mercury.exe, version 4.7.2.0, faulting module mercurye.dll, version 4.7.2.0, fault address 0x00017960. </p><p>Is the fault address helpful? </p><p> </p><p> </p>

Lot of people run Mercury on that OS version and processor, so that's not an issue. As the event log indicates that the error occurs in the mercurye.dll library I would suggest switching to MercuryC as a test. To do this you will need to edit MERCURY.INI manually. Open it in Notepad and change the Protocols section:

[Protocols]

MERCURYS.DLL

MERCURYP.DLL

# MERCURYE.DLL

MERCURYC.DLL

# MERCURYD.DLL

# MERCURYH.DLL

# MERCURYF.DLL

# MERCURYW.DLL

# MERCURYX.DLL

MERCURYI.DLL

# MERCURYB.DLL 

If you are able to start Mercury after doing this change we know that the problem has to do with something releating to MercuryE.

/Rolf 

<p>Lot of people run Mercury on that OS version and processor, so that's not an issue. As the event log indicates that the error occurs in the mercurye.dll library I would suggest switching to MercuryC as a test. To do this you will need to edit MERCURY.INI manually. Open it in Notepad and change the Protocols section:</p> <blockquote> <i>[Protocols]</i> <i>MERCURYS.DLL</i> <i>MERCURYP.DLL</i> <i># MERCURYE.DLL</i> <i>MERCURYC.DLL</i> <i># MERCURYD.DLL</i> <i># MERCURYH.DLL</i> <i># MERCURYF.DLL</i> <i># MERCURYW.DLL</i> <i># MERCURYX.DLL</i> <i>MERCURYI.DLL</i> <i># MERCURYB.DLL </i> </blockquote> <p>If you are able to start Mercury after doing this change we know that the problem has to do with something releating to MercuryE.</p> <p>/Rolf </p>

Hi,

I had similar thing happen before and it was either:

1)  a security issue (Mercury does not have full access to files where ever you are running it from)

OR

2.)  the Mercury.ini file was messed up.

Check the PATHS under the PROTOCOLS section in the mercury.ini:

They should be the UNC path like \\machinename\Mercury\mercurye.dll if over the network. 

This can cause the module to fail loading, which in turn restarts Mercuy over and over again, I'm not sure why Mercury does that.

=D

Mark 

 

<P>Hi,</P> <P>I had similar thing happen before and it was either:</P> <P>1)  a security issue (Mercury does not have full access to files where ever you are running it from) </P> <P>OR</P> <P>2.)  the Mercury.ini file was messed up.</P> <P>Check the PATHS under the PROTOCOLS section in the mercury.ini:</P> <P>They should be the UNC path like <A href="file://machinename/Mercury/mercurye.dll">\\machinename\Mercury\mercurye.dll</A> if over the network. </P> <P>This can cause the module to fail loading, which in turn restarts Mercuy over and over again, I'm not sure why Mercury does that.</P> <P>=D</P> <P>Mark </P> <P mce_keep="true"> </P>

Thanks for your help!

 1) Rolf: when I changed the protocol section as you suggested, Mercury did not crash. So the problem does seem to lie in MercuryE. What could I try next?

2) Mrpush: there is no PATHS section in my Mercury.ini file. Can you give an example of what it should look like?

Thanks again.

<p>Thanks for your help!</p><p> 1) Rolf: when I changed the protocol section as you suggested, Mercury did not crash. So the problem does seem to lie in MercuryE. What could I try next?</p><p>2) Mrpush: there is no PATHS section in my Mercury.ini file. Can you give an example of what it should look like?</p><p>Thanks again. </p>

Here is another thought. I am trying to run Mercury locally on a single machine. At the point in the installation process where I was asked for an IP address, I simply entered "localhost". Could the "localhost" be related to the MercuryE behavior? Or maybe I need to modify my machine's hosts file, as mentioned here: http://thegoldenear.org/toolbox/windows/docs/mercury-config.html ?

Here is another thought. I am trying to run Mercury locally on a single machine. At the point in the installation process where I was asked for an IP address, I simply entered "localhost". Could the "localhost" be related to the MercuryE behavior? Or maybe I need to modify my machine's hosts file, as mentioned here: http://thegoldenear.org/toolbox/windows/docs/mercury-config.html ?

Hi,

My protocol section in the INI looks like this:

[Protocols]
\\Server\MERCURY$\mercurys.dll
\\Server\MERCURY$\mercurye.dll

etc

Since you have Mercury installed and running on the same machine, it should look like:

[Protocols]
C:\MERCURY\mercurys.dll
etc

I don't recall the exact place in the install where it asked for an IP. 

The local host could be an issue, why not just enter the IP of the local machine,

or under the MercyE section of your INI, set Name Server to blank by putting a # in front like this:  No lines in the INI are read with a "#" in front of them.

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

Are you sure you are logged in with a user that has full admin rights?  I recall having issues like this when I did not have full rights.

Mark

  

 

<P>Hi,</P> <P>My protocol section in the INI looks like this:</P> <P>[Protocols] <A href="file://server/MERCURY$/mercurys.dll">\\Server\MERCURY$\mercurys.dll</A> <A href="file://server/MERCURY$/mercurye.dll">\\Server\MERCURY$\mercurye.dll</A></P> <P>etc</P> <P>Since you have Mercury installed and running on the same machine, it should look like:</P> <P>[Protocols] C:<A href="file://mercury$/mercurys.dll">\MERCURY\mercurys.dll</A> etc</P> <P>I don't recall the exact place in the install where it asked for an IP.  </P> <P>The local host could be an issue, why not just enter the IP of the local machine, </P> <P>or under the MercyE section of your INI, set Name Server to blank by putting a # in front like this:  No lines in the INI are read with a "#" in front of them.</P> <P>[MercuryE] Poll : 15 Timeout : 60 # Session_logging : o:\mail\mercury\melogs # Session_logmode : 1 <STRONG><U># Nameservers : 139.80.64.1</U></STRONG> </P> <P>Are you sure you are logged in with a user that has full admin rights?  I recall having issues like this when I did not have full rights.</P> <P>Mark</P> <P>  </P> <P mce_keep="true"> </P>

Here is another thought. I am trying to run Mercury locally on a single

machine. At the point in the installation process where I was asked for

an IP address, I simply entered "localhost". Could the "localhost" be

related to the MercuryE behavior? Or maybe I need to modify my

machine's hosts file, as mentioned here:

http://thegoldenear.org/toolbox/windows/docs/mercury-config.html ?

How about providing a copy of your systems mercury.ini file for analysis so we all can quite guessing about how you are setup.  ;-)
<blockquote>Here is another thought. I am trying to run Mercury locally on a single machine. At the point in the installation process where I was asked for an IP address, I simply entered "localhost". Could the "localhost" be related to the MercuryE behavior? Or maybe I need to modify my machine's hosts file, as mentioned here: http://thegoldenear.org/toolbox/windows/docs/mercury-config.html ?</blockquote>How about providing a copy of your systems mercury.ini file for analysis so we all can quite guessing about how you are setup.  ;-)

Thanks for this, Mark.

I don't have admin rights on my computer. It is a work laptop with Lotus Notes on it. Because the Lotus Notes client is so awful -- it literally takes 20 seconds to switch from one email to another email, even if both emails were previously read -- I'm trying to pull all my email from Lotus into a different client (Thunderbird) on the same machine.

I don't have access to my company's Lotus Notes mail server, so what I'm trying to do is, 1) install Mercury to be a local SMTP server on my laptop, 2) forward all the email from the laptop's Lotus Notes client to Mercury, 3) read the email from Mercury using Thunderbird.

Because my laptop moves around a lot, and also for security reasons, I want Mercury to be accessible only from my laptop -- not from any other computer, anywhere. That's why I'm trying to configure Mercuy using localhost as the IP address.

So the goal is for Mercury and Thunderbird to both be resident on my laptop, but able to talk only to each other (and to the Lotus Notes client on the same laptop).

I was inspired by this article:

http://www.benshoemate.com/2007/11/09/how-to-upload-all-your-old-archived-email-to-gmail-from-outlook-lotus-notes-and-unix-pine/  . However, in contrast to the article, it is important that my email stay resident only on my laptop. I just want to get my work email into a different reader -- it is important that the email never leave my work laptop, and that the email not be remotely accessible by other machines or servers.

It feels to me that debugging the Mercury crash behavior could take a lot more work. What do you think is the best way to move forward? What alternate lightweight SMTP servers would you recommend that I try installing?

Thanks for your advice!


<p>Thanks for this, Mark. </p><p>I don't have admin rights on my computer. It is a work laptop with Lotus Notes on it. Because the Lotus Notes client is so awful -- it literally takes 20 seconds to switch from one email to another email, even if both emails were previously read -- I'm trying to pull all my email from Lotus into a different client (Thunderbird) on the same machine. </p><p>I don't have access to my company's Lotus Notes mail server, so what I'm trying to do is, 1) install Mercury to be a local SMTP server on my laptop, 2) forward all the email from the laptop's Lotus Notes client to Mercury, 3) read the email from Mercury using Thunderbird. </p><p>Because my laptop moves around a lot, and also for security reasons, I want Mercury to be accessible only from my laptop -- not from any other computer, anywhere. That's why I'm trying to configure Mercuy using localhost as the IP address.</p><p>So the goal is for Mercury and Thunderbird to both be resident on my laptop, but able to talk only to each other (and to the Lotus Notes client on the same laptop).</p><p>I was inspired by this article: http://www.benshoemate.com/2007/11/09/how-to-upload-all-your-old-archived-email-to-gmail-from-outlook-lotus-notes-and-unix-pine/  . However, in contrast to the article, it is important that my email stay resident only on my laptop. I just want to get my work email into a different reader -- it is important that the email never leave my work laptop, and that the email not be remotely accessible by other machines or servers. </p><p>It feels to me that debugging the Mercury crash behavior could take a lot more work. What do you think is the best way to move forward? What alternate lightweight SMTP servers would you recommend that I try installing?</p><p>Thanks for your advice! </p><p> </p>

[quote user="bostoneer"]

Thanks for this, Mark.

I don't have admin rights on my computer. It is a work laptop with Lotus Notes on it. Because the Lotus Notes client is so awful -- it literally takes 20 seconds to switch from one email to another email, even if both emails were previously read -- I'm trying to pull all my email from Lotus into a different client (Thunderbird) on the same machine.

I don't have access to my company's Lotus Notes mail server, so what I'm trying to do is, 1) install Mercury to be a local SMTP server on my laptop, 2) forward all the email from the laptop's Lotus Notes client to Mercury, 3) read the email from Mercury using Thunderbird.

Because my laptop moves around a lot, and also for security reasons, I want Mercury to be accessible only from my laptop -- not from any other computer, anywhere. That's why I'm trying to configure Mercuy using localhost as the IP address.

So the goal is for Mercury and Thunderbird to both be resident on my laptop, but able to talk only to each other (and to the Lotus Notes client on the same laptop).

I was inspired by this article:

http://www.benshoemate.com/2007/11/09/how-to-upload-all-your-old-archived-email-to-gmail-from-outlook-lotus-notes-and-unix-pine/  . However, in contrast to the article, it is important that my email stay resident only on my laptop. I just want to get my work email into a different reader -- it is important that the email never leave my work laptop, and that the email not be remotely accessible by other machines or servers.

It feels to me that debugging the Mercury crash behavior could take a lot more work. What do you think is the best way to move forward? What alternate lightweight SMTP servers would you recommend that I try installing?

Thanks for your advice!


[/quote]

 

Wich version of Notes you use?

Normaly lotus notes is only slow, if the database is to big ( so more than ~ 4  GB). Have you a second environment, to run Notes without connect to the Server?

You can do different things to make Notes faster:

  1. Compress your Database (Open the Property-Window of your Database, Klick the Information-Tab and check how many percent of the Database are used. If under 60 %, compress the Database. See more information on the lotus notes help.
  2. Install the local archiving.
  3. If you have a clue of DOS,you can run ncompact and nfixup to repair your database.
  4. Have you checked the local protocoll for errors ?
Sorry i know it has nothing to do with Merury, but that are the points i would do, if i have this problems. And i think at last, you have a IT-Department to fix the problem.[;)]

 

[quote user="bostoneer"]<p>Thanks for this, Mark. </p><p>I don't have admin rights on my computer. It is a work laptop with Lotus Notes on it. Because the Lotus Notes client is so awful -- it literally takes 20 seconds to switch from one email to another email, even if both emails were previously read -- I'm trying to pull all my email from Lotus into a different client (Thunderbird) on the same machine. </p><p>I don't have access to my company's Lotus Notes mail server, so what I'm trying to do is, 1) install Mercury to be a local SMTP server on my laptop, 2) forward all the email from the laptop's Lotus Notes client to Mercury, 3) read the email from Mercury using Thunderbird. </p><p>Because my laptop moves around a lot, and also for security reasons, I want Mercury to be accessible only from my laptop -- not from any other computer, anywhere. That's why I'm trying to configure Mercuy using localhost as the IP address.</p><p>So the goal is for Mercury and Thunderbird to both be resident on my laptop, but able to talk only to each other (and to the Lotus Notes client on the same laptop).</p><p>I was inspired by this article: http://www.benshoemate.com/2007/11/09/how-to-upload-all-your-old-archived-email-to-gmail-from-outlook-lotus-notes-and-unix-pine/  . However, in contrast to the article, it is important that my email stay resident only on my laptop. I just want to get my work email into a different reader -- it is important that the email never leave my work laptop, and that the email not be remotely accessible by other machines or servers. </p><p>It feels to me that debugging the Mercury crash behavior could take a lot more work. What do you think is the best way to move forward? What alternate lightweight SMTP servers would you recommend that I try installing?</p><p>Thanks for your advice! </p><p> </p><p>[/quote]</p><p> </p><p>Wich version of Notes you use? </p><p>Normaly lotus notes is only slow, if the database is to big ( so more than ~ 4  GB). Have you a second environment, to run Notes without connect to the Server?</p><p>You can do different things to make Notes faster:</p><ol><li>Compress your Database (Open the Property-Window of your Database, Klick the Information-Tab and check how many percent of the Database are used. If under 60 %, compress the Database. See more information on the lotus notes help.</li><li>Install the local archiving.</li><li>If you have a clue of DOS,you can run ncompact and nfixup to repair your database.</li><li>Have you checked the local protocoll for errors ?</li></ol>Sorry i know it has nothing to do with Merury, but that are the points i would do, if i have this problems. And i think at last, you have a IT-Department to fix the problem.[;)] <p>  </p>

Thanks for this advice. I have spent several weeks trying to speed up Lotus Notes. The problem is not the mailbox size; the problem is that the latest version of the Lotus Notes client is written in Java and runs very, very slowly even though my laptop is high-end. The IT department of my company has not been helpful. So my goal here is to get the emails out of Lotus Notes while preserving security.

Thanks for this advice. I have spent several weeks trying to speed up Lotus Notes. The problem is not the mailbox size; the problem is that the latest version of the Lotus Notes client is written in Java and runs very, very slowly even though my laptop is high-end. The IT department of my company has not been helpful. So my goal here is to get the emails out of Lotus Notes while preserving security.

As Thomas said, it might help seeing your mercury.ini file. I'm not clear on where you have tried to enter "localhost" as IP, but change it to 127.0.0.1 anyhow. If Mercury is correctly set up it should be able to receive SMTP communication locally at least. As you move around to different nets with the computer I'm not sure if you will be able to use Mercury to send messages externally, though.

/Rolf

<p>As Thomas said, it might help seeing your mercury.ini file. I'm not clear on where you have tried to enter "localhost" as IP, but change it to 127.0.0.1 anyhow. If Mercury is correctly set up it should be able to receive SMTP communication locally at least. As you move around to different nets with the computer I'm not sure if you will be able to use Mercury to send messages externally, though.</p><p>/Rolf </p>

Here is my current mercury.ini file. The only thing I changed after installation was the Protocols section, per an earlier suggestion above. With this mercury.ini file in place, on my machine, Mercury crashes immediately after its window appears.

-----------------------------------------------------

 

#  MERCURY.INI generated by Mercury Setup
#
#
#  Sample Bindery Mode / Standalone Mode MERCURY.INI file.
#  This sample file implements most of the possible switches for each
#  module, but you can edit it to do less if you wish.
#
#  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.
#
#  Note that in general, manual modification of this file is NOT
#  RECOMMENDED - use the Mercury "Configuration" menu to change the
#  program's settings wherever possible.
#

[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:   D:\MERCURY\QUEUE   # Where mail should be put for delivery
smtpqueue:   D:\MERCURY\QUEUE   # Where the SMTP client should look for mail
newmail_path: D:\MERCURY\MAIL\~N

[Protocols]
D:\MERCURY\MERCURYS.DLL
D:\MERCURY\MERCURYP.DLL
D:\MERCURY\MERCURYE.DLL
# MERCURYC.DLL
# MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
# MERCURYW.DLL
# MERCURYX.DLL
D:\MERCURY\MERCURYI.DLL
# MERCURYB.DLL


[Mercury]
failfile:     D:\MERCURY\Mercury\FAILURE.MER  # Delivery failure notification template
confirmfile:  D:\MERCURY\Mercury\CONFIRM.MER  # Delivery confirmation template
aliasfile:    D:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file
synfile:      D:\MERCURY\Mercury\SYNONYM.MER  # User synonym database
listfile:     D:\MERCURY\Mercury\LISTS.MER    # List of lists
logfile:      D:\MERCURY\Logs\Core\~y-~m-~d.log  # Traffic logging file
# bitnethost:   cunyvm.cuny.edu      # Relay host for ".bitnet" rewrites
poll:         10                   # Seconds between queue polling cycles
scratch:      D:\MERCURY\Scratch   # Where we can write temp files
returnlines:  15                   # How many lines of failed messages to return
postmaster:   Admin   # Local user who acts as 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
# noticeboards: SYS:PUBLIC/NB        # Where to find Pegasus Mail noticeboards
auto_tzone:   1                    # If NZ, obtain timezone information from OS

[MercuryC]
logfile : D:\MERCURY\Logs\MercuryC\~y-~m-~d.log   # Traffic logging file
Session_logging : D:\MERCURY\Sessions\MercuryC\    # Directory for session log files
Session_logmode : 0
host:             # mail mail host which relays for us
scratch:     D:\MERCURY\scratch           # Where we can write temp files
poll:        30                   # Seconds between queue polling cycles
returnlines: 15                   # How many lines of failed messages to return
failfile:    D:\MERCURY\Mercury\FAILURE.MER  # Delivery failure template
esmtp:       1                    # Yes, we want to use ESMTP extensions

[MercuryE]
Poll : 15
Timeout : 60
logfile : D:\MERCURY\Logs\MercuryE\~y-~m-~d.log   # Traffic logging file
Session_logging : D:\MERCURY\Sessions\MercuryE\   # Directory for session log files
Session_logmode : 0
# Nameservers : 139.80.64.1

[MercuryD]
Session_logging : D:\MERCURY\Sessions\MercuryD\    # Directory for session log files
Session_logmode : 0
Scratch : D:\MERCURY\Scratch\MercuryD
# Timeout : 30
# Poll : 120               # How often to check hosts for new mail (seconds)

[MercuryS]
logfile : D:\MERCURY\Logs\MercuryS\~y-~m-~d.log   # Traffic logging file
Session_logging : D:\MERCURY\Sessions\MercuryS\    # Directory for session log files
Session_logmode : 0
debug:       1                    # Whether or not to show session progress
# allow:       192.156.225.2        # A machine we WILL permit to connect
# refuse:      192.156.225.0        # A group of machines we WON'T permit.
# size:        1500000
Relay : 0         # Control non-local relaying
Strict_Relay : 1  # Use strict relaying controls


[MercuryP]
logfile : D:\MERCURY\Logs\MercuryP\~y-~m-~d.log   # Traffic logging file
Session_logging : D:\MERCURY\Sessions\MercuryP\   # Directory for session log files
Session_logmode : 0
Scratch : D:\MERCURY\Scratch\MercuryP
Timeout : 60
UIDL_nul_list : 1
New_UIDs : 1
No_NUL_passwords : 1

[MercuryX]
Drain_queues: 1
# 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]
# NetWare Server           Domain name
localhost  :  localhost
localhost  :  localhost

# [Rewrite]
# *                    : pmail.gen.nz

[Maiser]
Maiser               :     Maiser
Helpfile             :     D:\MERCURY\Mercury\MAISER.HLP
Lookupfile           :     D:\MERCURY\Mercury\MAISER.LKP
Send_dir             :     D:\MERCURY\Mercury\SENDABLE
Logfile              :     D:\MERCURY\Logs\Maiser\~y-~m-~d.LOG
Notify               :     D:\MERCURY\Mercury\TMP
Local_only           :     Y

[MercuryH]
logfile : D:\MERCURY\Logs\MercuryH\~y-~m-~d.log   # Traffic logging file
# 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 : D:\MERCURY\Scratch\MercuryI
logfile : D:\MERCURY\Logs\MercuryI\~y-~m-~d.log   # Traffic logging file
Session_logging : D:\MERCURY\Sessions\MercuryI\   # Directory for session log files
Session_logmode : 0
Timeout : 120
Server_Port : 143
Idle_Timeout : 1800

[MercuryB]
Scratch : D:\MERCURY\Scratch\MercuryB
logfile : D:\MERCURY\Logs\MercuryB\~y-~m-~d.log   # Traffic logging file
Session_logging : D:\MERCURY\Sessions\MercuryB\   # Directory for session log files
Session_logmode : 0
Timeout : 120
Server_Port : 80
Idle_Timeout : 1800
# URL_Base : enter_your_domain_here

 

<p>Here is my current mercury.ini file. The only thing I changed after installation was the Protocols section, per an earlier suggestion above. With this mercury.ini file in place, on my machine, Mercury crashes immediately after its window appears. </p><p>-----------------------------------------------------</p><p> </p><p>#  MERCURY.INI generated by Mercury Setup # # #  Sample Bindery Mode / Standalone Mode MERCURY.INI file. #  This sample file implements most of the possible switches for each #  module, but you can edit it to do less if you wish. # #  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. # #  Note that in general, manual modification of this file is NOT #  RECOMMENDED - use the Mercury "Configuration" menu to change the #  program's settings wherever possible. # [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:   D:\MERCURY\QUEUE   # Where mail should be put for delivery smtpqueue:   D:\MERCURY\QUEUE   # Where the SMTP client should look for mail newmail_path: D:\MERCURY\MAIL\~N [Protocols] D:\MERCURY\MERCURYS.DLL D:\MERCURY\MERCURYP.DLL D:\MERCURY\MERCURYE.DLL # MERCURYC.DLL # MERCURYD.DLL # MERCURYH.DLL # MERCURYF.DLL # MERCURYW.DLL # MERCURYX.DLL D:\MERCURY\MERCURYI.DLL # MERCURYB.DLL [Mercury] failfile:     D:\MERCURY\Mercury\FAILURE.MER  # Delivery failure notification template confirmfile:  D:\MERCURY\Mercury\CONFIRM.MER  # Delivery confirmation template aliasfile:    D:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file synfile:      D:\MERCURY\Mercury\SYNONYM.MER  # User synonym database listfile:     D:\MERCURY\Mercury\LISTS.MER    # List of lists logfile:      D:\MERCURY\Logs\Core\~y-~m-~d.log  # Traffic logging file # bitnethost:   cunyvm.cuny.edu      # Relay host for ".bitnet" rewrites poll:         10                   # Seconds between queue polling cycles scratch:      D:\MERCURY\Scratch   # Where we can write temp files returnlines:  15                   # How many lines of failed messages to return postmaster:   Admin   # Local user who acts as 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 # noticeboards: SYS:PUBLIC/NB        # Where to find Pegasus Mail noticeboards auto_tzone:   1                    # If NZ, obtain timezone information from OS [MercuryC] logfile : D:\MERCURY\Logs\MercuryC\~y-~m-~d.log   # Traffic logging file Session_logging : D:\MERCURY\Sessions\MercuryC\    # Directory for session log files Session_logmode : 0 host:             # mail mail host which relays for us scratch:     D:\MERCURY\scratch           # Where we can write temp files poll:        30                   # Seconds between queue polling cycles returnlines: 15                   # How many lines of failed messages to return failfile:    D:\MERCURY\Mercury\FAILURE.MER  # Delivery failure template esmtp:       1                    # Yes, we want to use ESMTP extensions [MercuryE] Poll : 15 Timeout : 60 logfile : D:\MERCURY\Logs\MercuryE\~y-~m-~d.log   # Traffic logging file Session_logging : D:\MERCURY\Sessions\MercuryE\   # Directory for session log files Session_logmode : 0 # Nameservers : 139.80.64.1 [MercuryD] Session_logging : D:\MERCURY\Sessions\MercuryD\    # Directory for session log files Session_logmode : 0 Scratch : D:\MERCURY\Scratch\MercuryD # Timeout : 30 # Poll : 120               # How often to check hosts for new mail (seconds) [MercuryS] logfile : D:\MERCURY\Logs\MercuryS\~y-~m-~d.log   # Traffic logging file Session_logging : D:\MERCURY\Sessions\MercuryS\    # Directory for session log files Session_logmode : 0 debug:       1                    # Whether or not to show session progress # allow:       192.156.225.2        # A machine we WILL permit to connect # refuse:      192.156.225.0        # A group of machines we WON'T permit. # size:        1500000 Relay : 0         # Control non-local relaying Strict_Relay : 1  # Use strict relaying controls [MercuryP] logfile : D:\MERCURY\Logs\MercuryP\~y-~m-~d.log   # Traffic logging file Session_logging : D:\MERCURY\Sessions\MercuryP\   # Directory for session log files Session_logmode : 0 Scratch : D:\MERCURY\Scratch\MercuryP Timeout : 60 UIDL_nul_list : 1 New_UIDs : 1 No_NUL_passwords : 1 [MercuryX] Drain_queues: 1 # 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] # NetWare Server           Domain name localhost  :  localhost localhost  :  localhost # [Rewrite] # *                    : pmail.gen.nz [Maiser] Maiser               :     Maiser Helpfile             :     D:\MERCURY\Mercury\MAISER.HLP Lookupfile           :     D:\MERCURY\Mercury\MAISER.LKP Send_dir             :     D:\MERCURY\Mercury\SENDABLE Logfile              :     D:\MERCURY\Logs\Maiser\~y-~m-~d.LOG Notify               :     D:\MERCURY\Mercury\TMP Local_only           :     Y [MercuryH] logfile : D:\MERCURY\Logs\MercuryH\~y-~m-~d.log   # Traffic logging file # 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 : D:\MERCURY\Scratch\MercuryI logfile : D:\MERCURY\Logs\MercuryI\~y-~m-~d.log   # Traffic logging file Session_logging : D:\MERCURY\Sessions\MercuryI\   # Directory for session log files Session_logmode : 0 Timeout : 120 Server_Port : 143 Idle_Timeout : 1800 [MercuryB] Scratch : D:\MERCURY\Scratch\MercuryB logfile : D:\MERCURY\Logs\MercuryB\~y-~m-~d.log   # Traffic logging file Session_logging : D:\MERCURY\Sessions\MercuryB\   # Directory for session log files Session_logmode : 0 Timeout : 120 Server_Port : 80 Idle_Timeout : 1800 # URL_Base : enter_your_domain_here  </p>

I can't see any obvious reason for the crash, but there are some things that need to be fixed. The Domains section is crucial and should in your case probably look something like this:

[Domains]

Mercury: foo

Mercury: [127.0.0.1] 

Replace foo with the hostname assigned in Windows, and put the same name as myname under General. (Avoid using localhost here, it will only confuse.)

/Rolf 

<p>I can't see any obvious reason for the crash, but there are some things that need to be fixed. The Domains section is crucial and should in your case probably look something like this:</p> <blockquote> <i>[Domains]</i> <i>Mercury: foo</i> <i>Mercury: [127.0.0.1] </i> </blockquote> <p>Replace foo with the hostname assigned in Windows, and put the same name as myname under General. (Avoid using localhost here, it will only confuse.)</p> <p>/Rolf </p>

Thanks for the advice, Rolf. I made those changes but Mercury still crashes right after its window appears.

Team, my work schedule is getting heavier and it's tough for me to debug any further. I really appreciate your help and I'd be grateful if you could recommend an alternate lightweight SMTP server -- ideally something that's easy to install on WinXP, and simple to configure.

Thanks again for all your help!

<p>Thanks for the advice, Rolf. I made those changes but Mercury still crashes right after its window appears.</p><p>Team, my work schedule is getting heavier and it's tough for me to debug any further. I really appreciate your help and I'd be grateful if you could recommend an alternate lightweight SMTP server -- ideally something that's easy to install on WinXP, and simple to configure.</p><p>Thanks again for all your help! </p>

As discussed before you can switch from MercuryE to MercuryC to avoid the crashes. Finding out why MercuryE crashes may require some heavyweight debugging with a disk access surveillance tool. The only simple thing I can think of is to make sure there aren't any possibly defect files left in the queue directory.

/Rolf 

<p>As discussed before you can switch from MercuryE to MercuryC to avoid the crashes. Finding out why MercuryE crashes may require some heavyweight debugging with a disk access surveillance tool. The only simple thing I can think of is to make sure there aren't any possibly defect files left in the queue directory.</p><p>/Rolf </p>

> Team, my work schedule is getting heavier and it's tough for me to debug any further. I really appreciate your help and I'd be grateful
> if you could recommend an alternate lightweight SMTP server -- ideally something that's easy to install on WinXP, and simple to configure.

You've got it, every other one is much more difficult.  As long as Mercury/32 is installed to c:\mercury and Mercury has read/write access to this directory and all subdirectories it will run.

> Team, my work schedule is getting heavier and it's tough for me to debug any further. I really appreciate your help and I'd be grateful > if you could recommend an alternate lightweight SMTP server -- ideally something that's easy to install on WinXP, and simple to configure. You've got it, every other one is much more difficult.  As long as Mercury/32 is installed to c:\mercury and Mercury has read/write access to this directory and all subdirectories it will run.

Thanks for the tip! I don't quite understand the difference between E and C. Will C be able to act as a stand-alone SMTP server on my machine? (I don't have access to my company's SMTP server -- so I will have to set Lotus Notes to auto-forward all of its incoming emails to the instance of Mercury that is running on my machine.) Thanks again.

Thanks for the tip! I don't quite understand the difference between E and C. Will C be able to act as a stand-alone SMTP server on my machine? (I don't have access to my company's SMTP server -- so I will have to set Lotus Notes to auto-forward all of its incoming emails to the instance of Mercury that is running on my machine.) Thanks again.
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 ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft