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

Mercury NDS problem [Re: New User Having Trouble Setting Up Mercury]

Last post 07-03-2009, 18:54 by Thomas R. Stephenson. 1 replies.
Sort Posts: Previous Next
  •  07-03-2009, 14:16

    Mercury NDS problem [Re: New User Having Trouble Setting Up Mercury]

    Dear Sirs,

    Please help us solve the problem. We have installed Novell 6.5, Mercuri 1.48.     NDS mode. And we have a problem. We cannot make postmaster receive messages about errors. For example, if mail comes to a user who is not registered in Novell, Mercury  sends an answer to the author of the message about the error, but postmaster doesn’t get a message about it. This is my Mercury.ini

     

    #  MERCURY.INI generated by Mercury Setup
    #
    #
    #  Sample MERCURY.INI file for Mercury in NetWare 4.1 NDS mode.
    #  This version of the file 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.EXE 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.
    #

    [General]
    myname:      ukrnew.gov.ua   # Canonical name for this server
    timezone:    +0200   # Time Zone to add to date fields
    file_api:    1                    # Use the file api instead of queues
    mailqueue:   MAILN/SYS:SMTPMAIL      # Where mail should be put for delivery
    smtpqueue:   MAILN/SYS:SMTPMAIL      # Where the SMTP client should look for mail
                                      # note: smtpqueue and mailqueue can be the same

    [Mercury]
    failfile:     MAILN/SYS:SYSTEM/MERCURY/FAILURE.MER  # Delivery failure notification template
    confirmfile:  MAILN/SYS:SYSTEM/MERCURY/CONFIRM.MER  # Delivery confirmation template
    aliasfile:    MAILN/SYS:SYSTEM/MERCURY/ALIAS.MER    # System-wide alias file
    synfile:      MAILN/SYS:SYSTEM/MERCURY/SYNONYM.MER  # User synonym database
    listfile:     MAILN/SYS:SYSTEM/MERCURY/LISTS.MER    # List of lists
    logfile:      MAILN/SYS:SYSTEM/MERCURY/MERCURY.LOG  # Traffic logging file
    bitnethost:   cunyvm.cuny.edu      # Relay host for ".bitnet" rewrites
    poll:         10                   # Seconds between queue polling cycles
    scratch:      MAILN/SYS:SYSTEM/MERCURY   # Where we can write temp files
    switch:       2                    # number of ms to yield per op on heavy I/O
    returnlines:  15                   # How many lines of failed messages to return
    postmaster:   pm.ugen     # 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
    automaintenance : 1
    ldap_synonyms : 1
    decode_rfc1522 : 1                 # Decode RFC1522-encoded strings in broadcasts
    requeue_interval : 60              # Number of minutes between delivery retries
    max_retries : 48                   # Maximum number of delivery retry attempts
    # noticeboards: MAILN/SYS:PUBLIC/NB        # Where to find Pegasus Mail noticeboards
    # NDS_Reauthenticate : 1            # Work around NDS connection loss problems
    # gullible : 1                       # Do not perform strict address validation

    #  NetWare 4.x/5.x NDS mode user information
    #
    #  The [NDS] Section of MERCURY.INI is only used in NetWare NDS mode. It
    #  can be omitted in many cases, since Mercury will prompt for the values
    #  set in the section if they are absent.
    #
    #  Under NetWare 4.x and later, Mercury has to login to Directory Services
    #  as a user object. The account Mercury uses must have sufficient privilege
    #  to perform the following tasks:
    #
    #     * Scan, Create, Read, Rename and Delete files in every
    #       user's new mailbox directory
    #     * Read the "home directory" attribute for every mail user
    #       to which it might be called upon to deliver mail
    #     * Search the NDS tree (i.e, have Browse and Read rights) in
    #       all contexts in which it might operate
    #     * Read all members of any group to which it may be called
    #       upon to deliver mail
    #     * If running in automaintenance mode, it must be able to add
    #       and delete NDS attributes for any user to which it may
    #       deliver mail, and create and delete ACLs on any mail user's
    #       "home directory" NDS attribute.
    #
    #  If you omit the "password" field, Mercury will prompt for it at
    #  startup time.
    #
    #  Note that you must enter the Mercury User ID as an NDS name expressed
    #  RELATIVE TO THE ROOT OF YOUR NDS TREE - there is no default context.
    #
    #  Two other options affecting NDS-mode operation are also available in
    #  other sections of MERCURY.INI:
    #
    #  In the [General] Section:
    #  "Mailbox_Mode", value 0 or 1, default 0. If 0, Mercury will use the
    #     new mailbox directory structure created by MAKEMBOX and PMUSER. If
    #     1, Mercury will assume that you have loaded the NetWare 4.1 MHS
    #     Services product and will deliver to the mailbox structure created
    #     by that system. NOTE: this does NOT mean that Mercury will act as
    #     an MHS<-->SMTP gateway - it will NOT. It simply controls where it
    #     will place incoming mail.
    #
    #  In the [Mercury] section:
    #  "Automaintenance", value 1 or 0: if non-zero, Mercury will automatically
    #     create new mail directories for users when it detects that they need
    #     them, using the same logic as the PMUSER NLM. If 0, sending mail to
    #     a user with no new mail directory currently created will result in
    #     an error.

    # [NDS]
    # UserID      :  Admin.pmail
    # Password : xxxx

    [MercuryC]
    host:        10.95.1.10     # mail mail host which relays for us
    scratch:     MAILN/SYS:SYSTEM/MERCURY   # Where we can write temp files
    poll:        30                   # Seconds between queue polling cycles
    switch:      2                    # number of ms to yield per op on heavy I/O
    returnlines: 15                   # How many lines of failed messages to return
    failfile:    MAILN/SYS:SYSTEM/MERCURY/FAILURE.MER  # Delivery failure template
    max_retries: 72                   # Maximum number of delivery retry attempts
    esmtp:       1                    # Yes, we want to use ESMTP extensions
    # session_logging : SYS:SYSTEM/MERCURY/LOG


    [MercuryS]
    switch:      2
    debug:       1                    # Whether or not to show session progress
    relay:        0                   # We do not permit non-local mail relaying
    # strict_relay: 1                 # Turns on strict relaying controls
    # allow:       xxx.xxx.xxx.2        # A machine we WILL permit to connect
    # refuse:      xxx.xxx.xxx.0        # A group of machines we WON'T permit.
    # logfile:     MAILN/SYS:SYSTEM/MERCURY/MERCURYS.LOG
    # size:        1500000            # Maximum message size to accept
    # session_logging : SYS:SYSTEM/MERCURY/LOG
    # killfile:     SYS:SYSTEM/MERCURY/MERCURYS.KFL  # Never accept mail from here
    # smtp_auth:    1                 # Turn on authenticated SMTP support
    # auth_file:    sys:system/mercury/auth.mer  # Username/Password file for AUTH


    [MercuryP]
    scratch              :     MAILN/SYS:SYSTEM/MERCURY
    switch               :     2
    timeout              :     180
    # logfile            :     MAILN/SYS:SYSTEM/MERCURY/MERCURYP.LOG
    # allow:       xxx.xxx.xxx.2        # A machine we WILL permit to connect
    # refuse:      xxx.xxx.xxx.0        # A group of machines we WON'T permit.


    #  Using NetWare Groups: Mercury can deliver to NetWare Groups on your
    #  file server, but will only do so for groups that are defined in the
    #  "[Groups]" section. To enable a group for mail delivery, place its
    #  Internet name on the left-hand side of a [Groups] entry and the full
    #  NDS name of the group relative to the root of the NDS tree on the
    #  right-hand side.

    # [Groups]
    # testgroup            :     Test_group.pmail


    #  Defining domains for NetWare 4.1:
    #  Mercury can service an unlimited number of NDS contexts on your
    #  network, provided the NDS usercode you provide it with has sufficient
    #  privilege to be able to access all mail users in those contexts. Each
    #  context may have its own domain name, and it is possible to have a
    #  domain name which applies to all organizational units in and below a
    #  given context.
    #
    #  The [Domains] syntax for NetWare 4.1 is simply an NDS context on the
    #  left hand side, and the domain name by which it is known to Internet
    #  hosts on the right hand side. You may have multiple domain names for
    #  the same context, but at this stage you may not have multiple contexts
    #  with a single domain name. If you want a domain definition to apply
    #  to all organizational units (contexts) below the specified context as
    #  well as that context, prefix the context name with a '/' character -
    #  so the entry:
    #
    #       /dev.pmail  : dev.pmail.gen.nz
    #
    #  indicates that the Internet domain "dev.pmail.gen.nz" applies to the
    #  context "dev.pmail", and to any context below it in the NDS tree.

    [Domains]
    # Context                Domain name
    /[Root]   :     ukr.gov.ua


    [Maiser]
    Maiser               :     Maiser
    Helpfile             :     MAILN/SYS:SYSTEM/MERCURY/MAISER.HLP
    Lookupfile           :     MAILN/SYS:SYSTEM/MERCURY/MAISER.LKP
    Send_dir             :     MAILN/SYS:SYSTEM/MERCURY/SENDABLE
    Logfile              :     MAILN/SYS:SYSTEM/MERCURY/MAISER.LOG
    Notify               :     MAILN/SYS:SYSTEM/MERCURY/TMP
    Local_only           :     Y


    # The following section contains settings for the Mercury PH server,
    # MERCURYH.NLM. The principal item in this section is the "Addressbook"
    # keyword, which should reference the .PMR file of the Pegasus Mail
    # addressbook from which MercuryH should service requests.

    [MercuryH]
    # addressbook        :     sys:system/mercury/ph.pmr
    Administrator      :     postmaster@ukrnew.gov.ua
    Port               :     105

  •  07-03-2009, 18:54

    Re: Mercury NDS problem [Re: New User Having Trouble Setting Up Mercury]

    Please help us solve the problem. We have installed Novell 6.5, Mercuri 1.48.  NDS mode. And we have a problem. We cannot make postmaster receive messages about errors. For example, if mail comes to a user who is not registered in Novell, Mercury  sends an answer to the author of the message about the error, but postmaster doesn’t get a message about it.

    First of all a warning, I do not do NDS, only binary.  If mail is rejected by MercuryS then postmaster will only know about it by viewing the MercuryS logs.  If the mail gets to core then the way you are setup postmaster is also supposed to be notified but I would have to verify that mail to the postmaster@ukrnew.gov.ua is actually received.  I tried send to the postmaster@ukrnew.gov.ua address but the DNS said the domain was invalid.  Are you providing real data?

     

     


    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