| |
HB2PMS > JNOS 22.06.21 12:02l 106 Lines 3642 Bytes #999 (0) @ WW
BID : 9204HB2PMS
Read: GAST
Subj: JNOS 2.0m.5Gx (updates)
Path: DBO595<DBX320<DBX233<VB1BOX<NL3VKL<NL3PRC<HB1BBS<HB1BBS
Sent: 210621/2045 @:HB1BBS.ZL.NLD.EU Sally 7.2.051 $:9204HB2PMS
Message from: HB2PMS@HB1BBS
fixes and additions to 2.0m.5Gx - June 18, 2021
-----------------------------------------------
June 18
- By request, NEW capability in the rewrite file. One can now have entries
targeting (such a bad word) specific users / stations. In other words
one
can now add entries that apply to only a FROM <pattern>, for example :
*@ww:ve4klm hold
*@ww ww
This allows ALL incoming @ww to the ww area, but any @ww coming from me
is actually sent to the hold area instead. Or you could just refuse any
@ww coming from me, for example :
*@ww:ve4klm refuse
*@ww ww
In the case of refuse, it is rejected right when the proposal appears.
What is new is the addition of the ':' tag, followed by a PATTERN to
match in the FROM field of the incoming message (no spaces). Yes, it
is a pattern, not a direct callsign match, sort of a wildcard ...
You can get the test code from the rsync area as follows :
rsync -av www.langelaar.net::jnos2/newfiltercode
June 16
- nntpserv.c now contains the latest stability fixes
AND to appease the NNTP police out there ...
JNOS is getting LOTS of flack due to a recent NNTP incident where
internet
grade foul language and some very inappropriate content was channeled
into
the packet network, so I have modified the code such that JNOS will only
allow connections to NNTP servers on the 44 network.
This is supposedly 'to protect sysops from themselves' - not my words
and
not necessarily my choice, but I am really tired of this crap, maybe
more
so the 'software wars type exchanges' that ensued because of it ...
At the end of the day - we ALL make mistakes, enough said !
June 15
- Yesterday, Bob Bruninga WB4APR was kind enough to add an entry for
the NOSaprs module of JNOS 2.0 to his 'tocall' list maintained at :
http://aprs.org/aprs11/tocalls.txt
NOSaprs is now 'assigned' APN2XX, with APZ200 noted as being used by
older versions of JNOS. It's been quite some time since NOSaprs was
introduced, so it's not really experimental anymore.
Thank you Janusz HF1L (ex.SP1LOP) for suggesting this change.
The APZ200 in aprs.h is now set to APN20H
IF you have routing for 'apz200', make sure you change the apz200 to
the new 'apn20h' AFTER you have the new source in place. YES, if you
use NOSaprs to TX, use 'ax25 route' to set the APRS path, example :
# 30Dec2020, So K4KPN-10 will catch it and pass it on further
ax25 route add apz200 rp0 WIDE1-1
73 Henk.
(Message sent with Sally 7.2.051)
======================================================================
_ _ ____ __ ____ ____ _____
| | | | _ \/_ | _ \| _ \ / ____| SYS: Henk (hb1nos@hb1bbs.com)
| |__| | |_) || | |_) | |_) | (___ QTH: Ouwerkerk - JO11XO
| __ | _ < | | _ <| _ < \___ \ BBS: HB1BBS.ZLD.NLD.EU
| | | | |_) || | |_) | |_) |____) | QRV: 27.235 MHz (FM 1200bps)
|_| |_|____/ |_|____/|____/|_____/ WEB: www.hb1bbs.com
======================================================================
AXUDP : HB1BBS.NET UDP 93
APRS : APRS.HB1BBS.COM (51.37.48N : 003.59.01E)
TELNET: HB1BBS.NET 23
** Netrom/Node HB7NOD::HB7NOS (Jnos)
** Netrom/Node HB8NOD::HB8NOS (Bpq32)
** Netrom/Node HB9NOD::HB9NOS (LinBpq)
======================================================================
** This message is generated with Sally 7.2.044
----------------------------------------------------------------------
** Timed maandag 21 juni 2021 20:45 West-Europa (zomertijd)
** BBS HB2PMS@HB1BBS
Lese vorherige Mail | Lese naechste Mail
| |