[nos-bbs] Junk Headers

[Maiko Langelaar (Personal)]

Read the documentation, search for 'bulletin check' :

   https://www.langelaar.net/jnos2/documents/manuals/JNOS2-MAN.txt

It's been part of JNOS long before I took it over ...

This is all about the black magic of R: lines :]

M

On 8/19/25 08:35, Chris Maness wrote:

> Never mind, I see it in my autoexec.nos.  But the question still
> stands, do I need this on for something to function correctly?
>
> -Chris KQ6UP
>
> On Tue, Aug 19, 2025 at 6:32 AM Chris Maness
> <christopher.maness at gmail.com> wrote:
>> It is on.  What sets this variable, and is it necessary?  Is it a
>> compile time option, or a runtime option?
>>
>> On Tue, Aug 19, 2025 at 6:13 AM Maiko Langelaar (Personal)
>> <maiko at pcsinternet.ca> wrote:
>>> The only other possibility that I can see (so far) in the code is :
>>>
>>>      jnos> bulletin check
>>>      Use R: to check buls: off
>>>
>>> IF this is on, it may required certain X- headers to function properly.
>>>
>>> Maiko
>>>
>>> On 8/19/25 08:02, Chris Maness wrote:
>>>
>>>> Thanks, I will have a look at this.  My smtptoo does nothing to turn
>>>> off the X-* lines for some reason.
>>>>
>>>> -Chris KQ6UP
>>>>
>>>> On Tue, Aug 19, 2025 at 5:52 AM Mark Herson, N2MH <n2mh at n2mh.net> wrote:
>>>>> For what it's worth...
>>>>>
>>>>> Normally I run jnos with `mbox smtptoo = off` and messages appear as
>>>>> they would from a non-jnos system. As an experiment, I set
>>>>> `mbox smtptoo = on`. As a result, the Junk Headers appeared:
>>>>>
>>>>>> >From n2mh%n2mh at jnos2.n2mh.ampr.org Mon Aug 18 21:39:12 2025
>>>>>> Received: from jnos2.n2mh.ampr.org by jnos2.n2mh.ampr.org (jnos 2.0p) with SMTP
>>>>>>         id AA35826 ; Mon, 18 Aug 2025 21:39:12 GMT
>>>>>> Message-Id: <A8KFIDF_PWXB at n2mh.bbs>
>>>>>>> From: n2mh%n2mh.bbs at jnos2.n2mh.ampr.org
>>>>>> X-JNOS-User-Port: Telnet   (n2mh @ 44.64.24.194)  ->  Sending message
>>>>> When I went back to normal and set 'mbox smtptoo = off`, the Junk
>>>>> Headers disappeared. Note that when smtptoo was on, the Junk Headers
>>>>> appeared for traffic passing through jnos as well as traffic originated
>>>>> on jnos.
>>>>>
>>>>> Also, For What It's Worth, I have found that the order of configuration
>>>>> directives in autoexec.nos is important. As a result, I have grouped all
>>>>> directives for a given task/service together, apparently in the order of
>>>>> when those given tasks/services are enabled inside of jnos and are ready
>>>>> and able to take configuration directives.
>>>>>
>>>>> So, my mbox section looks like this:
>>>>>
>>>>>> # mbox #
>>>>>> mbox attend off
>>>>>> mbox convers on
>>>>>> mbox fbb 0
>>>>>> mbox fwdinfo    "jnos 2.0p"
>>>>>> mbox haddress   n2mh.#nnj.nj.usa.noam
>>>>>> mbox header on
>>>>>> mbox mailfor 600
>>>>>> mbox nobid on
>>>>>> mbox newmail    on
>>>>>> mbox nrid       on
>>>>>> mbox qth        "via Mesh"
>>>>>> mbox smtptoo    off
>>>>>> mbox tdisc      120
>>>>>> mbox timer      30      # forwarding timer
>>>>>> mbox tmsg       "Welcome to the N2MH jnos BBS - MH2BBS\n"
>>>>>> mbox winlinkcalls 5u4gb 6al5
>>>>> Hope this helps.
>>>>>
>>>>> 73, Mark, N2MH
>>>>> N2MH at N2MH.#NNJ.NJ.USA.NOAM
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> nos-bbs mailing list
>>>>> nos-bbs at lists.tapr.org
>>>>> http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org
>>>>
>>
>>
>> --
>> Thanks,
>> Chris Maness
>
>