Tim Sneddon <tim at sneddon.id.au> writes:
but you might even be able to use: > > _MCP>
"<""{host}::{user}""@localhost>" > > ...but this might hork up replies.
For more elaborate schemes, MX is > capable of rewriting using *IX-style
regular expressions with /REGEX > on the 'DEFINE REWRITE_RULE' command.
Spot on.
;)
For the reverse (outgoing and replies), configure the DN_SMTP server
which is SMTP over DECnet. >
This is a part of MX that I don't know nearly as well as I should, but I
though you needed MX at both ends to make that work. Which would rule
out RSTS and RSX hosts.
They could forward to a VMS host or implement their own SMTP transport.
I use MX% and 'TCP/IP Services' SMTP% transport. If you define logicals
correctly, they can both coexist in harmony. Both 'TCPIP Services' POP
and IMAP require that the MAIL$INTERNET_TRANSPORT logical be defined as
SMTP and that the MX_PROTOCOL_PREFIX logical be defined as SMTP%.
MX has alias translation, mailing list features and other delivery >
agents such as X25, UUCP and a SITE interface. The latter allows a
X25 and UUCP have been dropped when MX became open source. SITE is
definitely still there. I've seend that used for lots of interesting
stuff. I'm pretty sure it was Ruslan Laishev that developed an SMS
gateway for MX.
Well, in the age of ubiquitous internet, there's probably little need
for either X25 and UUCP agents.
You've yanked out the MX licensing now that it's open-source?
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On Wed, 30 Jan 2013 09:20:43 -0500
"Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote:
Tim Sneddon <tim at sneddon.id.au> writes:
I have used MX at sites that receive quite a decent amount of mail
and have been quite impressed with the performance. Although, I'm
biased...
Yup! But it often times requires a bit of queue tuning. I didn't
want to open pandoras box by cluttering this discussion WRT that. ;)
Yeah, the chatter certainly has gone up lately. However, I must admit
I don't mind it so much as there is not the flaming that is so
prevalent on c.o.v.
Regards, Tim. MX Maintainer
Any new releases on the horizon and where is the current these days?
I still have V5.4 licensed from MadGoat.
This does drift a bit off topic...so I'll keep it brief, as I think
there may be some people that use MX on here. If you want more info,
then follow up with me off-list...
MX V6.1 is nearing release. MMK has been put into github and it has
been the test bed for developing VMS software using git (there is
currently no client for anyone asking, but I'm working on that). There
are a number of fixes and new features (see me for current release
notes). The production release date is March 1st, along with MMK V5.0
and new releases of WATCHER and NETLIB. I've been busy...:-)
If you'd like to know more, mail me privately.
Regards, Tim.
On Wed, 30 Jan 2013 09:10:26 -0500
"Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote:
Sampsa Laine <sampsa at mac.com> writes:
On 30 Jan 2013, at 14:55, Brian Schenkenberger, VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes: > > > Back when I worked in
one
of my Uncle Sam's DoD research labs, all email > was handled on the
VMS cluster and distributed to other mail servers and > clients in
the labs.
PMDF was the engine used there for this task. If > you don't
anticipate HUGE volume of email, even MX could do this and MX > is
freeware.
So MX can do the subdomain -> decnet node name conversion?
Why not? Use its rewrite rules.
Assume there is a HECnet.net domain and that all nodenames are used as
hostnames in a FQDN. The mail handler node is called PMASTR or TCP/IP
hame of postmaster.HECnet.net.
MCP> DEFINE REWRITE_RULE "<{user}(a){host}.HECnet.net>" -
_MCP> "<""{host}::{user}""@postmaster.HECnet.net>"
I need to check here but you might even be able to use:
_MCP> "<""{host}::{user}""@localhost>"
...but this might hork up replies. For more elaborate schemes, MX is
capable of rewriting using *IX-style regular expressions with /REGEX
on the 'DEFINE REWRITE_RULE' command.
Spot on.
For the reverse (outgoing and replies), configure the DN_SMTP server
which is SMTP over DECnet.
This is a part of MX that I don't know nearly as well as I should, but
I though you needed MX at both ends to make that work. Which would
rule out RSTS and RSX hosts.
MX has alias translation, mailing list features and other delivery
agents such as X25, UUCP and a SITE interface. The latter allows a
X25 and UUCP have been dropped when MX became open source. SITE is
definitely still there. I've seend that used for lots of interesting
stuff. I'm pretty sure it was Ruslan Laishev that developed an SMS
gateway for MX.
customizable interface to other applications running on its host. I
once used it to interface to a trouble report (user support) system
and I use it today to provide customers with access to a temporary
licence (PAK) generator for software trials.
In addition, I know the MX developers quite well. ;)
Regards, Tim.
On Wed, 30 Jan 2013 15:23:21 +0200
Sampsa Laine <sampsa at mac.com> wrote:
On 30 Jan 2013, at 14:55, Brian Schenkenberger, VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes:
Back when I worked in one of my Uncle Sam's DoD research labs, all
email was handled on the VMS cluster and distributed to other mail
servers and clients in the labs. PMDF was the engine used there
for this task. If you don't anticipate HUGE volume of email, even
MX could do this and MX is freeware.
So MX can do the subdomain -> decnet node name conversion?
Not straight out of the box, but it sounds like something fun to try
and set up. MX can do a lot of useful things, including breaking out
to a DCL procedure to do message handling.
It would be an interesting feature to add though. I guess if I looked
in to how MAIL-11 does its business it would be possible to knock up
something bi-directional.
Regards, Tim.
Sampsa Laine <sampsa at mac.com> writes:
On 30 Jan 2013, at 14:55, Brian Schenkenberger, VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes: > > > Back when I worked in one
of my Uncle Sam's DoD research labs, all email > was handled on the VMS
cluster and distributed to other mail servers and > clients in the labs.
PMDF was the engine used there for this task. If > you don't
anticipate HUGE volume of email, even MX could do this and MX > is
freeware.
So MX can do the subdomain -> decnet node name conversion?
Why not? Use its rewrite rules.
Assume there is a HECnet.net domain and that all nodenames are used as
hostnames in a FQDN. The mail handler node is called PMASTR or TCP/IP
hame of postmaster.HECnet.net.
MCP> DEFINE REWRITE_RULE "<{user}(a){host}.HECnet.net>" -
_MCP> "<""{host}::{user}""@postmaster.HECnet.net>"
I need to check here but you might even be able to use:
_MCP> "<""{host}::{user}""@localhost>"
...but this might hork up replies. For more elaborate schemes, MX is
capable of rewriting using *IX-style regular expressions with /REGEX
on the 'DEFINE REWRITE_RULE' command.
For the reverse (outgoing and replies), configure the DN_SMTP server
which is SMTP over DECnet.
MX has alias translation, mailing list features and other delivery
agents such as X25, UUCP and a SITE interface. The latter allows a
customizable interface to other applications running on its host. I
once used it to interface to a trouble report (user support) system
and I use it today to provide customers with access to a temporary
licence (PAK) generator for software trials.
In addition, I know the MX developers quite well. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Sampsa,
This end also has a gateway but it is restricted (at the moment). I
have been experimenting with it mostly. Fred set it up for me on the
Postfix side and I did the other end.
That said, Multi-Watch makes use of CHIMPY:: to send out IP address
changes.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of sampsa at mac.com
Sent: Tuesday, January 29, 2013 23:09
To: hecnet at Update.UU.SE
Subject: [HECnet] Mail gateways?
Is anyone (aside from myself)* running a mail gateway between
HECnet and the Internet at large?
I remember there being a plan to set up a domain and then set
up subdomains for each node, but not sure what happened to that..
* CHIMPY gateways mail to and from the Internet, rather
awkwardly though and not all providers like the slightly
wacky addresses it produces.
To send, mail to: CHIMPY::smtp%"joe at example.com"
Your inbound address is <NODENAME>::<USERNAME>@chimpymail.com
Sampsa
On Wed, 30 Jan 2013 07:55:53 -0500
"Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote:
Sampsa Laine <sampsa at mac.com> writes:
On 30 Jan 2013, at 11:25, Mark Wickens wrote:
On 30/01/2013 05:45, Sampsa Laine wrote: >> On 30 Jan 2013, at
06:23,
Ian McLaughlin wrote: >> >>> Chimpy. Sorry for the autocorrect on
your name below - just noticed :) >>> >> Oh cool, glad to know
someone finds it useful. >> >> sampsa >> >> >> > I probably mumbled
at one time about setting up a gateway via the 'hecnet.eu' domain -
alas I don't have the technical skills to do this, but there is a
24/7 VAX SIMH instance running behind that domain that could easily
be used to run a gateway. >
Regards, Mark.
The subdomain -> machine mapping would be cool, maybe some other MTA
like PMDF (or whatever it's called) oculd handle it?
Back when I worked in one of my Uncle Sam's DoD research labs, all
email was handled on the VMS cluster and distributed to other mail
servers and clients in the labs. PMDF was the engine used there for
this task. If you don't anticipate HUGE volume of email, even MX
could do this and MX is freeware.
I have used MX at sites that receive quite a decent amount of mail and
have been quite impressed with the performance. Although, I'm biased...
Regards, Tim.
MX Maintainer
On 30 Jan 2013, at 14:55, Brian Schenkenberger, VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes:
Back when I worked in one of my Uncle Sam's DoD research labs, all email
was handled on the VMS cluster and distributed to other mail servers and
clients in the labs. PMDF was the engine used there for this task. If
you don't anticipate HUGE volume of email, even MX could do this and MX
is freeware.
So MX can do the subdomain -> decnet node name conversion?
Sampsa Laine <sampsa at mac.com> writes:
On 30 Jan 2013, at 11:25, Mark Wickens wrote:
On 30/01/2013 05:45, Sampsa Laine wrote: >> On 30 Jan 2013, at 06:23,
Ian McLaughlin wrote: >> >>> Chimpy. Sorry for the autocorrect on your
name below - just noticed :) >>> >> Oh cool, glad to know someone finds
it useful. >> >> sampsa >> >> >> > I probably mumbled at one time about
setting up a gateway via the 'hecnet.eu' domain - alas I don't have the
technical skills to do this, but there is a 24/7 VAX SIMH instance
running behind that domain that could easily be used to run a gateway. >
Regards, Mark.
The subdomain -> machine mapping would be cool, maybe some other MTA
like PMDF (or whatever it's called) oculd handle it?
Back when I worked in one of my Uncle Sam's DoD research labs, all email
was handled on the VMS cluster and distributed to other mail servers and
clients in the labs. PMDF was the engine used there for this task. If
you don't anticipate HUGE volume of email, even MX could do this and MX
is freeware.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
By the way, putting a hostname after file:// does either not work,
or initiates an ftp session...
On Tue, Jan 29, 2013 at 04:40:49PM +0100, Johnny Billquist wrote:
On 2013-01-29 15:29, Erik Olofsen wrote:
Yes indeed - unfortunately it doesn't work because Lynx does not allow
a host:: name as part of the url...
I suspected as much from the comments in the url you sent.
Seems silly, though. What happens if you just say "file://mim::info.txt" ?
(I must admit that I'm slightly confused on how many slashes are
appropriate...)
Johnny
Erik
On Tue, Jan 29, 2013 at 03:26:01PM +0100, Johnny Billquist wrote:
On 2013-01-29 14:53, Erik Olofsen wrote:
If we may use an url such as mim::something.html, which would normally be a
file:// there would be some basic functionality I think?
Right, since that is basically just using the file: transport/protocol.
The fact that files can be accessed transparently over DECnet makes it
possible to access documents "over DECnet".
Depending on how the parsing/handling of the url for something in the
file: domain is done, this might actually work straight away.
Johnny
Erik
On Tue, Jan 29, 2013 at 02:04:39PM +0100, Johnny Billquist wrote:
On 2013-01-29 13:44, Erik Olofsen wrote:
HECnetters,
Is anyone interested in using Lynx on HECnet?
Using node names in the url is not possible; some information is here:
http://lists.gnu.org/archive/html/lynx-dev/1997-01/msg00057.html
On my Alpha with VMS 6.1, I'm able to compile Lynx version 2.3.
It seems that the latest version, 2.8.7, does not compile under VMS 8.3.
Perhaps I'm going to have a look at the old sources; perhaps I'm going
to do something more useful...
Well, the basic "problem" is that there is no http object defined in
DECnet, nor any equivalent to the http protocol, so how would you expect
it to work?
DECnet is not IP, nor TCP.
Johnny
