| |
N2NOV > BPQ 29.08.18 13:01l 22 Lines 1202 Bytes #999 (0) @ WW
BID : 81550_N2NOV
Read: GAST
Subj: WP Forwarding As Bulletins
Path: DB0FFL<OE5XBL<F1OYP<ON0AR<GB7CIP<N2NOV
Sent: 180829/1005z @:N2NOV.#RICH.NY.USA.NOAM [NYC] [JNOS] #:81552 $:81550_N2NOV
>From n2nov@n2nov.ampr.org Wed Aug 29 06:05:01 2018
Received: from n2nov.ampr.org by n2nov.ampr.org ([JNOS]) with SMTP
id AA481552 ; Wed, 29 Aug 2018 06:05:01 EDT
Message-Id: <481550@n2nov.ampr.org>
>From: n2nov@n2nov.ampr.org
X-JNOS-User-Port: Telnet (n2nov @ 86.41.253.84) -> Sending message
It seems that the sysops of the various BPQ systems do not have the
WP forwarding filters set properly. Recently, two Arkansas stations
that send out WP messages as bulletins instead as private messages to
their forwarding partners are again cropping up in my hold area. WP
messages should never be sent as a bulletin to @WW, @EU, etc as it
just clutters up the airwaves. The way the WP databases work in the
various BBS packages is to send and receive ONLY to/from your partners.
There is no reason for my system in NYC to be flooded with WP messages
from far away places. Since previous comments about this topic last
year and this past Spring, this has dropped off considerably as it
properly should have. Lately, I am seeing it pop up again with the
two stations in Arkansas, USA and am concerned that the BPQ community
as a whole might have something set wrong in their configuration files.
Lese vorherige Mail | Lese naechste Mail
| |
