💾 Archived View for aphrack.org › issues › phrack30 › 7.gmi captured on 2021-12-04 at 18:04:22. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-12-03)
-=-=-=-=-=-=-
==Phrack Inc.=
Volume Three, Issue 30, File #7 of 12
=-------------------=
VAX/VMS Fake Mail
by Jack T. Tab
=-------------------=
In the August 1986 issue of VAX PROFESSIONAL, the BASIC subroutine that appears
at the end of this text was published. It was not until more than two years
later that DEC included a callable mail interface with VMS 5.x. While the
official version is much more extensive, the routine included here has one
important feature. The ability to have a mail message appear to be from
someone else is a good addition to most "toolkits."
VMS Mail works in two manners. The first is the familiar interactive. The
second is as a network object. In this method, MAIL is invoked by the
NETSERVER.COM command procedure in response to an incoming connect request.
MAIL.EXE is activated as network object 27. The other network objects can be
viewed by using the NCP command SHOW KNOWN OBJECTS. In this mode, MAIL.EXE
operates as a slave process, receiving instructions from the master process.
The master, in most cases, is another process running MAIL.EXE interactively.
The slave process can handle requests to deliver mail to as many recipients as
necessary. Addresses that are not on the same node as the slave process are
forwarded by activating yet another slave process on the target node. The
information sent by the master MAIL to the slave MAIL is quite simple and
straightforward, consisting of a series of strings.
The first string is for the FROM name. This is what makes the subroutine
useful, as it can be anything (i.e. the_Easter_Bunny). The next set of strings
are to whom the mail is to be sent. One address per string, with a null
string, chr(0), terminating the list. The third item is what the receiver(s)
sees in their TO: field. This also can be anything. VMS MAIL can use this
option for its .DIS distribution lists. The final information is the body of
the message. It too is terminated by another null string. The subject of the
mail message is taken from the first line of this text.
The MAIL slave will send back appropriate status messages indicating problems
if they occur. Such as "Addressee Unknown" or VMS and DECnet errors like "Disk
Quota Exceeded" or "Remote Node Not Reachable").
The only privilege that seems necessary is NETMBX. Without it the subroutine
cannot call MAIL as a network object. Our beloved system management resolved
the problem of people pretending to be SYSTEM by installing MAIL with NETMBX
and removing the priv from the student accounts. The subroutine works just as
well with JNET and BITNET as it does with DECNET addresses.