<div class="ForumReplyToPostArea"> <blockquote><p>Beautiful,  Thank you.</p><p>I followed a tutorial on how to set the server up, it called for an ip address to be put in the interface fields.  I understand why now and why I don't need it.</p><p> Thank you very much for you support, I am amazed on how fast it was.</p></blockquote><p>Notice how quickly you got an answer when you posted the mercury.ini file?  I wish everyone asking Mercury setup type questions would always provide the host name, IP address and mercury.ini file.  ;-)</p><p> </p> </div>

<P>Hi all,</P> <P> I've decided to try out Mercury as for a mail system and I am very happy with it and would like to purchase a licence.  However after I restarted my server (windows 2008) I could not log into Mercury mail server via an outlook client.  Also any email I sent from gmail, hotmail etc get a bounce back saying that my server refused the connection.   If I delete the Mercury file folder and re-install everything works fine once again until a reboot.</P> <P> Has anyone else had this issue?  I've tried turning off windows firewall, opening all ports with no success, the only thing that seems to work is re-installing the server.  I've also created a session using WinPcap and from what I can tell is that the request is coming into my server but not making it to the mercury program.</P> <P> If any more info is required please ask.  As I said before I like this program and would like to purchase a licence but I need to be sure that I won't have to reinstall it everytime I have to reboot the server.</P> <P mce_keep="true"> </P> <P>Thank you.</P>

<p>Start with checking the logs for the server modules you use (MercuryS and either MercuryP or MercuryI) and see if the requests make it to Mercury at all.</p><p>Make sure the user that is running Mercury has full access to all Mercury directories, and that no other software (for instance realtime antivirus programs) interfere in any way.</p><p>/Rolf </p>

<p>In addition to what Rolf has told you how about providing the host name and IP address of the server and the mercury.ini file for analysis.  FWIW, I suspect the port calls are not even getting to Mercury. </p><blockquote><p> </p></blockquote>

