Current version
The current release of Name Router is 4.1-8. Earlier versions of Name
Router may not work correctly with PMDF 5.2. To obtain further details
click here . To find out what version
you currently have click here.
Supported OpenVMS & PMDF Versions.
OpenVMS: V6.2 through V7.3
PMDF: V5.2 through V6.1-1.
Name Router 4.1 Software Product Description.
Name Router is a mail routing utility, which allows users to receive mail
using conceptual domain names, rather than machine node names. For example,
a user called John Smith, in the sales department of Scrooge accountants
in Ireland might have a mailbox called smithj@vax1.scrooge.ie. Name Router
allows him to be addressed as j.smith@sales.scrooge.ie.
Name Router maintains a database specifying the mappings from the conceptual
domain addresses to actual mailbox addresses, and will route incoming
messages to the former to the latter. Name Router will also allow abbreviated
fields within the conceptual name.
The full specification for a conceptual address is of the form
forename.middle.surname@domain1[.domain2. ..]
All but the surname field can be omitted or abbreviated. If ambiguity arises
from this, Name Router may be configured to do one of three things:
- Route to the first match.
- Reject the message as unrouteable.
- Send the originator a message listing the matching entries in the database.
For example, if john.will.smith@sales.scrooge.ie is entered in the database,
any of the following localparts will match this entry:
smith
j.smith
john.smith
john.w.smith
jo.smith
The following entries would NOT match:
joe.smith
john.k.smith
Any of the following domain parts would also match:
sales.scrooge.ie
scrooge.ie
ie
The following would not:
accounts.scrooge.ie
rival.ie
There must be a match in both localpart and domain for the mapping to take
place. Name Router is not case sensitive on any of the fields.
Name Router 4.1 has the following features:
- runs under OpenVMS VAX or OpenVMS AXP.
- Uses RFC-822 style domain addressing.
- optional rejection messages to sender and/or local postmaster
for unrouteable messages.
- optional default mapping, for handling unmatched addresses, e.g.
an unmatched entry could be mapped to
surname_forenameinitial@machine.domain, so
fred.jones, if not matched would go to jones_f@machine.domain.
- per-domain defaults whereby unmatched entries to specific domains
can be routed to specific destinations.
- optional return message to sender for ambiguous names, listing the
possible entries (up to a maximum of 10).
- User defined text which is included in all return messages.
- Can interface to the PMDF mail system, or can generate and
read BSMTP message files to/from specified directories.
- Optional organization name, which is automatically added to
all entries.
- Database build program, which inputs mappings in text form into
indexed file.
- Test program to check mapping tables.
- Generates reverse mapping tables compatible with PMDF REVERSE.DAT
facility, allowing originator fields to be set to the sender's
conceptual address.
- Entries may be marked as direction specific, so they will appear
in either the routing or reverse databases only.
- Routing algorithm may be enhanced by the user of user written
routines placed in a shareable image, and activated by Name Router.
- Name Router is installed using VMSINSTAL.
- Sources are included.
- Documentation in LaTeX source, Postscript and LN03 formats.
- Name Router may be freely distributed, subject to the
restrictions
listed.
Name Router is mainly written in FORTRAN, but a FORTRAN compiler is not
required unless you wish to modify or recompile.
No formal support is provided for Name Router at present, but I will answer any
queries, and try to fix any bugs. Suggested enhancements, criticisms and
small unmarked bills are also welcome.
Please read the conditions of use
here before downloading
Download Name Router
Download UNZIP for Alpha
Download UNZIP for IA64
Download UNZIP for VAX
Other TomWade Software