6 Apr
2017
6 Apr
'17
11:02 p.m.
I've been busy (as usual) with writing stuff for RSX. And been a bit
annoyed at not having a nice mail gateway between TCP/IP and DECnet. So
I've written one for RSX, which is now live.
This is still very new and not so very tested code, so I really
appreciate any error reports, feature requests, thought, or just stress
tests... :-)
So, without making it any more complicated:
To send mail from anywhere on the Internet to a host on HECnet:
<node>::<user>@Mim.Update.UU.SE
To send mail from a node on HECnet to Internet:
MIM::<user>@<host>
Of course, as usual, PMR addressing works on the DECnet side. Also, this
mail gateway can also deal with local mail on Mim, in case anyone
wonders. And it does *not* relay mail on the Internet.
I've done a cut of BQTCP as well, with this mailer included. But I'm not
officially making a release yet. That is what the next week or so of
testing is leading me up to, though. :-)
And if people try to get this up and working let me know, as the
documentation might still be a bit cryptic as well.
And in case anyone wonder - yes, it does use MX records on the TCP/IP
side. Also, Mim is behind a firewall, so for most people, SMTP access
directly to Mim does not work. However, Mim also have an MX record
pointing to an intermediate machine which then relays the messages on to
Mim, but this introduces about a 10s delay in mails sent from the
Internet to HECnet.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
6 Apr
6 Apr
11:23 p.m.
Thanks Johnny, worked perfect for me (qcocal::sanyal is setup to be
forwarded to openvms-vax.sanyal.duckdns.org at riseup.net).
I am not an expert and do not understand the X-VMS-True-From header but
will try to figure it out.
Thanks again,
Supratim
Return-Path: <openvms-vax.sanyal.duckdns.org at riseup.net>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
vireo.riseup.net
X-Spam-Level: ***
X-Spam-Pyzor: Reported 0 times.
X-Spam-Status: No, score=3.5 required=11.0
tests=AM_TRUNCATED,CK_419SIZE,
DKIM_SIGNED,DKIM_VALID,FROM_IS_TO,MAILPHISH3B,RCVD_IN_DNSWL_MED,
RISEUP_SPF_TRUE,SPF_FAIL,TO_NOREAL shortcircuit=no
autolearn=disabled
version=3.4.0
Delivered-To: supratim at riseup.net
Received: from mx1.riseup.net (unknown [10.0.1.33])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
bits))
(Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation
Secure Server CA" (verified OK))
by vireo.riseup.net (Postfix) with ESMTPS id 82E0BAE
for <supratim at riseup.net>; Thu, 6 Apr 2017 21:13:48 +0000 (UTC)
Received: from a2i603.smtp2go.com (a2i603.smtp2go.com [103.47.206.91])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128
bits))
(Client did not present a certificate)
by mx1.riseup.net (Postfix) with ESMTPS id 0CB511A2091
for <OPENVMS-VAX.SANYAL.DUCKDNS.ORG at riseup.net>; Thu, 6 Apr 2017
21:13:48 +0000 (UTC)
Authentication-Results: mx1.riseup.net; dkim=pass
reason="2048-bit key; unprotected key"
header.d=smtpcorp.com header.i=(a)smtpcorp.com header.b=fv/KTM0+;
dkim-adsp=none (unprotected policy); dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=smtpcorp.com; s=a0-2;
h=Feedback-ID:X-Smtpcorp-Track:Subject:To:From:
Message-Id:Date:List-Unsubscribe:Reply-To;
bh=xc4j0WMVZbQ9528/mXlZo+ljbIhmo2uVv/GFigPYU1s=;
b=fv/KTM0+lmf5zKD1z2Al5JIR6f
wrNwtC6CsLQBTsZaZ3PZwzsCgaNt/I9qAtUI1qVD+10op6PMcj0B7JRjYmnOO31HOfAsaFRdaA49D
yHxnEj2ser5bJsxTIsPYUjaOw+ps200DNupLzAl9KnvrvU3caB0l5+SuyqW1U5YPtlUWtaddpXU3c
n9T2rAZRzjtTmtl5qpha5BWvoX9w65lmmkwb/J2AJ1zjxyOp6xdtu8Re1fQec3MZVzz0uoPv7ICIP
rtD73h+BoH/w3zxXltDHgGhrB9dSKZ/7Nfs1GJbiXwGgjq9FzXlmU5xR8in4fE5OWtUA2Xhut+Eu3
LaEMKO9g==;
X-Virus-Scanned: amavisd-new at
Date: Thu, 6 Apr 2017 21:13:07 +0000 (UTC)
Message-Id: <17040621130776 at sanyalnet-openvms-vax.freeddns.org>
From: openvms-vax.sanyal.duckdns.org at riseup.net (DO NOT REPLY -
OpenVMS/VAX
7.3 on VAXserver 3900 Hobbyist System at sanyal.duckdns.org)
To: OPENVMS-VAX.SANYAL.DUCKDNS.ORG at riseup.net
Subject: TEST | Fwd: [HECnet] HECnet mail gateway...
X-VMS-To: "qcocal::sanyal"@Mim.Update.UU.SE
X-VMS-True-From:
"MIM::supratim at riseup.net"(a)sanyalnet-openvms-vax.freeddns.org
X-Smtpcorp-Track: 1cwEio4gfFmj41.5IADMHv-i
Feedback-ID: 155438m:155438aI-WQNj:155438s3CBMMPXu6:SMTPCORP
X-Report-Abuse: Please forward a copy of this message, including all
headers, to <abuse at smtp2go.com>
On 2017-04-06 17:02, Johnny Billquist wrote:
I've been busy (as usual) with writing stuff for
RSX. And been a bit
annoyed at not having a nice mail gateway between TCP/IP and DECnet.
So I've written one for RSX, which is now live.
This is still very new and not so very tested code, so I really
appreciate any error reports, feature requests, thought, or just
stress tests... :-)
So, without making it any more complicated:
To send mail from anywhere on the Internet to a host on HECnet:
<node>::<user>@Mim.Update.UU.SE
To send mail from a node on HECnet to Internet:
MIM::<user>@<host>
Of course, as usual, PMR addressing works on the DECnet side. Also,
this mail gateway can also deal with local mail on Mim, in case anyone
wonders. And it does *not* relay mail on the Internet.
I've done a cut of BQTCP as well, with this mailer included. But I'm
not officially making a release yet. That is what the next week or so
of testing is leading me up to, though. :-)
And if people try to get this up and working let me know, as the
documentation might still be a bit cryptic as well.
And in case anyone wonder - yes, it does use MX records on the TCP/IP
side. Also, Mim is behind a firewall, so for most people, SMTP access
directly to Mim does not work. However, Mim also have an MX record
pointing to an intermediate machine which then relays the messages on
to Mim, but this introduces about a 10s delay in mails sent from the
Internet to HECnet.
Johnny
25 Aug
25 Aug
1:09 a.m.
New subject: DECnet-Linux/Ubuntu 17 64-bit
Hi
I have started to work on a 64-bit Ubuntu 17/Zesty VM to try to get it
to talk DECnet. Many of you have already done this.
This is going to be called MOKSHA with address 1.553.
I had to compile dn-progs and dn-common from source; the dnping/dndir
etc. stuff in the Ubuntu repos crashed on invocation.
Currently trying to figure out how to get Johnny's bridge into the mix;
the closest I have gotten so far is dneigh shows a few HECnet nodes but
nothing else works.
I may have flooded psilo.update.uu.se too, which may have blocked my IP
off because I am not hearing back from psilo.update.uu.se.
Anyway, that's all for now. Any tips on HECnet bridging for Ubuntu/Linux
welcome.
Thanks for reading.
Supratim
29 Aug
29 Aug
4:31 p.m.
New subject: DECnet-Linux/Ubuntu 17 64-bit
Hi,
I've been trying and failing to get Ubuntu 16.04 LTS 64bit up and running
as 1.251 (MASTER).
I had it working before but its failing utterly this time.
On Fri, Aug 25, 2017 at 12:09 AM, Supratim Sanyal <supratim at riseup.net>
wrote:
Hi
I have started to work on a 64-bit Ubuntu 17/Zesty VM to try to get it to
talk DECnet. Many of you have already done this.
This is going to be called MOKSHA with address 1.553.
I had to compile dn-progs and dn-common from source; the dnping/dndir etc.
stuff in the Ubuntu repos crashed on invocation.
Currently trying to figure out how to get Johnny's bridge into the mix;
the closest I have gotten so far is dneigh shows a few HECnet nodes but
nothing else works.
I may have flooded psilo.update.uu.se too, which may have blocked my IP
off because I am not hearing back from psilo.update.uu.se.
Anyway, that's all for now. Any tips on HECnet bridging for Ubuntu/Linux
welcome.
Thanks for reading.
Supratim
9:29 p.m.
New subject: DECnet-Linux/Ubuntu 17 64-bit
No luck here either Tony so far. I can get dneigh to see the nodes but am struggling with
the proxies configuration to set host to it. sethost out of it just hangs there. Will keep
trying - this should work! Ubuntu 17 zesty 64 bit here btw.
On Aug 29, 2017, at 10:31 AM, Tony Blews <tonyblews
at gmail.com> wrote:
Hi,
I've been trying and failing to get Ubuntu 16.04 LTS 64bit up and running as 1.251
(MASTER).
I had it working before but its failing utterly this time.
On Fri, Aug 25, 2017 at 12:09 AM, Supratim Sanyal
<supratim at riseup.net> wrote:
Hi
I have started to work on a 64-bit Ubuntu 17/Zesty VM to try to get it to talk DECnet.
Many of you have already done this.
This is going to be called MOKSHA with address 1.553.
I had to compile dn-progs and dn-common from source; the dnping/dndir etc. stuff in the
Ubuntu repos crashed on invocation.
Currently trying to figure out how to get Johnny's bridge into the mix; the closest I
have gotten so far is dneigh shows a few HECnet nodes but nothing else works.
I may have flooded psilo.update.uu.se too, which may have blocked my IP off because I am
not hearing back from psilo.update.uu.se.
Anyway, that's all for now. Any tips on HECnet bridging for Ubuntu/Linux welcome.
Thanks for reading.
Supratim
30 Aug
30 Aug
8:05 p.m.
New subject: DECnet-Linux/Ubuntu 17 64-bit
Hi,
I'm being told elsewhere that its unsupported since about 13.04. Which
explains how I had it working before. I'm going to spin up a 13.04
installation and try that.
In the meantime, on 16.04 I'm getting
tony at servalan:~$ dnlogin 1.251
Cannot connect to 1.251: Rejected by object
tony at servalan:~$ dnlogin master
Cannot connect to master: Rejected by object
and not showing up on the node list anyway
On Tue, Aug 29, 2017 at 8:29 PM, Supratim Sanyal <supratim at riseup.net>
wrote:
No luck here either Tony so far. I can get dneigh to
see the nodes but am
struggling with the proxies configuration to set host to it. sethost out of
it just hangs there. Will keep trying - this should work! Ubuntu 17 zesty
64 bit here btw.
9 Sep
9 Sep
3:44 p.m.
New subject: DECnet-Linux/Ubuntu 17 64-bit
Tony,
Success with Ubuntu 14.4 ... all OK except ctermd looks for /pty - guess will have to
build from sources
Thanks
Supratim
On Aug 29, 2017, at 3:29 PM, Supratim Sanyal
<supratim at riseup.net> wrote:
No luck here either Tony so far. I can get dneigh to see the nodes but am struggling with
the proxies configuration to set host to it. sethost out of it just hangs there. Will keep
trying - this should work! Ubuntu 17 zesty 64 bit here btw.
> On Aug 29, 2017, at 10:31 AM, Tony Blews <tonyblews at gmail.com> wrote:
>
> Hi,
> I've been trying and failing to get Ubuntu 16.04 LTS 64bit up and running as
1.251 (MASTER).
> I had it working before but its failing utterly this time.
>
>> On Fri, Aug 25, 2017 at 12:09 AM, Supratim Sanyal <supratim at riseup.net>
wrote:
>> Hi
>>
>> I have started to work on a 64-bit Ubuntu 17/Zesty VM to try to get it to talk
DECnet. Many of you have already done this.
>>
>> This is going to be called MOKSHA with address 1.553.
>>
>> I had to compile dn-progs and dn-common from source; the dnping/dndir etc. stuff
in the Ubuntu repos crashed on invocation.
>>
>> Currently trying to figure out how to get Johnny's bridge into the mix; the
closest I have gotten so far is dneigh shows a few HECnet nodes but nothing else works.
>>
>> I may have flooded psilo.update.uu.se too, which may have blocked my IP off
because I am not hearing back from psilo.update.uu.se.
>>
>> Anyway, that's all for now. Any tips on HECnet bridging for Ubuntu/Linux
welcome.
>>
>> Thanks for reading.
>>
>> Supratim
>
13 Sep
13 Sep
6:43 p.m.
New subject: DECnet-Linux/Ubuntu 17 64-bit
Hi Supratim,
I still find DECnet on Ubuntu to be very flakey after 9.10 and the code
being "orphaned". My 9.10 x32 instance (DOCTOR) is sometimes up at 1.252.
I just need to port it from my win10 laptop to the Ubuntu 16.04 x64 rack
unit.
(never underestimate the usefulness of old 1U rack unit bought for pennies
on eBay - if I don't stop myself I will end up with a floor-standing 18U,
which is entering MicroVAX like proportions).
Tony.
On Sat, Sep 9, 2017 at 2:44 PM, Supratim Sanyal <supratim at riseup.net> wrote:
Tony,
Success with Ubuntu 14.4 ... all OK except ctermd looks for /pty - guess
will have to build from sources
Thanks
Supratim
On Aug 29, 2017, at 3:29 PM, Supratim Sanyal <supratim at riseup.net> wrote:
No luck here either Tony so far. I can get dneigh to see the nodes but am
struggling with the proxies configuration to set host to it. sethost out of
it just hangs there. Will keep trying - this should work! Ubuntu 17 zesty
64 bit here btw.
On Aug 29, 2017, at 10:31 AM, Tony Blews <tonyblews at gmail.com> wrote:
Hi,
I've been trying and failing to get Ubuntu 16.04 LTS 64bit up and running
as 1.251 (MASTER).
I had it working before but its failing utterly this time.
On Fri, Aug 25, 2017 at 12:09 AM, Supratim Sanyal <supratim at riseup.net>
wrote:
Hi
I have started to work on a 64-bit Ubuntu 17/Zesty VM to try to get it to
talk DECnet. Many of you have already done this.
This is going to be called MOKSHA with address 1.553.
I had to compile dn-progs and dn-common from source; the dnping/dndir
etc. stuff in the Ubuntu repos crashed on invocation.
Currently trying to figure out how to get Johnny's bridge into the mix;
the closest I have gotten so far is dneigh shows a few HECnet nodes but
nothing else works.
I may have flooded psilo.update.uu.se too, which may have blocked my IP
off because I am not hearing back from psilo.update.uu.se.
Anyway, that's all for now. Any tips on HECnet bridging for Ubuntu/Linux
welcome.
Thanks for reading.
Supratim
7:42 p.m.
New subject: DECnet-Linux/Ubuntu 17 64-bit
Want a rack to put that all in? ?
On Sep 13, 2017 12:44, "Tony Blews" <tonyblews at gmail.com> wrote:
Hi Supratim,
I still find DECnet on Ubuntu to be very flakey after 9.10 and the code
being "orphaned". My 9.10 x32 instance (DOCTOR) is sometimes up at 1.252.
I just need to port it from my win10 laptop to the Ubuntu 16.04 x64 rack
unit.
(never underestimate the usefulness of old 1U rack unit bought for pennies
on eBay - if I don't stop myself I will end up with a floor-standing 18U,
which is entering MicroVAX like proportions).
Tony.
On Sat, Sep 9, 2017 at 2:44 PM, Supratim Sanyal <supratim at riseup.net>
wrote:
Tony,
Success with Ubuntu 14.4 ... all OK except ctermd looks for /pty - guess
will have to build from sources
Thanks
Supratim
On Aug 29, 2017, at 3:29 PM, Supratim Sanyal <supratim at riseup.net> wrote:
No luck here either Tony so far. I can get dneigh to see the nodes but am
struggling with the proxies configuration to set host to it. sethost out of
it just hangs there. Will keep trying - this should work! Ubuntu 17 zesty
64 bit here btw.
On Aug 29, 2017, at 10:31 AM, Tony Blews <tonyblews at gmail.com> wrote:
Hi,
I've been trying and failing to get Ubuntu 16.04 LTS 64bit up and running
as 1.251 (MASTER).
I had it working before but its failing utterly this time.
On Fri, Aug 25, 2017 at 12:09 AM, Supratim Sanyal <supratim at riseup.net>
wrote:
Hi
I have started to work on a 64-bit Ubuntu 17/Zesty VM to try to get it
to talk DECnet. Many of you have already done this.
This is going to be called MOKSHA with address 1.553.
I had to compile dn-progs and dn-common from source; the dnping/dndir
etc. stuff in the Ubuntu repos crashed on invocation.
Currently trying to figure out how to get Johnny's bridge into the mix;
the closest I have gotten so far is dneigh shows a few HECnet nodes but
nothing else works.
I may have flooded psilo.update.uu.se too, which may have blocked my IP
off because I am not hearing back from psilo.update.uu.se.
Anyway, that's all for now. Any tips on HECnet bridging for Ubuntu/Linux
welcome.
Thanks for reading.
Supratim
10 Apr
10 Apr
10:04 a.m.
That is so damned cool!
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Johnny Billquist
Sent: Friday, April 7, 2017 7:02 AM
To: hecnet at Update.UU.SE
Subject: [HECnet] HECnet mail gateway...
I've been busy (as usual) with writing stuff for RSX. And been a bit annoyed at not
having a nice mail gateway between TCP/IP and DECnet. So I've written one for RSX,
which is now live.
This is still very new and not so very tested code, so I really appreciate any error
reports, feature requests, thought, or just stress tests... :-)
So, without making it any more complicated:
To send mail from anywhere on the Internet to a host on HECnet:
<node>::<user>@Mim.Update.UU.SE
To send mail from a node on HECnet to Internet:
MIM::<user>@<host>
Of course, as usual, PMR addressing works on the DECnet side. Also, this mail gateway can
also deal with local mail on Mim, in case anyone wonders. And it does *not* relay mail on
the Internet.
I've done a cut of BQTCP as well, with this mailer included. But I'm not
officially making a release yet. That is what the next week or so of testing is leading me
up to, though. :-)
And if people try to get this up and working let me know, as the documentation might still
be a bit cryptic as well.
And in case anyone wonder - yes, it does use MX records on the TCP/IP side. Also, Mim is
behind a firewall, so for most people, SMTP access directly to Mim does not work. However,
Mim also have an MX record pointing to an intermediate machine which then relays the
messages on to Mim, but this introduces about a 10s delay in mails sent from the Internet
to HECnet.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Disclaimer
The information in this e-mail is confidential and may contain content that is subject to
copyright and/or is commercial-in-confidence and is intended only for the use of the above
named addressee. If you are not the intended recipient, you are hereby notified that
dissemination, copying or use of the information is strictly prohibited. If you have
received this e-mail in error, please telephone Fujitsu Australia Limited on 02 9776 4555
or by reply e-mail to the sender and delete the document and all copies thereof.
Whereas Fujitsu Australia Limited would not knowingly transmit a virus within an email
communication, it is the receiver?s responsibility to scan all communication and any files
attached for computer viruses and other defects. Fujitsu Australia Limited does not accept
liability for any loss or damage (whether direct, indirect, consequential or economic)
however caused, and whether by negligence or otherwise, which may result directly or
indirectly from this communication or any files attached.
If you do not wish to receive commercial and/or marketing email messages from Fujitsu
Australia Limited, please email unsubscribe at au.fujitsu.com.
12 Apr
12 Apr
10:20 p.m.
Unfortunately gmail, in its infinite wisdom, gives the following fatal
error:
Error
The address "glgmsh::phiber at mim.update.uu.se" in the "To" field was
not
recognized. Please make sure that all addresses are properly formed.
On Thu, Apr 6, 2017 at 2:02 PM, Johnny Billquist <bqt at softjar.se> wrote:
I've been busy (as usual) with writing stuff for
RSX. And been a bit
annoyed at not having a nice mail gateway between TCP/IP and DECnet. So
I've written one for RSX, which is now live.
This is still very new and not so very tested code, so I really appreciate
any error reports, feature requests, thought, or just stress tests... :-)
So, without making it any more complicated:
To send mail from anywhere on the Internet to a host on HECnet:
<node>::<user>@Mim.Update.UU.SE
To send mail from a node on HECnet to Internet:
MIM::<user>@<host>
Of course, as usual, PMR addressing works on the DECnet side. Also, this
mail gateway can also deal with local mail on Mim, in case anyone wonders.
And it does *not* relay mail on the Internet.
I've done a cut of BQTCP as well, with this mailer included. But I'm not
officially making a release yet. That is what the next week or so of
testing is leading me up to, though. :-)
And if people try to get this up and working let me know, as the
documentation might still be a bit cryptic as well.
And in case anyone wonder - yes, it does use MX records on the TCP/IP
side. Also, Mim is behind a firewall, so for most people, SMTP access
directly to Mim does not work. However, Mim also have an MX record pointing
to an intermediate machine which then relays the messages on to Mim, but
this introduces about a 10s delay in mails sent from the Internet to HECnet.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
10:24 p.m.
I was able to get through google's stupidity by saying "glgmsh::phiber"@
mim.update.uu.se (with the added quotes), but I don't know if it reached
you, or if your gateway barfed on the quotes. Still hasn't arrived at the
remote end.
-Mark
On Wed, Apr 12, 2017 at 1:20 PM, Mark Abene <phiber at phiber.com> wrote:
Unfortunately gmail, in its infinite wisdom, gives the
following fatal
error:
Error
The address "glgmsh::phiber at mim.update.uu.se" in the "To" field
was not
recognized. Please make sure that all addresses are properly formed.
On Thu, Apr 6, 2017 at 2:02 PM, Johnny Billquist <bqt at softjar.se> wrote:
I've been busy (as usual) with writing stuff
for RSX. And been a bit
annoyed at not having a nice mail gateway between TCP/IP and DECnet. So
I've written one for RSX, which is now live.
This is still very new and not so very tested code, so I really
appreciate any error reports, feature requests, thought, or just stress
tests... :-)
So, without making it any more complicated:
To send mail from anywhere on the Internet to a host on HECnet:
<node>::<user>@Mim.Update.UU.SE
To send mail from a node on HECnet to Internet:
MIM::<user>@<host>
Of course, as usual, PMR addressing works on the DECnet side. Also, this
mail gateway can also deal with local mail on Mim, in case anyone wonders.
And it does *not* relay mail on the Internet.
I've done a cut of BQTCP as well, with this mailer included. But I'm not
officially making a release yet. That is what the next week or so of
testing is leading me up to, though. :-)
And if people try to get this up and working let me know, as the
documentation might still be a bit cryptic as well.
And in case anyone wonder - yes, it does use MX records on the TCP/IP
side. Also, Mim is behind a firewall, so for most people, SMTP access
directly to Mim does not work. However, Mim also have an MX record pointing
to an intermediate machine which then relays the messages on to Mim, but
this introduces about a 10s delay in mails sent from the Internet to HECnet.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
13 Apr
13 Apr
12:58 a.m.
On 2017-04-12 22:24, Mark Abene wrote:
I was able to get through google's stupidity by
saying
"glgmsh::phiber"@mim.update.uu.se <http://mim.update.uu.se> (with the
added quotes), but I don't know if it reached you, or if your gateway
barfed on the quotes. Still hasn't arrived at the remote end.
There was some hiccup at Mim, so the mail got stuck for a while. I
improved the MAIL11 code some, and then the mail went through, I believe.
Johnny
-Mark
On Wed, Apr 12, 2017 at 1:20 PM, Mark Abene <phiber at phiber.com
<mailto:phiber at phiber.com>> wrote:
Unfortunately gmail, in its infinite wisdom, gives the following
fatal error:
Error
The address "glgmsh::phiber at mim.update.uu.se
<mailto:glgmsh%3A%3Aphiber at mim.update.uu.se>" in the "To"
field was
not recognized. Please make sure that all addresses are properly formed.
On Thu, Apr 6, 2017 at 2:02 PM, Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
I've been busy (as usual) with writing stuff for RSX. And been a
bit annoyed at not having a nice mail gateway between TCP/IP and
DECnet. So I've written one for RSX, which is now live.
This is still very new and not so very tested code, so I really
appreciate any error reports, feature requests, thought, or just
stress tests... :-)
So, without making it any more complicated:
To send mail from anywhere on the Internet to a host on HECnet:
<node>::<user>@Mim.Update.UU.SE <http://Mim.Update.UU.SE>
To send mail from a node on HECnet to Internet:
MIM::<user>@<host>
Of course, as usual, PMR addressing works on the DECnet side.
Also, this mail gateway can also deal with local mail on Mim, in
case anyone wonders. And it does *not* relay mail on the Internet.
I've done a cut of BQTCP as well, with this mailer included. But
I'm not officially making a release yet. That is what the next
week or so of testing is leading me up to, though. :-)
And if people try to get this up and working let me know, as the
documentation might still be a bit cryptic as well.
And in case anyone wonder - yes, it does use MX records on the
TCP/IP side. Also, Mim is behind a firewall, so for most people,
SMTP access directly to Mim does not work. However, Mim also
have an MX record pointing to an intermediate machine which then
relays the messages on to Mim, but this introduces about a 10s
delay in mails sent from the Internet to HECnet.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se <mailto:bqt at softjar.se> ||
Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
2419
days inactive
2579
days old
14 comments
7 participants
participants (7)
-
Alastair.Boyanich＠au.fujitsu.com -
bqt＠softjar.se -
mcguire＠neurotica.com -
phiber＠phiber.com -
supratim＠riseup.net -
tonyblews＠gmail.com -
wonko＠4amlunch.net