| |
AL0Y > SYSOP 28.12.20 21:00l 45 Lines 1752 Bytes #999 (0) @ WW
BID : 1895_AL0Y
Read: GUEST
Subj: WP updates as B messages
Path: IW8PGT<HB9ON<IW2OHX<UA6ADV<LU4ECL<VK2RZ<W0ARP<AL0Y
Sent: 201228/1732Z @:AL0Y.#NNJ.NJ.USA.NOAM #:1895 [WAYNE-NJ-USA] $:1895_AL0Y
From: AL0Y@AL0Y.#NNJ.NJ.USA.NOAM
To : SYSOP@WW
Hello, all SYSOPs..
Happy new year...
I would like to remind you all that WP update messages should not be sent as B
messages
and definetly not to WW, USA, EU or the likes...
WP messages should be always sent as P messages to your forwarding partners who
will then process
these updates and send them to their partners and so on.
There is no logic in sending it to WW.
I have setup my BBS to actually reject any WP message that is sent as B.
These messages will not be accepted when proposed to my BBS and will not be
re-forwarded..
however, because they are addressed as B to WW, they propably will still travel
the whole network
and flood it with unprocessable messages.
I will quote the following from a Bull sent previously by N2NOV:
From n2nov@n2nov.ampr.org Mon Aug 14 13:55:39 2017
I am seeing WP BULLETINS being sent out (ie: WP@EU, WP@WW, WP@ALL, etc)
when they should actually be sent as private messages to your forwarding
partners. Not all systems are running a White Pages server and some
have no idea what to do with these received bulletins. When your system
runs a White Pages service (available for many systems like JNOS/FBB/etc)
then the private WP messages from your forwarding partner is automatically
incorporated into your database. When the message is sent as a bulletin,
it is not. Let's all get on board with the White Pages service on our
systems and provide this useful feature to the users worldwide.
Thanks, N2NOV for this comment. I couldn't agree more.
If anyone needs help with setting this up in BPQ or in FBB, please reach out to
me
and I will gladly help with that. I am sorry I am not familiar with any other
BBS sysetm tho.
73 and happy new year
AL0Y
Read previous mail | Read next mail
| |
