🚀 go-pugleaf

Yeah, I know.  People have been leaning on me for nearly a year to move from
v4.0 to v4.1.  Well, finally the v4.0 -only homebrew channel we'd been using to
support All-in-1 is no longer required (our few All-in-1 users have chosen to
look at not using All-in-1 for Email), and we can move to v4.1 with impunity.

Running VMS v5.5-2, Multinet v3.0 Rev H (soon to install v3.2), Jnet v3.5.

We have v4.1-10 in hand to install.

(1) Any compatibility problems with using the current PMDF v4.0 SMTP handler
        if we move to Multinet v3.2 before I get PMDF v4.1 installed? (Note:
        DIFFERENT staff are responsible for installations here -- I have PMDF
        and JNET, another has Multinet and VMS; out installation might not be
        compatible).

(2) Any compatibility problems with using the PMDF v4.1-10 SMTP handler as
        linked in the install kit with Multinet v3.2?  Just relink?  Higher
        PMDF patch release?

(3) Any need for a higher patch release of PMDF v4.1?  What's the current
        revision and where is a list of the fixes that current revision
        supplies?

(4) How close am I to v4.2?  Is moving to v4.1 advisable with v4.2 just around
        the corner?

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services         AT&T:(814) 865-1818 FAX:(814)863-3560  |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+