<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Maiko, do you propose to do this by relaying the message to an
SMTP server, with a 'To' address that causes the server to send
back a 'sorry' message? That would involve an SMTP server that
JNOS can connect to, and that always responds this way.<br>
</p>
<p>A 'To' address that's rewritten to "refuse" causes JNOS to
immediately refuse to accept the message, not send a 'sorry'
message back to the originator. The specificity of the pattern
that recognizes the 'To' address doesn't seem to matter.</p>
<p>Similarly, a 'To' address that's rewritten to
<whatever>@<undefined DNS name> is immediately
refused, although in this case it tells the BBS user the rewritten
address. For example:</p>
<pre>(#0) >
sp person@evil
To: <a class="moz-txt-link-abbreviated" href="mailto:person@evil.is.not.allowed">person@evil.is.not.allowed</a>
Bad user or hostname, please mail 'sysop' for help
(#0) >
</pre>
<div class="moz-signature">Best regards,<br>
John Kristian W6JMK<br>
<br>
</div>
<div class="moz-cite-prefix">On 10/28/2022 11:13 AM,
<a class="moz-txt-link-abbreviated" href="mailto:maiko@pcsinternet.ca">maiko@pcsinternet.ca</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:17bc5424ecbfa9931f343712153a4864@pcsinternet.ca">Actually,
if this is SMTP side, I am wondering if it should be :
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:kf5jrv%kf5jrv.#nwar.ar.usa.na@winnipeg.ampr.org">kf5jrv%kf5jrv.#nwar.ar.usa.na@winnipeg.ampr.org</a>
<br>
<br>
Note the additional @winnipeg.ampr.org is my own SMTP side ...
<br>
<br>
On 2022-10-28 13:10, <a class="moz-txt-link-abbreviated" href="mailto:maiko@pcsinternet.ca">maiko@pcsinternet.ca</a> wrote:
<br>
<blockquote type="cite">Have you tried to actually put in a refuse
in your rewrite, but using
<br>
the fully qualified address, for instance :
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:ve4klm@ve4klm.#wpg.mb.can.noam">ve4klm@ve4klm.#wpg.mb.can.noam</a> refuse
<br>
<br>
The key I suppose would be to find the correct spot in rewrite
to put
<br>
this so that it does not get processed first and 'shortened'. I
will
<br>
play with this, the SMTP code suggests that something is
possible.
<br>
<br>
It might just require a tweak then, since accepting messages is
a
<br>
standard thing, it's just we might have to do a minor change in
the
<br>
delivery part. Will let you know what I find.
<br>
<br>
Maiko / VE4KLM<br>
<br>
On 2022-10-28 12:12, John Kristian wrote:
<br>
<blockquote type="cite">Yes, to implement this JNOS would have
to receive a message, parse its
<br>
headers and then send a reply.
<br>
<br>
It's starting to sound like this would require a change to the
JNOS
<br>
source code. No one has suggested a solution using only
configuration
<br>
changes.
<br>
<br>
-- John Kristian W6JMK
<br>
<br>
On 10/28/2022 9:46 AM, <a class="moz-txt-link-abbreviated" href="mailto:maiko@pcsinternet.ca">maiko@pcsinternet.ca</a> wrote:
<br>
<blockquote type="cite">... There is just NO way to find out
who this came from at the point
<br>
where we decide to accept or refuse a message; as far as any
FBB
<br>
forwarding is concerned that is. We would have to accept the
msg
<br>
first, then parse it's headers, then reject it afterwards.
<br>
<br>
So the interesting exercise then becomes SMTP side. I know
the
<br>
SMTP side has refuse code, so perhaps it still can be done,
but
<br>
we would have to accept the message from FBB first, then
reject
<br>
it on delivery type of thing. Never done that before, but
...
<br>
<br>
Maiko / VE4KLM
<br>
<br>
On 2022-10-27 18:06, John Kristian wrote:
<br>
<blockquote type="cite">I would want the return message sent
to the value of the original
<br>
message's 'Return-Path' header, or if there is none, the
'From'
<br>
header.
<br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>