| |
K5DAT > 7PLUS 10.04.26 15:34l 25 Lines 835 Bytes #999 (0) @ WW
BID : 32454_K5DAT
Read: DJ6UX DL5MBW GUEST
Subj: Re: 7+ diamon~1.jpg 19/26 from VK2SX
Path: DB0FHN<OE2XZR<OK1TOR<SR6DWH<SR8BBS<SR1BSZ<EA2RCF<LU9DCE<VE3CGR<PI8ZTM<
IW2OHX<K5DAT
Sent: 260410/1256Z 32454@K5DAT.#NEWI.WI.USA.NOAM LinBPQ6.0.25
The first R line in these 7plus messages, which I assume
is created by the Sally7 PMS, is creating a problem with
WP updates. The "Sally" in the line below is interpreted
as a callsign - at least it is by BPQ - and the result
is a WP update that is sent using "SALLY" as the callsign.
> R:260410/1254 @:Sally 7.2.061 [Local] $:751VK2SX
Looking at the next R lines in the message for comparison,
it appears that "Sally 7.2.061" is in the wrong place, i.e.
it's in the area that normally applies to the address.
R:260410/1111Z 21806@GB7JED.#71.GBR.EURO LinBPQ6.0.25
R:260410/1108Z @:GB7CIP.#32.GBR.EURO #:56901 [Caterham Surrey GBR] $:770VK2SX
There appears to be a fair amount of leeway regarding what
comes after the address, but the address following the "@"
seems to be consistent across various BBS software.
73,
Lee K5DAT
Read previous mail | Read next mail
| |
