| |
I0OJJ > SYSOP 16.12.22 00:34l 36 Lines 1368 Bytes #999 (10) @ WW
BID : FCWI0OJJ_00H
Read: GAST
Subj: Re: Fwd: More on
Path: DB0FFL<DB0FHN<DB0RBS<DB0ERF<IZ3LSV<I0OJJ
Sent: 221215/2030z @:I0OJJ.ITA.EU [Rome] obcm1.08-5-g2f4a LT:010
From: I0OJJ @ I0OJJ.ITA.EU (Gustavo)
To: SYSOP @ WW
X-Info: Sent with login password
Hi all,
while the following statements are correct, other PBBS SW following
the F6FBB implementation gave the possibility to generate to Sysop/
Co-Sysop callsign(s) other copies of SP message(s), so, where that
last messages are not read by Sysops concerned--- other no-delivery
are created (clearly that is a bug).
However, *almost all* PBBS SW generate an 'acknowledgement message'
to Sender, when receive a SP mail having an '/ACK' at beginning of
a new line... also this last practice is almost forgotten :)
73, gustavo
>Hello Sergej,
>
>I understand your opinion, but my view is different:
>
>In my knowledge, sending SP SYSOP@WW mails was established long ago with
>an intention that bbs admins have their 'private' way to communicate in
>between themselves. Without end users to read such mails. Why? Because
>of potential 'revenge', and/or further hacking, ham pirate behavior, etc.
>
>In that direction, most (if not all) bbs software were supposed to
>process such SP (private) mails as those intended for local sysops only.
>
>So, if you ask me, I would never report an abuse in packet network (or
>some 'bad user' behavior) publicly in a bulletin *before* I discuss a
>particular problem in the closed circle of bbs administrators :-)
>
>73, Misko
Lese vorherige Mail | Lese naechste Mail
| |
