| |
N2NOV > SYSOP 25.11.22 01:54l 39 Lines 1423 Bytes #999 (0) @ WW
BID : 6ZCJ_N2NOV
Read: GUEST
Subj: Fwd: Non-delivery Notification
Path: IW8PGT<I3XTY<I0OJJ<LU4ECL<VE2PKT<N2NOV
Sent: 221125/0051z @:N2NOV.#RICH.NY.USA.NOAM $:6ZCJ_N2NOV
>From n2nov@n2nov.ampr.org Thu Nov 24 19:51:27 2022
Received: from n2nov.ampr.org by n2nov.ampr.org (JNOS2.0n.dev) with SMTP
id AA325747 ; Thu, 24 Nov 2022 19:51:27 EST
Message-Id: <325745@n2nov.ampr.org>
>From: n2nov@n2nov.ampr.org
X-JNOS-User-Port: Telnet (n2nov @ 44.68.41.2) -> Sending message
The BPQ sysops really need to get a handle on this message deletion thing.
A private message or a bulletin like this one gets deleted on many BPQ
systems in anywhere from zero to 60 days as "could not be delivered".
Some thought that a bulletin was being changed into a private message,
but I think that it is something else going on here. I sent a private
message to YT7MPB in response to a bulletin questioning the whereabouts
of a former contact and it comes back the same day as not delivered?
Really? This should be looked at by all BPQ experts and John himself.
-------- Forwarded Message --------
Subject: Non-delivery Notification
Date: 24 Nov 22 13:23:00 GMT
From: yt7mpb@yt7mpb.#nsd.srb.eu
To: n2nov@n2nov.#rich.ny.usa.noam
R:221124/1415Z @:GB7CIP.#32.GBR.EURO #:34022 [Caterham Surrey GBR]
R:221124/1323Z 56385@YT7MPB.#NSD.SRB.EU LinBPQ6.0.23
Your Message ID 6Z52_N2NOV Subject Re: Presley, N5VGC to YT7MPB could not be delivered in 0 days.
Message had been deleted.
--
73 de N2NOV
n2nov@n2nov.ampr.org
n2nov@n2nov.#rich.ny.usa.noam
--
73 de N2NOV
n2nov@n2nov.ampr.org
n2nov@n2nov.#rich.ny.usa.noam
Read previous mail | Read next mail
| |
