OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

IW8PGT

[Mendicino(CS)-Italy]

 Login: GUEST





  
I0OJJ  > SYSOP    25.11.19 22:15l 54 Lines 1710 Bytes #999 (0) @ WW
BID : PBTI0OJJ_005
Read: GUEST
Subj: Re: Duplicate bulls bid AA6HF
Path: IW8PGT<IR2UBX<IW2OHX<IR1UAW<IQ5KG<I0OJJ
Sent: 191125/2113z @:I0OJJ.ITA.EU [Rome] obcm1.08-3-g9b42
From: I0OJJ @ I0OJJ.ITA.EU (Gustavo)
To:   SYSOP @ WW
X-Info: Sent with login password
X-Info: Received by SMTP-gateway

Hi all,

> R:191125/1325Z @:CX2SA.SAL.URY.SOAM #:19665 [Salto] FBB7.00e $:19665_CX2SA
> From: CX2SA@CX2SA.SAL.URY.SOAM
> To  : SYSOP@WW
> 
> Hello Sysop!
> Please check your systems.
> Duplicate messages have appeared on the network.
> I have 126 bulletines with BID changed to AA6HF
> Momentarily I have put all messages with BID AA6HF in reject.sys
> Now I'm deleting each bull :(
> 
> 73, Jose

such a problems arose from time to time for
several reason. Analyzing the mass of bulletins
arrived I observed some causes of this last
trouble; at least, mainly depends upon no purged
systems as indicated by Brian; the JNOS as
per the original project was not structured in
various kinda mode as the new PBBS systems.
So, the JNOS 'areas' need to be expired to
maintain a reasonable number of mails (SP
and SB) and so low sizes of *.txt files.

In this case, the systems concerned, have to
restart a 'virgin' copy of software, no way
for doing things right :)

Then note also some swapping of senders/BBSs
and re-bidding... a true catastrophe !

Apropos of 'duplicate' I note a revival of
doubled or tripled kinda traffic such as
keps, equake, dxnews, humor, weather, etc
so, there must be a minimum of common sense,
at lest that if one historically manage
an area, another sysop should not duplicate
that/those areas already served. or not?

So, since the matter can not be mitigated
(in practice it is so) I begin to put in
reject not only the dangerous WP traffic
and occasional BID/MIDs, but also almost
any doubled or unnecessary stuff...

-- 
73 and ciao, gustavo i0ojj/ir0aab/ir0eq



Read previous mail | Read next mail


 23.12.2024 17:19:15lGo back Go up