| |
ZL2TZE > WNLK2 28.12.00 17:02l 45 Lines 1335 Bytes #999 (0) @ WW
BID : 59285-ZL2TZE
Read: GUEST DO5JAB
Subj: Is Winlink 2000 Responsibe ?
Path: DB0ABH<DB0RGB<DB0MRW<DB0ERF<DB0SHG<DB0FC<DF0HMB<DB0HHW<DB0IL<OZ5BBS<
OZ4PAC<OZ2BOH<OZ2DIZ<7M3TJZ<HA3PG<PP5BLU<PY3KW<ZL2TZE
Sent: 001228/0855Z @:ZL2TZE.#73.MLB.NZL.OC #:59285 $:59285-ZL2TZE
From: ZL2TZE@ZL2TZE.#73.MLB.NZL.OC
To : WNLK2@WW
[fbb] H Route Change
Have any other FBB operators noticed that the H route addresses are
being changed ?
I have received a number of messages that have had the original H
address changed like this;
<addressee>@FK8KAB.#NEA.NCL.OC being changed to
<addressee>@VK2AAB.FK8KAB.#NEA.NCL.OC
another example
ZL2TZE@ZL2TZE.#73.MLB.NZL.OC being changed to
ZL2TZE@VK2AAB.ZL2TZE.#73.MLB.NZL.OC
They generated Unknown Route messages on my BBS. I listed the
messages and the @BBS was @VK2AAB.
I changed this to the appropriate BBS and off they went.
Phillip ZL2TZE informs me that the return address of the message he
received was VK2AAB. It has not corrupted my White Pages but may have
corrupted Phillips. With the next one I'll check the white pages before
I edit it. If it is corrupting white pages we could be in for some
trouble.
The common factor in these messages seems to be Winlink 2000 BBSs. I
suspect that this is happening when a message has an @BBS not known to
the Winlink BBS it inserts the callsign of a BBS in the continent known
to it. Not certain about this at all, but it would fit the evidence as
every message to which this has happened has come through a Winlink BBS
to which I forward.
Does anyone know what is going on ?
Barry VK2AAB
Read previous mail | Read next mail
| |
