🚀 go-pugleaf

Hi all,

I read this list on a utility that currently has ~300 postings stored,
so I have done *some* checking, and I see questions about using MX over
specific TCP/IP packages, and I noted the following reply from Matt -

        >What tcp/ip packages does the current version of MX support?
               :
               :
    DEC VMS/ULTRIX Connection V1.2 and later
       (as of V2.0 called TCP/IP Services for VMS)
               :
               :

         -Matt

At our site, we are abandoning the recently abandoned CMU-Tek, with which
we successfully used MX 3.0 for more than a year.  Now we are on UCX 2.0
(CSLG license).  For the sole reason that we have published user manuals and
done training using MX, we do not want to abandon it as our VMS system mailer.

UCX, as of 2.0, ships with an SMTP<-->VAXMail interface, and unless someone can
warn me of a hidden hell with UCX' SMTP mail, the manuals/training thing
will remain the only reason.

Can someone answer:

* Do I have to use the MX SMTP server? Can't MX communicate with the UCX
  SMTP server?

* To test it, do I have to install from scratch? The MX CONFIG programs don't
  seem able to give me a working MX that will fly with UCX.

(NB: I *have* been trying different things, testing, and RTFMing.  I'm
not supplying excessive detail because I'm just looking for general
advice and/or warnings.)


From reading the docs, it seems to me that there should be a way to
just have MX handle the VMSMail interface, and let SMTP service, routing,
et al., be handled by UCX, but am I wrong?

This is not only for the sake of a few manuals, but also
compatibility with other University systems, so I can't exactly
just drop MX.

Any thoughts appreciated.
---------------------------------------------------------------------
Anthony Rzepela    <rzepela@cvi.hahnemann.edu>