6 Apr
2017
6 Apr
'17
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