[Info-vax] Use of logical names other than I/O redirection

[alanfe...@gmail.com]

On Monday, September 12, 2022 at 4:40:49 PM UTC-4, Stephen Hoffman wrote:
> On 2022-09-12 18:18:09 +0000, alanfe... at gmail.com said: 
> 
> > You can use logical names for recipients!

[...]

> > I don't know if this is a true story, but someone did a$ DEFINE MORON
> > <user-address> 
> > And when the person received it, it should that it was sent to MORON!
> You can do that with pretty much any mail tool, or with DNS translations, etc.
> > I suppose that's harmless enough for personal use. I suppose one could 
> > make "public" logical names for positions like systems administrator, 
> > or HR Head, who might change from time to time.
> Easier to use a forwarding entry in the database for forwarding 
> arriving OpenVMS MAIL to a fixed address (and SYSTEM, FIELD, etc., are 
> routinely forwarded on systems I have administered), but there are 
> limits. OpenVMS MAIL doesn't like multiple forwarders. Forwarding to a 
> forwarding server does work, as a workaround. 

The MORON bit was an unintentional thing. The sender didn't know it would appear as "To: MORON" to the recipient. The sender must have assumed that MAIL would show the recipient the translation, not the actual logical name.

> 
> MAIL really doesn't work all that well by current standards. When open 
> and unsecured network connections are still permissible, MAIL does 
> provides a way to send logs and notifications. Though there are other 
> and more secure paths for that. I've used php and other tools to make 
> secure connections, where the target SMTP is operating with modern 
> settings and where security exceptions are discouraged. 

The only time I use VMS MAIL is on EISNER, and it's always initiating by the system manager. I'm just curious about how people here feel about logical names, other than I/O direction.

[...]
> Pure Personal Opinion | HoffmanLabs LLC

Alan