<P>User has full access to C:\Mercury?  Yes Check the logs?    Nothing shows up in the logs at all.  The connection gets to my computer but not the mail server.</P> <P>my domain name is dcwebsolutions.ca 216.110.252.42 here is the ini file.  Thank you for the quick reply</P> <P mce_keep="true"> </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. #</P> <P>[General] myname:      dcwebsolutions.ca  # 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:\MERCURY\QUEUE   # Where mail should be put for delivery smtpqueue:   C:\MERCURY\QUEUE   # Where the SMTP client should look for mail newmail_path: C:\MERCURY\MAIL\~N</P> <P>[Protocols] C:\MERCURY\mercurys.dll C:\MERCURY\mercurye.dll C:\MERCURY\mercuryp.dll</P> <P> [Mercury] failfile:     C:\MERCURY\Mercury\FAILURE.MER  # Delivery failure notification template confirmfile:  C:\MERCURY\Mercury\CONFIRM.MER  # Delivery confirmation template aliasfile:    C:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file synfile:      C:\MERCURY\Mercury\SYNONYM.MER  # User synonym database listfile:     C:\MERCURY\Mercury\LISTS.MER    # List of lists logfile:      C:\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:      C:\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</P> <P>[MercuryC] logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log   # Traffic logging file Session_logging : C:\MERCURY\Sessions\MercuryC\    # Directory for session log files Session_logmode : 0 host:             # mail mail host which relays for us scratch:     C:\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:    C:\MERCURY\Mercury\FAILURE.MER  # Delivery failure template esmtp:       1                    # Yes, we want to use ESMTP extensions</P> <P>[MercuryE] HELO : dcwebsolutions.ca Session_logging : C:\MERCURY\Sessions\MercuryE Session_logmode : 0 Poll : 15 Timeout : 60 Logfile : C:\MERCURY\Logs\MercuryE\~y-~m-~d.log Log_Verbose : 0 DNS_Timeout : 20 DNS_Retries : 4 Transcripts : 1 MaxThreads : 10</P> <P>[MercuryD] Session_logging : C:\MERCURY\Sessions\MercuryD\    # Directory for session log files Session_logmode : 0 Scratch : C:\MERCURY\Scratch\MercuryD # Timeout : 30 # Poll : 120               # How often to check hosts for new mail (seconds)</P> <P>[MercuryS] Debug : 1 Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log Timeout : 30 Relay : 0 Strict_Relay : 0 Interface : dcwebsolutions.ca Allow_Illegals : 0 SMTP_Authentication : 0 Session_logging : C:\MERCURY\Sessions\MercuryS Session_logmode : 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:\MERCURY\Scratch\MercuryP Logfile : C:\MERCURY\Logs\MercuryP\~y-~m-~d.log Stack : 32768 Interface : dcwebsolutions.ca Mark_Read : 1 SSL_Mode : 0 Login_Disabled : 0 UIDL_nul_list : 1 New_UIDs : 1 No_NUL_passwords : 1 Session_logging : C:\MERCURY\Sessions\MercuryP Session_logmode : 0 Timeout : 60</P> <P>[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</P> <P># [Groups] # testgroup            :     TESTGRP</P> <P>[Domains] # NetWare Server           Domain name dcwebsolutions  :  dcwebsolutions dcwebsolutions  :  dcwebsolutions.ca</P> <P># [Rewrite] # *                    : pmail.gen.nz</P> <P>[Maiser] Maiser               :     Maiser Helpfile             :     C:\MERCURY\Mercury\MAISER.HLP Lookupfile           :     C:\MERCURY\Mercury\MAISER.LKP Send_dir             :     C:\MERCURY\Mercury\SENDABLE Logfile              :     C:\MERCURY\Logs\Maiser\~y-~m-~d.LOG Notify               :     C:\MERCURY\Mercury\TMP Local_only           :     Y</P> <P>[MercuryH] logfile : C:\MERCURY\Logs\MercuryH\~y-~m-~d.log   # Traffic logging file # 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:\MERCURY\Scratch\MercuryI logfile : C:\MERCURY\Logs\MercuryI\~y-~m-~d.log   # Traffic logging file Session_logging : C:\MERCURY\Sessions\MercuryI\   # Directory for session log files Session_logmode : 0 Timeout : 120 Server_Port : 143 Idle_Timeout : 1800</P> <P>[MercuryB] Scratch : C:\MERCURY\Scratch\MercuryB logfile : C:\MERCURY\Logs\MercuryB\~y-~m-~d.log   # Traffic logging file Session_logging : C:\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> <P mce_keep="true"> </P> <P mce_keep="true"> </P> <P mce_keep="true"> </P>

<p>This may sound like a silly question, but is Mercury actually running after you restart your server?</p><p>Have you installed it as a service? (either 'native' or via a wrapper)</p><p>Do you start it manually? </p>

Yes I installed it as a service but if my understanding is correct I can't use it as a service until I buy a licence for it.  Therefore after I restarted my computer I had to start mercury manually (using the mecury loader.exe file).  I am using WinPcap to see that the SMTP and POP3 packets are in fact being received by my computer but the modules on Mercury don't show any traffic at all.

<p>Check that the Mercury modules have the correct (or blank) network interface .. Aha!</p><p>[quote]</p><p>[MercuryS] Debug : 1 Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log Timeout : 30 Relay : 0 Strict_Relay : 0 <b>Interface : dcwebsolutions.ca</b> </p><p>[/quote]</p><p>Delete the '<b>dcwebsolutions.ca'</b>and it should go.</p><p>This should be EMPTY, or be the interface to listen on (see help).</p><p>[quote]</p><p>IP Interface to use  If your computer supports multiple IP interfaces, you can use this field to tell MercuryS which interface it should select when listening for connections: enter the interface as a dotted IP address in the general form www.xxx.yyy.zzz. As an example, your system may have one IP address assigned to a dialup PPP connection, and another, different IP address assigned to a local Ethernet network - you would enter here the interface MercuryS should use. If you leave this field blank, MercuryS will listen on all available interfaces. Unless you are *very* sure of what you are doing, or have been instructed by an ISP or network administrator, you should leave this field blank. If you change the IP interface in this field, you must restart Mercury before the new interface number will be used. [/quote] </p>

<P>Beautiful,  Thank you.</P> <P>I followed a tutorial on how to set the server up, it called for an ip address to be put in the interface fields.  I understand why now and why I don't need it.</P> <P> Thank you very much for you support, I am amazed on how fast it was.</P>