NI_NIFTP(8)

NAME
JNT Mail File Submission process

SYNOPSIS
ni_niftp Net File TSaddress

DESCRIPTION

Ni_niftp is invoked by a File Transfer Protocol server to interpret a JNT Mail File (see jntmail(8) ) sent to it. Ni_niftp queues the message using submit(8) and returns error messages relating to bad addresses in the JNT Mail file. Ni_niftp must be invoked with a privileged real uid (root, daemon, or mmdf).

File is the JNT Mail file to be submitted. Net is the network which the JNT Mail File has come from. A table niftp.nets must exist in the tailor file (see the MMDF installation document) which has legal values of net on the LHS and the associated MMDF channel on the RHS. An example tailor entry is:
MTBL  name="niftp.nets", file="niftp.nets",
        display="NIFTP net to channel map"
This indirection allows the NIFTP to have different channel nomenclature to MMDF, and gives a measure of security by preventing JNT Mail on spurious channels. TSaddress should correspond to the LHS of the associated channel table, but may be in reverse domain ordering (on the basis that many NIFTP implementations may only understand NRS ordering). This will be used in the message trace information. If it is not in the tables, it will be treated as a domain literal. Any "," or "*" characters in the string will be mapped to "?" for compatibility with submit(8).

The exit values of ni_niftp are standard mmdf exit values as defined in h/mmdf.h. RP_NDEL is given special significance, as a JNT Mail File with no valid destination address, where no return address could be determined. Ni_niftp will unlink the JNT Mail file, except in cases of permanent failure, when the file will be left to assist debugging.

FILES
<mmdflib>/ni_niftp
<mmdfsource>/h/mmdf.h

SEE ALSO
jntmail(8), york-inst(8), york-inst(8)