| |
UT1HZM > SYSOPS 31.08.12 15:55l 87 Lines 3063 Bytes #999 (0) @ WW
BID : 18924_UT1HZM
Read: GUEST
Subj: Re: Please note!
Path: IZ3LSV<DB0ERF<DB0ABZ<DK0MNL<UT1HZM
Sent: 120831/1338Z 18924@UT1HZM.KREM.POL.UKR.EU BPQ1.4.52
PE1BIV:
>But as long as I have been in Packet Radio, the address sysop has been had
>a special position and was for communication between sysop.
>messages were supposed to be send as p-mail.....
>As such I will still be sending my messages to fellow sysops using the
>address sysop@ww, eu or whichever distribution area my message would be
>intended for, and will be sending it with the p-flag set, and will not
>be sending it as a bulletin.
Sorry but I'm can not found anything about that in some "packet manuals",
maybe its common practice in the Netherlands?
SYSOP @ WW or @ EU was always Bulletin directory for info related
to sysops, same like "DX @ WW" is Bulletin directory related to DX infos...
F1OYP:
>As some other sysops said , messages adressed to a sysop ARE TO BE
>(P)ersonal simply because if you send any message in (B)ulletin @WW ,
>everybody having a permission to connect RF or telnet bbs gateways
>(whole ham community ) will read this message.
Well, your version is to hide sysops talks from non-sysop packet user.
There is really something in SYSOP topic that should
be hidden from other packet users?!
Other disadvantage to send sysop@ww as P-mail is
possibility of unproper routing.
Why? In general each BBS to route P-mail should use H-address.
But H-address of @WW is not valid for P-type message!
H-address for P-messages should consist of bbs.qth.country.continent codes.
But it could be "valid" for "next generation" sysops,
who like to flood any message to any BBS, regardless of its original
destination or message type.
That way P-message of SYSOP@WW arrives in this days...
>That's what i just wanted to do.
>That's what every sysop is doing till packet radio is alive in ham world.
But being personally in this game more than 15 years, I'm see behavior
to send SYSOP@WW as P-message only in last year or so :-)
>With the following advice you sent , now if applied , no service message
>will be sent direct to the sysop ...
System/service message generated as local P-message for given SYSOP, not @WW.
There is no problem. Moreover, most proper BBS software have option to copy
SYSOP bulls to the Private message directory of sysop!
Operator need to activate it, and will receive copy of SYSOP bulls to own
private directory, if need.
IW5BEM:
>If you write a message to SP SYSOP only the Sysop of the system can read it,
>if you write SB SYSOP all people can read it ..........
You right. SP SYSOP used to send message for the sysop of some given BBS,
not to all sysops...
So again:
SP SYSOP to send message to operator of particular BBS used at time of write;
SP SYSOP @ something like WW, EU etc - is not correct;
SB SYSOP without @ (at field) have not sence as normally
not go outside of given bbs;
SB SYSOP @ WW - message to sysops topic around the World;
SB SYSOP @ EU - same for EU sysops;
SB SYSOP @ ITA - topic for Italian sysops.
etc...
73, Sergej.
P.S. This topic was intended to send as sysopS @ WW to get replys as bulletin,
not that "new style" to reply to sysop@ww message as P-type.
Read previous mail | Read next mail
| |
