[Info-vax] REPLY/ALL in VMS Mail client ?

Phillip Helbig undress to reply helbig at asclothestro.multivax.de
Tue Dec 14 16:21:59 EST 2021


In article <61b900e3$0$706$14726298 at news.sunsite.dk>,
=?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne at vajhoej.dk> writes: 

> On 12/14/2021 3:20 PM, Simon Clubley wrote:
> > It's a pity that DEC/HPE never shipped a more modern command line
> > mail client as a standard part of VMS so that we could use that while
> > people like you who are happy with the current client could continue
> > to use that.
> 
> PMDF comes with an enhanced VT email client.

I have a bit of experience with PMDF, but not on my own cluster.  The 
usual VMS MAIL commands work exactly like they should.  Most people 
probably don't even notice PMDF underneath, except when they need some 
feature which vanilla MAIL doesn't have.

Also useful: a distribution list in TCPIP$SMTP_COMMON will be seen by 
TCPIP before VMS MAIL is reached and forward incoming messages to that 
list (which can be any valid email addresses).  When doing so, the SMTP 
headers stay intact (sometimes a problem when forwarding from within VMS 
MAIL).

An empty list silently sends stuff to the bit bucket.

MAIL> SET FORWARD/USER=foo bar at klim.bim or whatever can be used from a 
privileged account to set up forwarding for arbitrary users like foo.  
They don't have to be real users or valid VMS usernames.  The forwarding 
address can be a TCPIP address, a VMS MAIL address, a distribution list, 
whatever.  Useful for creating addresses one mus to enter somewhere so 
that one can see who sends email to that address.  When no longer 
needed, forward it to NL.DIS (which is just empty).

I'm not exaggerating when I say that I've never used another mail 
utility---and I've used several at work and so on---where I didn't miss 
many features of VMS MAIL (and the SMTP stuff in TCPIP on VMS).




More information about the Info-vax mailing list