22 Feb
2016
22 Feb
'16
3:12 p.m.
I have been working to get my MicroVAX 3100 communicating with TCPIP, and I
got pretty far but I ran into a little snag. I don't have it on right
now, but anyone wanted to connect for fun it's available from
microvax3100.vintagecomputer.net, just give me a few minutes to fire it up.
I can telnet in/out and I can send SMTP messages, but I cannot yet receive
them (reply to). The issue is with the format of the email address.
I was wondering if I must send emails from my VMS 5.5 and multinet 4.1 as
such:
MAIL> MAIL
To: SMTP%"bill at myemail.com"
etc..
Is there a way instead to send like this:
MAIL> MAIL
To: bill at myemail.com"
Question #2
I'd like to be able to send messages to my MicroVAX (reply to messages).
At present if I try to send a message to SYSTEM at microvax3100@
vintagecomputer.net I get a rejection from the POSTMASTER like this:
Bad address -- <SYSTEM>
Error --
%MAIL-E-USERSPEC, invalid user specification ':'
-------------
I have been reading up and I have narrowed the issue down to the
differences between DEC mail format and "modern UNIX". I don't believe
anything is being blocked. I am sure if I sent an email from a VAX to my
VAX it would work just fine. I am also guessing there is a translation
gateway that I need to set as part of the boot up process, and that this is
a DECnet issue, not a Multinet issue. I was playing around with
*@MULTINET:MR_CONFIGURE
*but I am unsure if that's the correct process, or how to store this so
it's permanently set.
http://crpppc19.epfl.ch/vms/multinet/html/admin_guide/Ch08.htm#E15E104
Anyone have any tips? I don't want to upgrade the system unless I have to.
If I find the answer on my own I will post it here.
--
@ BillDeg:
Web: vintagecomputer.net
Twitter: @billdeg <https://twitter.com/billdeg>
Youtube: @billdeg <https://www.youtube.com/user/billdeg>
Unauthorized Bio <http://www.vintagecomputer.net/readme.cfm>
22 Feb
22 Feb
3:59 p.m.
I can telnet in/out and I can send SMTP messages, but I cannot yet receive
them (reply to). The issue is with the format of the email address.
I was wondering if I must send emails from my VMS 5.5 and multinet 4.1 as
such:
MAIL> MAIL
To: SMTP%"bill at myemail.com"
etc..
Is there a way instead to send like this:
MAIL> MAIL
To: bill at myemail.com"
I think being able to that (without the trailing doublequote) came in with
VMS MAIL in V7.something.
If you install PMDF (which also has a hobbyist licence), you get the PMDF MAIL
client which can do this and can also do MIME attachments and is generally a
lot more capable than VMS MAIL.
Question #2
I'd like to be able to send messages to my MicroVAX (reply to messages).
At present if I try to send a message to SYSTEM at microvax3100@
vintagecomputer.net I get a rejection from the POSTMASTER like this:
Bad address -- <SYSTEM>
Error --
%MAIL-E-USERSPEC, invalid user specification ':'
-------------
PMDF can probably help you here too as it is vastly more capable than Multinet
SMTP. However, there is also a lot to learn.
I have been reading up and I have narrowed the issue down to the
differences between DEC mail format and "modern UNIX". I don't believe
anything is being blocked. I am sure if I sent an email from a VAX to my
VAX it would work just fine. I am also guessing there is a translation
gateway that I need to set as part of the boot up process, and that this is
a DECnet issue, not a Multinet issue. I was playing around with
*@MULTINET:MR_CONFIGURE
*but I am unsure if that's the correct process, or how to store this so
it's permanently set.
http://crpppc19.epfl.ch/vms/multinet/html/admin_guide/Ch08.htm#E15E104
Anyone have any tips? I don't want to upgrade the system unless I have to.
If I find the answer on my own I will post it here.
I'm not quite sure whether SYSTEM at microvax3100(a)vintagecomputer.net is really
what you need here. Maybe SYSTEM%microvax3100 at vintagecomputer.net would work,
assuming the mail server for vintagecomputer.net is configured to know how
to route mail for a mail domain called microvax3100.
Also, bear in mind that many mail servers may be configured to reject mails
with convoluted routing such as this as spammers often found ways to abuse it.
Regards,
Peter Coghlan.
23 Feb
23 Feb
3:50 a.m.
I'm not quite sure whether SYSTEM at microvax3100(a)vintagecomputer.net is
really
what you need here. Maybe SYSTEM%microvax3100 at
vintagecomputer.net would
work,
assuming the mail server for vintagecomputer.net is
configured to know how
to route mail for a mail domain called microvax3100.
Also, bear in mind that many mail servers may be configured to reject
mails
with convoluted routing such as this as spammers often
found ways to
abuse it.
Regards,
Peter Coghlan.
Thanks for your reply. My error I meant send email to
system at microvax3100.vintagecomputer.net
If the older version of vms and multinet have these limits then so be it.
I found only newer docs for Multinet to use. Whoever owned this machine
before me must have used for local mail and some sort of development or
computer support work before open Internet emailing. I have to pull the
battery, etc. and stabilize the system but I prefer to keep everything
as-was and not upgrade the services. I only changed the networking values
so I could do comms.
Bill
5:15 a.m.
Thanks for your reply. My error I meant send email to
system at microvax3100.vintagecomputer.net
Multinet is an excellent TCP/IP stack but the SMTP server included with it
is a bit limited and V4.1 is old. If you allow it to accept SMTP mail directly
from the internet, it may be difficult or impossible to
secure it against
exploitation as a spam relay which would cause lots of problems
for others
as well as yourself.
Having said that, it should be possible to feed mail to it from a more capable
internet facing SMTP mail server or set it up to send/receive SMTP mail on your
internal network only.
To do this, you don't need the DECnet to SMTP mail gateway you mentioned. If
this was configured on your machine, it may have been used to allow the machine
running Multinet SMTP to accept mail from the internet and pass it on to other
DECnet connected machines which did not run SMTP.
I don't know what MULTINET:MR_CONFIGURE.COM is but "MR" suggests it might
be
something to do with ALL-IN-1 mail rather than VMS MAIL. If you want to run
ALL-IN-1 mail, this is very different to using VMS MAIL.
Everything you need to route SMTP mail to/from VMS MAIL on your machine should
be provided by:
$ MULTINET CONFIGURE /MAIL
Regards,
Peter Coghlan.
7:08 a.m.
On Tue, Feb 23, 2016 at 8:15 AM, Peter Coghlan <cctalk at beyondthepale.ie>
wrote:
Peter,
I won't be leaving this box up perpetually for sure. I have a 4000-200
with a newer version of MULTINET and VMS that allows a person to send and
receive mail with "normal" email addresses but even that one is only left
running occasionally. I watch attempts every few minutes to probe it from
the outside world, sheesh, bots.
Thanks for your reply. My error I meant send email to
system at microvax3100.vintagecomputer.net
Multinet is an excellent TCP/IP stack but the SMTP server included with it
is a bit limited and V4.1 is old. If you allow it to accept SMTP mail
directly
from the internet, it may be difficult or impossible to secure it against
exploitation as a spam relay which would cause lots of problems for others
as well as yourself.
Having said that, it should be possible to feed mail to it from a more
capable
internet facing SMTP mail server or set it up to send/receive SMTP mail on
your
internal network only.
To do this, you don't need the DECnet to SMTP mail gateway you mentioned.
If
this was configured on your machine, it may have been used to allow the
machine
running Multinet SMTP to accept mail from the internet and pass it on to
other
DECnet connected machines which did not run SMTP.
I don't know what MULTINET:MR_CONFIGURE.COM is but "MR" suggests it might
be
something to do with ALL-IN-1 mail rather than VMS MAIL. If you want to
run
ALL-IN-1 mail, this is very different to using VMS MAIL.
Everything you need to route SMTP mail to/from VMS MAIL on your machine
should
be provided by:
$ MULTINET CONFIGURE /MAIL
Regards,
Peter Coghlan.
MULTINET CONFIG /MAIL
This is what I use to compare the mVax3100 and my 4000-200. I could not
find anything other than the versions of the services to explain why one
could not use simpler email addressing (bill at emaildomain.com).
Basically, the 3100 with it's older multinet and VMS "works as designed"
which for now is fine with me. I just wanted to be sure I did not need to
perform a trick everyone but me knows about to streamline email, other than
simply upgrade these services.
Thanks again for your reply.
Bill
--
@ BillDeg:
Web: vintagecomputer.net
Twitter: @billdeg <https://twitter.com/billdeg>
Youtube: @billdeg <https://www.youtube.com/user/billdeg>
Unauthorized Bio <http://www.vintagecomputer.net/readme.cfm>
3178
days inactive
3179
days old
4 comments
2 participants
participants (2)
-
billdegnan＠gmail.com -
cctalk＠beyondthepale.ie