| |
PY2BIL > TEST 05.12.19 00:13l 56 Lines 1876 Bytes #999 (0) @ WW
BID : 10536PY2BIL
Read: GUEST
Subj: Re: PY2BIL > F>
Path: IW8PGT<I3XTY<I0OJJ<I0OJJ<GB7CIP<N7HPX<N3DWB<LU9HGS<LU1HVK<PY2BIL
Sent: 191204/2207Z 18024@PY2BIL.SP.BRA.SOAM LinBPQ6.0.19
>From py2bil%py2bil.sp.bra.soam@i0ojj.ampr.org Wed Dec 4 23:10:42 2019
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0m) with SMTP
id AA40587 ; Wed, 04 Dec 2019 23:10:42 +0100
Message-Id: <10536PY2BIL@i0ojj.bbs>
>From: py2bil@py2bil.sp.bra.soam
X-JNOS-User-Port: Telnet (i0ojj @ 44.134.32.240) -> Sending message
+------------------------------------------------------------------------------+
Brian,
Quoting from a previous message...
> As you see, your follow up to your own bulletin was fine because it avoided
> 6.0.16 version:
Yes, I figured that out with the message exchange from yesterdaay and the fact
that it reached two divfferent nodes through different paths with different
results.
> Regardless of the reasons why it occurs, the fact of the matter is that
> it does occur. This is one of the issues that gives just cause to updating
> the BBS specs.
I took some action on it and reached out to the BPQ support forum where John
Wieseman (G8BPQ) himself mentioned that that issue was fixed already some time
ago. With that in hand I emailed VE1MPF to let him know about the issue and
suggested he considers upgrading his BPQ BBS to the latest version.
I haven't heard back from him yet, but I hope he will follow that advise.
73 to all and thanks for the support in troubleshooting this.
Guillermo/Bill (PY2BIL)
What follows is just a Tagline....
ASCII stupid question, get a stupid ANSI.
+-------------------------- SAO PAULO PACKET NODE ---------------------------+
| Grid GG66 Sao Paulo - SP - Brazil 144.390MHz |
| Sysop: PY2BIL PY2BIL.SP.BRA.SOAM py2bil@gmail.com |
+------------------------------------------------------------------------------+
(Message sent with Sally 7.2.032)
Timed 04-dez-2019 19:00 E. South America Standard Time
BBS: PY2BIL.SP.BRA.SOAM
Read previous mail | Read next mail
| |
