🚀 go-pugleaf

>Don't use a dn_ channel, that will not run the correct channel program.  You
>need to use a "d" or "d_" channel for this.  A "d" channel is normally used to
>support DECnet MAIL-11 for remote DECnet nodes that do not have PMDF.  It turns
>out that PMDF supports remote DECnet MAIL-11 nodes simply by handing the
>message
>to VMS MAIL, which makes the network connection and does the transfer.  If
>the address has no remote node then this devolves to being the same as a local
>VMS MAIL delivery -- hence the use of a "d" channel for alternate local
>delivery.

>If you are already using a "d" channel and you don't want its configuration to
>change for this purpose, go ahead and create a "d_headers" or something channel
>(everything after the "d_" can be whatever you like).

Okay, this is close, but when trying this I see that the "d" channels parse
the user@host format in its entirety interpreting the host as a decnet node
name, while the "l" channel will strip off the "@host" portion.  What is
the best way to set up the rewrite rules in our homogeneous cluster (which
shares the PMDF configuration) to get the decnet hostname to work properly.
I'd prefer not to write a rule for each node to get it to work out
properly.

May I also suggest adding support for multiple "l" channels...

Thanks,
Joel D. Kraft
System Manager
Buena Vista College