Pegasus Mail & Mercury

Welcome to the Community for Pegasus Mail and
The Mercury Mail Transport System, the Internet's longest-serving PC e-mail system!
Welcome to Pegasus Mail & Mercury Sign in | Join | Help
in
Home Blogs Forums Downloads Pegasus Mail Overview Mercury Overview Wiki

selected protocol module

Last post 05-05-2009, 18:29 by Thomas R. Stephenson. 3 replies.
Sort Posts: Previous Next
  •  05-05-2009, 16:51

    selected protocol module

    Hi everyone :-)

     

    I have selected protocol modules : mercuryS, mercuryP, mercuryE, mercuryD

    then restart the mercury, and restart the server machine as well

    but why mercuryE and mercuryD can't be loaded ???

    please advice

     

    Thanks

  •  05-05-2009, 17:10

    Re: selected protocol module

    but why mercuryE and mercuryD can't be loaded ???
    No idea but if you were to provide your mercury.ini file we might be able to help.

    Thomas R. Stephenson
    San Jose, California
    Member of Pegasus Mail Support Team

    I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.
  •  05-05-2009, 17:34

    Re: selected protocol module

    hi Thomas :-)

     

    here is my mercury.ini file

     

    [General]
    myname: mail.mydns.co.id. # 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 # Where to find the users' WinPMail mailboxes.

    [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
    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: D:\MERCURY\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

    [Domains]
    bima: bima
    bima: mail.mydns.co.id
    bima: 202.93.33.182

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

    [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

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

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

    please advice

    Thanks

  •  05-05-2009, 18:29

    Re: selected protocol module

    Really strange, you do not have over half of the sections in the normal mercury.ini file.  Try just adding the following to this file and see what happens.

    [MercuryC]
    Host :
    Failfile : C:\MERCURY\Mercury\FAILURE.MER
    Poll : 30
    Scratch : C:\MERCURY\Mercury
    ReturnLines : 15
    Timeout : 300
    ESMTP : 1
    Server_Port : 587
    SMTP_Username:
    SMTP_Password:
    SMTP_ConnFlags : 4
    POP3_Auth : 0
    Logfile : c:\mercury\logs\mercuryc\MercuryC.log
    Log_Verbose : 0
    Session_logging : c:\mercury\logs\mercuryc
    Session_logmode : 1

    [MercuryE]
    Poll : 15
    Timeout : 60

    [MercuryD]
    Scratch : C:\MERCURY\scratch
    Timeout : 300
    Poll : 100

    [MercuryS]
    Debug : 1
    Logfile : C:\MERCURY\Logs\MERCURYS\mercuryS.LOG
    Timeout : 300
    Relay : 0
    Strict_Relay : 1
    Alt_Server_Port : 587
    Allow_Illegals : 0
    SMTP_Authentication : 1
    Auth_File : c:\mercury\pass.txt
    Session_logging : c:\mercury\logs\mercurys
    Session_logmode : 1
    Compliance_Settings : 0
    Maximum_Failed_Rcpts : 4
    Max_Relay_Attempts : 4
    SSL_Mode : 0
    ST_Blacklisting : 0
    No_VRFY : 0
    SMTP_ConnFlags : 0

    You will have to go through and reconfigure all of the protocols but this may not work even then.  If it does not then you will have to re-install as new over the current program to get a valid mercury.ini file.  You might though want to check the mercury.bak and mercury.bk1 files to see if these are good mercury.ini files . 

     


    Thomas R. Stephenson
    San Jose, California
    Member of Pegasus Mail Support Team

    I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.
View as RSS news feed in XML

Contact | Advertise | Host provider: PraktIT | Terms of Use | Privacy Statement
Copyright © 2007-2010 David Harris / Peter Strömblad. | Pegasus Mail Home Page