| |
YT7MPB > SYSOP 15.12.22 15:53l 128 Lines 3658 Bytes #999 (0) @ WW
BID : 56906_YT7MPB
Read: GUEST
Subj: Fwd: More on "Non-delivery Notification"
Path: IW8PGT<I3XTY<I0OJJ<N6RME<YT7MPB
Sent: 221215/1350Z 56906@YT7MPB.#NSD.SRB.EU LinBPQ6.0.23
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
-------- Forwarded Message --------
Subject: More on "Non-delivery Notification"
Date: Tue, 13 Dec 22 09:00:00 Z
From: UT1HZM <>
Newsgroups: SYSOP.WW
R:221213/1030Z @:N6RME.#NCA.CA.USA.NOAM #:2997 [El Dorado] $:16568_UT1HZM
R:221213/1026Z @:CX2SA.SAL.URY.SOAM #:20169 [Salto] FBB7.00e $:16568_UT1HZM
R:221213/1026Z 46964@N9PMO.#SEWI.WI.USA.NOAM BPQ6.0.23
R:221213/1025Z 22136@VE3UIL.#EON.ON.CAN.NA LinBPQ6.0.23
R:221213/1025Z 8409@LU9DCE.TOR.BA.ARG.SOAM LinBPQ6.0.23
R:221213/1023Z 45337@PY2BIL.SP.BRA.SOAM LinBPQ6.0.23
R:221213/1000Z 7844@EI2GYB.DGL.IRL.EURO BPQ6.0.23
R:221213/0900Z 16568@UT1HZM.KREM.POL.UKR.EU BPQ6.0.23
Hello, Misko, Jose and all sysops!
>"Send Non-delivery Notifications
>for P and T messages"
>
>It was enabled previously. Now it is not. Try to resend the mail that
>bounced back. Tnx!
>
>73, Misko YT7MPB
>
>
>From: CX2SA@CX2SA.SAL.URY.SOAM
>To : SYSOP@WW
>
>Stations that send Non-delivery Notification message are placed in my
>reject file.
Please note that disabling "send non-delivery" or banning stations of
originals of that messages is not the solution!!!
Disabling will destroy the non-delivery notifications system for P-mails,
its well done system like in classic internet e-mails.
Don't disable that!
Also banning (rejecting) not effective.
Simply, that station may not be responsible for the cause of these messages!
The root of problems could be other:
when someone send message to sysop@ww and sent it by error not as
Bulletin, but like 'SP sysop@ww' or 'S sysop@ww' !
SP - should be only used to send P-mail directly to usercall @
bbscall.h.addr.es
BBS software threads that wrong 'SP sysop@ww' like personal message,
and when there is non-exist real user with callsign "sysop" - it will
generate
non-delivery message, after some time, ofcourse...
Its normal behavior of non-deliv. system.
Someone says that problem of BPQ bbs, its not right!
Just look below for the same behavior of FBB software.
CX4AE uses FBB s/w, not BPQ...
So again, when sent message to sysop@ww, always check to be SB or bull,
not SP (not P-message) !
73, Sergej.
16321 27-Nov PN 692 UT1HZM @UT1HZM CX4AE Undelivered mail in CX4AE
de UT1HZM>
r 16321
From: CX4AE
To: UT1HZM
Type/Status: PN
Date/Time: 27-Nov 22:01Z
Bid: 27578_CX4AE
Title: Undelivered mail in CX4AE
R:221127/2225Z @:F3KT.FPDL.FRA.EU #:21956 [Pont Saint Martin] LFBB7.7-beta3
R:221127/2224Z @:F3KT.#44.FPDL.FRA.EU #:14999 [Pont Saint Martin] LFBB7.07
R:221127/2210Z @:CX2SA.SAL.URY.SOAM #:19424 [Salto] FBB7.00e $:27578_CX4AE
R:221127/2201Z @:CX4AE.MVD.URY.SA #:27578 [Montevideo] FBB7.00e
$:27578_CX4AE
From: CX4AE@CX4AE.MVD.URY.SA
To : UT1HZM@UT1HZM.KREM.POL.UKR.EU
CX4AE BBS, Sun Nov 27 19:01:28 2022
** MENSAJE NO ENVIADO POR BBS AUSENTE AL FWD **
SP CX4AE @ CX4AE.CAN.URY.SA < UT1HZM
CP SYSOP: Re: Useless Non-Delivery Notifications
Original to SYSOP@WW
Path: !CX2SA!OK2PEN!OK0PBR!UT1HZM!
Read previous mail | Read next mail
| |
