info-vax@ucbvax.ARPA (03/15/85)
From: sasaki@harvard.ARPA (Marty Sasaki)
Let me clarify a few points about my recent flame about mail to non-VMS
systems from VMS.
o I don't care whether VMS mail uses SMTP or not. I would just
like to see a specification of the protocol used and some kind
of guarentee that the protocol will continue to be used at least
for a while. When the protocol does get changed, I want to know
how it is going to be changed.
o It is important (at least for us) to use VMS mail for many
users. The primary reason is that we can communicate with other
VMS systems using DECNET. Many of these other sites don't want
to support a different piece of mail software, but still want to
communicate with us and the outside world.
o The issue of software support is simple. I don't expect DEC to
provide support for my mailer. Nor do I expect DEC to support
their mailer if my mailer is feeding it. I just want to know
what the protocol is. I'll write my own software (or buy it) and
take my chances.
o I'm thrilled that DEC knows this is a problem. The solution is a
simple one, let people know what the protocols are. DEC must
have internal documentation about how all of this is supposed to
work, the RSX guys need to know how to talk to the VMS guys. I
would sign a non-disclosure for this information. I'm sure that
there are loads of others who would do the same.
I understand that DEC would have problems with this. But why not provide
something like the current print symbionts, only for mail? (The symbiont
allows the substitution for parts of the normal symbiont with user
code.)
As I've said before, I don't think that my position is all that unique.
The volume of personal mail that I've received confirms my feelings.
Come on DEC, let us know what is going on.
--------------------------------------------------------------------------
Marty Sasaki net: sasaki@harvard.{arpa,uucp}
Havard University Science Center phone: 617-495-1270
One Oxford Street
Cambridge, MA 02138