[nos-bbs] Junk Headers

[Mark Herson, N2MH]

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