OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
G8PZT  > PACKET   27.12.13 08:41l 30 Lines 1294 Bytes #999 (0) @ WW
BID : 000078360PZT
Read: GUEST
Subj: Dupe bulls
Path: IZ3LSV<ED1ZAC<VK2DOT<GB7PZT
Sent: 131227/0738Z @:GB7PZT.#24.GBR.EU [Kidderminster] #:7800 XSERV500f
Date: Fri, 27 Dec 2013 07:38:56 +0000
From: g8pzt@gb7pzt.#24.gbr.eu (Paula)
To: packet@ww

Subject: Dupe bulls

With reference to VK2AWZ's comments about XS32 causing duplicate bulletins,
I would like to draw his and your attention to ZL2BAU BBS numbers 474282
and 475291, which are duplicates. One had passed through VK2DOT, which runs
XS32 BBS, and the other had not.

Both bulletins have the same BID on ZL2BAU. This should not be possible,
as BBS's are supposed to refuse a bull if they already have the BID.

The second pair of dupes are numbers 475323 and 475333. Both of these traversed VK2DOT and GB7PZT, which both run XS32 BBS software. However there is only
one copy on each XS32 BBS. The nmessage was forwarded from VK2DOT to ZL2BAU and
N9PMO, and it then went via a few others before being offered by a French
BBS to ZL2BAU a second time. ZL2BAU already had the message, but somehow
managed to accept it a second time.

No doubt I could find other examples, but I think two are enough to make my
point that XS32 is not at fault here.

Or does anyone more knowledgable than me have evidence to the contrary?

XS32 as a Windows BBS is still in beta test, but the code is a direct port of
the 16 bit version which has been in full service for as long as FBB.

73 Paula

G8PZT @ GB7PZT


Read previous mail | Read next mail


 06.11.2024 12:16:07lGo back Go up