# # Sample 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.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: rzi.ngate.uni-regensburg.de # Canonical name for this ser ver timezone: +0100 # Time Zone to add to date fields mailqueue: MAILQUEUE # Queue: where mail is submitted by PMail smtpqueue: MAILQUEUE # Queue: where outgoing mail should be placed # note: smtpqueue and mailqueue can be the # same # To use Mercury 1.11`s spooler directory submission mechanism instead of # the queue-based system, you would comment out the section above and # uncomment the section shown below: # # [General] # myname: urania.pmail.gen.nz # Canonical name for this ser ver # timezone: +1100 # Time Zone to add to date fields # file_api: 1 # Use a spool directory instead of queues # mailqueue: SYS:SMTPMAIL # Path: where mail is submitted by PMail # smtpqueue: SYS:SMTPMAIL # Path: where outgoing mail should be placed [Mercury] failfile: SYS:SYSTEM/MERCURY/FAILURE.MER
# Delivery failure notification tem plate confirmfile: SYS:SYSTEM/MERCURY/CONFIRM.MER
# Delivery confirmation template aliasfile: SYS:SYSTEM/MERCURY/ALIAS.MER # System-wide alias file synfile: SYS:SYSTEM/MERCURY/SYNONYM.MER # User synonym database listfile: SYS:SYSTEM/MERCURY/LISTS.MER # List of lists logfile: SYS:SYSTEM/MERCURY/MERCURY.LOG # Traffic logging file #bitnethost: rrzs1.rz.uni-regensburg.de
# Relay host for ".bitnet" rewrites poll: 10 # Seconds between queue polling cycles scratch: 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: SUPERVISOR swapids: 1 GULLIBLE: 1 [MercuryC] host: 132.199.3.13 # mail mail host which relays for us scratch: 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: SYS:SYSTEM/MERCURY/FAILURE.MER
# Delivery failure template [MercuryS] switch: 2 debug: 1 # Whether or not to show session pro gress discard: 100000 # Max. number lines to allow in a mes sage [MercuryP] scratch: SYS:SYSTEM/MERCURY switch: 2 [Groups] # Alias for group Actual NetWare group name everyone : MAILUSERS [Domains] # NetWare Server Domain name rzi : rzi rzi : rzi.ngate.uni-regensburg.de rzi : rzi.rz.uni-regensburg.de rzi : rzi.uni-regensburg.de [Maiser] Maiser : Maiser Helpfile : SYS:SYSTEM/MERCURY/MAISER.HLP Lookupfile : SYS:SYSTEM/MERCURY/MAISER.LKP Send_dir : SYS:SYSTEM/MERCURY/SENDABLE Logfile : SYS:SYSTEM/MERCURY/MAISER.LOG # Notify : SYS:SYSTEM/MERCURY/TMP # Local_only : Y [Rewrite] * : ngate.uni-regensburg.de
load mercury load mercurys load mercuryc
unload mercuryc unload mercurys unload mercury
; Sample alias file for Mercury. ; Copright (c) 1993, David Harris, All Rights Reserved. ; ; The format for this file is: ; ; alias == real_address ; ; Lines starting with ';`, '#` or '*` are considered comments ; and are ignored, as are blank lines. There may be trailing ; and leading whitespace on entries - it is all stripped out ; in the alias file. It is a limitation of this release of ; Mercury that you cannot have an alias or real address which ; contains '==` because no quoting mechanism is implemented. ; ; Compile the file using MALIAS.EXE, and copy it to the place ; you have specified in MERCURY.INI. You can update Mercury`s ; alias file while Mercury is running, although it is best to ; use PCONSOLE to stop servers from servicing jobs in the mail ; queue while you do so. ; ; You can have an almost unlimited number of aliases, and you ; may have them resolve to anything you wish. Aliases are ; resolved before any other attempt at address resolution is ; made, so it is perfectly legal to have a local-looking alias ; resolve to an off-server address. Note, though, that aliases ; work strictly on the ADDRESS - they are not affected by any ; quoted or comment text which is attached to it. As an example ; of the impact of this, the aliasing mechanism regards these ; two addresses as identical: ; ; "My what a funny day!" david@pmail.gen.nz ; (Master of the Lightbulbs) <david@pmail.gen.nz> "Pop!" ; ; Aliases may be applied recursively up to four levels deep - ; that is, you may have aliases for aliases in this file. ; (although it still eludes me why anyone would do this). ; ; Neither aliases nor real addresses are case-sensitive, ; although case is preserved in real addresses. D.Harris@pmail.gen.nz == David@pmail.gen.nz David_Harris@pmail.gen.nz == David@pmail.gen.nz D.Harris@urania.pmail.gen.nz == David@pmail.gen.nz David_Harris@urania.pmail.gen.nz == David@pmail.gen.nz G.Schwarz@rz.uni-regensburg.de == Schwarz@rzi.ngate.uni-regens burg.de Guenter_Schwarz@rz.uni-rbg.de == Schwarz@rzi.ngate.uni-regens burg.de
Table of Contents Next Chapter