| |
I0OJJ > SYSOP 05.10.20 23:00l 72 Lines 2526 Bytes #999 (0) @ WW
BID : 5AUI0OJJ_00D
Read: GUEST
Subj: Re: Dupe/Triplicates
Path: IW8PGT<IZ3LSV<I0OJJ
Sent: 201005/2100z @:I0OJJ.ITA.EU [Rome] obcm1.08-5-g2f4a
From: I0OJJ @ I0OJJ.ITA.EU (Gustavo)
To: SYSOP @ WW
X-Info: Sent with login password
X-Info: Received by SMTP-gateway
On 10/5/20 9:18 PM, n1uro@n1uro.#cct.ct.usa.noam wrote:
> R:201005/1920z @:I0OJJ.ITA.EU $:54167_N1URO
> R:201005/1918Z @:GB7CIP.#32.GBR.EURO #:8422 [Caterham Surrey GBR] $:54167_N1URO
> R:201005/1918Z @:N1URO.#CCT.CT.USA.NOAM #:54167 [Unionville] $:54167_N1URO
>
> From: N1URO@N1URO.#CCT.CT.USA.NOAM
> To : SYSOP@WW
>
> MSYS is great for showing issues with bids:
>
> [MSYS-1.20beta4-BFHI$]
>>
> r+
> MSG # TR SIZE TO FROM @BBS DATE TITLE
> 15155 BH 1225 JNOS2 I0OJJ WW 201005 Re: help dyndns
> Forwarding path: N1URO N1URO I0OJJ I0OJJ
> This bulletin has same title and from call as msg 15154 with bid 25014_AA6HF
> size 1954 going to JNOS2@WW and may be a duplicate with altered bid
> BID='5AUI0OJJ_008'
> Kill, Hold, $ for bulletin, # for forwarded, N for personal, Read, or Abort?
> k
> Msg 15155 Killed
> MSG # TR SIZE TO FROM @BBS DATE TITLE
> 15154 BH 1954 JNOS2 I0OJJ WW 201005 Re: help dyndns
> Forwarding path: N1URO GB7CIP GB7YEW KE0GB KF6NMZ AA6HF N2NOV VE3CGR
> I0OJJ
> R: lines suggest bid has been altered at this line:
> R:201005/1621z @:N2NOV.#RICH.NY.USA.NOAM #:68580 $:4476e_I0OJJ
> ^ lower case?
> BID='25014_AA6HF'
> Kill, Hold, $ for bulletin, # for forwarded, N for personal, Read, or Abort?
>
> Note: BIDs are required to be all in CAPS since this is how DOS handled
> BIDs in the earlier days of packet. When they're not seen in the proper
> format, it's as good as if no BID exists during forwarding.
>
> 73
> ---
> SendBBS v1.1 by N1URO for LinFBB
nope, again :)
now we are in the linux era and so BIDs should be managed in
the *original* format lower or caps and not swapped all in
caps, so apart the aged DOS/WIN, not more recoverable, this
bug should be corrected at least in LinFBB which is in
current development.
NOTE for Maiko VE4KLM:
^^^^^^^^^^^^^^^^^^^^^
since PBBS softwares other then (x)NOS and obcm/dptnt/thebox
etc., are swapping the BID in CAPS, and so when the JNOS2
receive the same message in this format it is recognized as
a new msg and then it is normally queued... and a dupe occour(?)
to modify this area in JNOS2 in the way that:
if the JNOS2 *receives* a BID abcde_I0OJJ or a BID ABCDE_I0OJJ
the two MUST BE considered as the same BID so, the second msg
received MUST BE rejected as a duped msg...
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
Read previous mail | Read next mail
| |
