| |
I0OJJ > JNOS2 31.10.19 19:34l 42 Lines 1229 Bytes #-2372 (0) @ WW
BID : 29306I0OJJ
Read: DF7EAV DJ6UX GUEST
Subj: Re: Re: I0OJJ > JNOS2 2.0M (beta) Oct 29, 2019,>
Path: DB0FHN<DB0BLO<DB0ERF<DB0RES<IR2UBX<IW8PGT<I3XTY<I0OJJ
Sent: 191031/1715z @:I0OJJ.ITA.EU [Rome] #:30781 $:29306i0ojj
Brian et al,
> Date: 31 Oct 19 13:00:00 GMT
> From: n1uro@n1uro.#cct.ct.usa.noam
> To: jnos2@ww
> Subject: Re: I0OJJ > JNOS2 2.0M (beta) Oct 29, 2019
> Gus et al;
>
>> a new bug was introduced on the subject 'beta' release:
>> in practice it is not possible anymore to upload any msgs
>> with any address to JNOS2.
>
> What you think is a bug, is in reality proper behavior.
>
>> I want to specify that no troubles was experienced on
>> previous JNOS2 versions.
>
> This is because prior to the fix, JNOS2 would insert it's own BID upon
> receipt of a message without a bid which is why there were so many BID
> changes by AA6HF and N9LYA. Now this no longer occurs and dupes are
> halted.
Nope, my two last bulletins sent toward LinFBB
and obcm PBBSs (which are almost standard in
a pure packet-radio environment) since they
were without a BID, the above system generate
one for each message and then forwarded the
Bulletins as stated from the protocol.
Note that the above process is the same as
per Users as per declared PBBSs callsigns
accessing LinFBB and obcm PBBSs.
The above mensioned AA6HF and N9LYA systems
are or out control or mis-configured as per
my opinion.
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
Read previous mail | Read next mail
| |
