[nos-bbs] JNOS return to sender

[John Kristian]

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.

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.

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:

(#0) >
sp person at evil
To:person at evil.is.not.allowed
Bad user or hostname,  please mail 'sysop' for help
(#0) >

Best regards,
John Kristian W6JMK

On 10/28/2022 11:13 AM, maiko at pcsinternet.ca wrote:
> Actually, if this is SMTP side, I am wondering if it should be :
>
> kf5jrv%kf5jrv.#nwar.ar.usa.na at winnipeg.ampr.org
>
> Note the additional @winnipeg.ampr.org is my own SMTP side ...
>
> On 2022-10-28 13:10, maiko at pcsinternet.ca wrote:
>> Have you tried to actually put in a refuse in your rewrite, but using
>> the fully qualified address, for instance :
>>
>> ve4klm at ve4klm.#wpg.mb.can.noam  refuse
>>
>> The key I suppose would be to find the correct spot in rewrite to put
>> this so that it does not get processed first and 'shortened'. I will
>> play with this, the SMTP code suggests that something is possible.
>>
>> It might just require a tweak then, since accepting messages is a
>> standard thing, it's just we might have to do a minor change in the
>> delivery part. Will let you know what I find.
>>
>> Maiko / VE4KLM
>>
>> On 2022-10-28 12:12, John Kristian wrote:
>>> Yes, to implement this JNOS would have to receive a message, parse its
>>> headers and then send a reply.
>>>
>>> It's starting to sound like this would require a change to the JNOS
>>> source code. No one has suggested a solution using only configuration
>>> changes.
>>>
>>> -- John Kristian W6JMK
>>>
>>> On 10/28/2022 9:46 AM, maiko at pcsinternet.ca wrote:
>>>> ... There is just NO way to find out who this came from at the point
>>>> where we decide to accept or refuse a message; as far as any FBB
>>>> forwarding is concerned that is. We would have to accept the msg
>>>> first, then parse it's headers, then reject it afterwards.
>>>>
>>>> So the interesting exercise then becomes SMTP side. I know the
>>>> SMTP side has refuse code, so perhaps it still can be done, but
>>>> we would have to accept the message from FBB first, then reject
>>>> it on delivery type of thing. Never done that before, but ...
>>>>
>>>> Maiko / VE4KLM
>>>>
>>>> On 2022-10-27 18:06, John Kristian wrote:
>>>>> I would want the return message sent to the value of the original
>>>>> message's 'Return-Path' header, or if there is none, the 'From'
>>>>> header.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20221028/2d0b23c3/attachment-0001.html>