| |
DM3TT > SYSOP 23.07.11 11:05l 101 Lines 3825 Bytes #999 (0) @ BAYCOM
BID : 34679-TA2BBS
Read: GUEST
Subj: Corr. BIN MSGS SR1BSZ > WA7V
Path: IZ3LSV<IK2XDE<DB0RES<DB0OSN<DB0PDF<TA2BBS
Sent: 110723/0859Z @:TA2BBS.#ANK.TUR.EU [Ankara] HFPR/PTOR XFBB7.04j $:34679-TA
From: DM3TT@TA2BBS.#ANK.TUR.EU
To : SYSOP@BAYCOM
Hello BCM sysops
There is a problem when forwarding messages with a full 8bit Autobin content
from BCM to any BBS such as FBB, xNOS etc. which are not Autobin capable.
Such data will be corrupted since FBB etc. can't handle such contents 8 bit
transparently and Autobin featured terminals can't decode these messages
later any more.
Here's a recent example
>R:110722/1822Z @:CX2SA.LAV.URY.SA #:17816 [Minas] FBB7.00e $:LOQTRP_DB0LJ
>R:110722/1810Z @:WA7V.#SEWA.WA.USA.NOAM #:56798 [C-Basin Hub] $:LOQTRP_DB0LJ
>R:110722/1809z @:SR1BSZ.SZ.POL.EU $:LOQTRP_DB0LJ
>R:110722/1816z @:IV3SCP.IFVG.ITA.EU $:LOQTRP_DB0LJ
>R:110722/1809z @:IW0QNL.IUMB.ITA.EU $:LOQTRP_DB0LJ
>R:110722/1810z @:IZ3LSV.IVEN.ITA.EU $:LOQTRP_DB0LJ
>R:110722/1808z @:DB0ERF.#THR.DEU.EU [Erfurt DL3AMi] DP6.00 $:LOQTRP_DB0LJ
>R:110722/1807z @:DB0FBB.#NRW.DEU.EU
>R:110722/1805z @:DB0IUZ.#NRW.DEU.EU $:LOQTRP_DB0LJ
>R:110722/1730z @:DB0GOS.#NRW.DEU.EU $:LOQTRP_DB0LJ
>R:110722/1805z @:DB0EEO.#NRW.DEU.EU $:LOQTRP_DB0LJ
>R:110722/2007z @:DB0RES.#NRW.DEU.EU $:LOQTRP_DB0LJ
>R:110722/1805z @:DB0OVN.#NRW.DEU.EU $:LOQTRP_DB0LJ
>R:110722/1643z @:DB0LJ.#RPL.DEU.EU [Mayen-KO,JO30QJ] DP6.00 $:LOQTRP_DB0LJ
>From: DL8KN @ DB0LJ.#RPL.DEU.EU (Peter)
>To: BILDER @ WW
>X-Info: Upload without password authentication
>
>#BIN#58272#|51091#$3EF68C2F#Bluete-Trichterblume.jpg
corrupted 8bit data starts here
Therefore, it is not recommended to offer such traffic from any BCM to
any non-BCM, non-DPBOX or non-DIEBOX software
The option -i was implemented in BCM for testing purposes only and is
usesless since Autobin capabilty is indicated by the letter D in the BBS SID.
Autobin capabilty can be negotiated between both BBS themselves without any sysop
configuration.
[OpenBCM-1.06b58-AB1D1FHMRW$]
^^ OK
[DP-6.00-AB1D1FHMRW$]
^^ OK
[FBB-7.04j-AB1FHMR$]
see no "D" here.
That means NEVER USE OPTION -I IN FWD.BCM AT ALL !
The sysop of SR1BSZ is to remove -I at the section for WA7V in FWD.BCM in
this case, pse.
See the BCM/openbcm manual, enter HELP OPTION FORWARD at the BCM BBS prompt.
::::::::::::::::::::
:: OPTION FORWARD ::
::::::::::::::::::::
These are all possible S&F options:
-b<bytes> maximum size of forward mails ( > 10k)
-d (delay) S&F only at set times of "crontab.bcm"
-e send E/M files with 4 lines in 1 frame (e.g. DB0SAO)
-f send empty line before start S&F (e.g. xNOS)
-i BoxBin mails are forwarded regardless of the capabilites of ***
the receiving system (not useful in most cases) ***
-k no forward of autobin bulletins
-l no forward of autobin user mails
-m no forward of 7plus bulletins
-n no forward of 7plus user mails
-o entries are sorted by size (smallest at first)
-p suppress prompt after login (e.g. needed for DB0SAO)
-r send ONLY bulletins from "fwd.bcm" to S&F partner
-s SID is send immediately of connected BBS
-t tracing active (if "fwdtrace 2" is set)
-u connection is closed immediately, without this parameter S&F
is waiting for some time if new mails can be forwarded
Note: You should use option "-l" and "-k" ONLY in that case, if S&F partner
can't handle 7plus or autobin mails, like shortwave gateways. Don't restrict
user mails without reason!
Parameter "-b" makes only sense, if S&F partner only supports ASCII S&F
protocol (from WA7MBL). Internally OpenBCM limits the size of one mail at the
moment to 10 MBytes. Every option must be separated through spaces, if
you use more than one.
See also HELP FWDTIMEOUT, HELP FWDTRACE and HELP FWDSSID.
-- end of quote --
73 Thomas
DM3TT@DB0LJ.#RPL.DEU.EU
/ack
Read previous mail | Read next mail
| |
