🚀 go-pugleaf

In article <1990Jul13.223745.24604@supernet.UUCP> cluther@supernet.UUCP (Clay Luther) writes:
>I recently obtained smail 3.17 as a solution for a certain problem we have
>at our site.  I had heard that smail allowed you to easily define new
>routers/transports, more so that sendmail.

You may want to pick up 3.18 somewhere.  It's on uunet as smail3.1.19.Z
(oddly enough).

>We have a host connected to us via tokenring.  We have a program, called xcmd,
>which performs the exact same function as uux except over tokenring.
>When mail is sent to this host, I want smail to use xcmd (with parameters)
>rather than uux.  There is only one host that smail would have to do this
>for.  The xcmd program *does* work.

Copy the config, router, and transport files from the samples/generic
directory in the smail distribution into your installed smail lib
directory.
  Make sure you have an entry in your paths file for this host that
  says:
      host host!%s   (I like to put all the uucp neighbors here as well
  to save running uuname to find them).

In the "pathalias" router entry, change the line:
   transport = uux
     to
   method = uucp
Create a directory called "methods" in the smail lib directory (or set
the name you want in the config file), and create a file named uucp
in this directory containing:
    hostname  xcmd
      *       uux
Now edit the "transports" file.  Duplicate the entire 5 or 6 line entry
describing the uux or demand transport, change the name to xcmd, and
change the "cmd" line to do whatever you need.

Test it with:
  smail -v200 -N hostname!user
...some input <EOT>
and watch the debug output for the lookup and generated command.
(The -N will prevent actual delivery).

Les Mikesell
  les@chinet.chi.il.us