found something else...

[mark lewis]

what i'm showing is what is on the conio output... i don't understand what is
at the end...

+ 20:46 [43957] incoming session with 71.234.229.39 (21218)
- 20:46 [43957] SYS Bits & Bytes BBS
- 20:46 [43957] ZYZ Andrew Leary
- 20:46 [43957] LOC North Stonington, CT USA
- 20:46 [43957] NDL 115200,IBN,ITN,IVM,INA:bnbbbs.net
- 20:46 [43957] TIME Mon, 18 Jun 2012 19:41:52 -0400
- 20:46 [43957] VER binkd/1.0a-608/OS2 binkp/1.1
+ 20:46 [43957] addr: 1:320/***@fidonet
+ 20:46 [43957] addr: 1:320/***@fidonet
+ 20:46 [43957] addr: 1:16/***@fidonet
+ 20:46 [43957] addr: 10:10/***@league10.org (n/a or busy)
+ 20:46 [43957] addr: 10:3000/***@league10.org (n/a or busy)
+ 20:46 [43957] addr: 10:3000/***@league10.org (n/a or busy)
+ 20:46 [43957] addr: 33:860/***@advnet (n/a or busy)
+ 20:46 [43957] addr: 33:860/***@advnet (n/a or busy)
+ 20:46 [43957] addr: 110:212/***@linuxnet (n/a or busy)
+ 20:46 [43957] addr: 110:212/***@linuxnet (n/a or busy)
+ 20:46 [43957] addr: 111:4950/***@stn (n/a or busy)
+ 20:46 [43957] addr: 111:4950/***@stn (n/a or busy)
+ 20:46 [43957] addr: 111:4950/***@stn (n/a or busy)
+ 20:46 [43957] addr: 618:100/***@micronet (n/a or busy)
+ 20:46 [43957] addr: 618:100/***@micronet (n/a or busy)
+ 20:46 [43957] addr: 618:100/***@micronet (n/a or busy)
+ 20:46 [43957] addr: 618:10/***@micronet (n/a or busy)
+ 20:46 [43957] addr: 92:762/***@zenet (n/a or busy)
+ 20:46 [43957] addr: 92:762/***@zenet (n/a or busy)
+ 20:46 [43957] addr: 92:762/***@zenet (n/a or busy)
+ 20:46 [43957] addr: 510:269/***@justanet (n/a or busy)
+ 20:46 [43957] addr: 510:269/***@justanet (n/a or busy)
+ 20:46 [43957] addr: 510:5112/***@justanet (n/a or busy)
+ 20:46 [43957] addr: 115:1502/***@pascalnet (n/a or busy)
- 20:46 [43957] OPT NDA EXTCMD CRYPT GZ BZ2
+ 20:46 [43957] Remote supports asymmetric ND mode
+ 20:46 [43957] Remote supports EXTCMD mode
+ 20:46 [43957] Remote requests CRYPT mode
+ 20:46 [43957] Remote supports GZ mode
+ 20:46 [43957] Remote supports BZ2 mode
- 20:46 [43957] TRF 0 0
+ 20:46 [43957] Remote has 0b of mail and 0b of files for us
+ 20:46 [43957] pwd protected session (MD5)
- 20:46 [43957] session in CRYPT mode
+ 20:46 [43957] done (from 1:320/***@fidonet, OK, S/R: 0/0 (0/0 bytes)
+ 20:46 [43957] done (from 1:320/***@fidonet, OK, S/R: 0/0 (0/0 bytes))
20:46 [43957] session closed, quitting...
20:46 [33936] rc(43957)=0
$ -- 1:16/***@fidonet busy
-- 1:320/***@fidonet busy
-- 1:320/***@fidonet busy
-- 1:16/***@quartz busy
-- 1:320/***@quartz busy
-- 1:320/***@quartz busy

here we see the end of a connection with 1:320/119 and we see scans for their
zone 1 addresses but then we also see scans for those same addresses in another
domain which has a completely different zone (1234)... my config has this...

root-domain binkp.net
domain fidonet x:\\bink\\outbound 1
domain quartz x:\\bink\\outbound 1
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet
domain quartz.net alias-for quartz

should that first quartz definition line have 1234 instead of 1?

in my hybrid environment, my mail tosser does frontdoor dynamic and static
queue outbounds with another tool then "converts" to BSO (via fileboxes mostly)
so i'm just needing to get this figured out what binkd wants and i'll make
everything else (scripts mainly) conform ;)

)\/(ark

[Stas Degteff]

Hello mark.

18 Jun 12 20:52, you wrote to all:

ml> rc(43957)=0 $
ml> -- 1:16/***@fidonet busy
ml> -- 1:320/***@fidonet busy
ml> -- 1:320/***@fidonet busy
ml> -- 1:16/***@quartz busy
ml> -- 1:320/***@quartz busy
ml> -- 1:320/***@quartz busy

ml> here we see the end of a connection with 1:320/119 and we see scans
ml> for their zone 1 addresses but then we also see scans for those same
ml> addresses in another domain which has a completely different zone
ml> (1234)... my config has this...

ml> root-domain binkp.net
ml> domain fidonet x:\\bink\\outbound 1
ml> domain quartz x:\\bink\\outbound 1

two domains pointed to one directory => binkd scans this directory twice. This
is normal if your tosser don't support 5D FTN addressing scheme


Stas
Jabber-ID: ***@grumbler.org
GPG key 0x72186DB9 (keyserver: hkp://wwwkeys.eu.pgp.net)
... Golded+, Husky & RNTrack maintainer, Binkd developer&webmaster

[mark lewis]

ml> root-domain binkp.net
ml> domain fidonet x:\\bink\\outbound 1
ml> domain quartz x:\\bink\\outbound 1

SD> two domains pointed to one directory => binkd scans this directory
SD> twice. This is normal if your tosser don't support 5D FTN
SD> addressing scheme

thanks... that is what i thought... however, my tosser doesn't enter into this
mix... my tosser doesn't even know about the bink side of my setup... the tool
i use to move files into and out of the bink directories is manually configured
for each one so anything goes as it is only concerned with the directory names
and not their layout...

how should the above be if there is a 5D capibility? just change the quartz
line to have that network's zone at the end of the line and then the files
would go into outbound.f00 or whatever the hex is for that zone's number?

how do i tell binkd what zones are covered by the quartz network? fidonet has 1
thru 6 and i guess that is hardcoded? what about others?

)\/(ark

[Stas Degteff]

Hello mark.

23 Jul 12 19:42, you wrote to me:

ml>> root-domain binkp.net
ml>> domain fidonet x:\\bink\\outbound 1
ml>> domain quartz x:\\bink\\outbound 1

SD>> two domains pointed to one directory => binkd scans this
SD>> directory twice. This is normal if your tosser don't support 5D
SD>> FTN addressing scheme

ml> thanks... that is what i thought... however, my tosser doesn't enter
ml> into this mix... my tosser doesn't even know about the bink side of my
ml> setup... the tool i use to move files into and out of the bink
ml> directories is manually configured for each one so anything goes as it
ml> is only concerned with the directory names and not their layout...

ml> how should the above be if there is a 5D capibility? just change the
ml> quartz line to have that network's zone at the end of the line and
ml> then the files would go into outbound.f00 or whatever the hex is for
ml> that zone's number?

The number on the last position of the "domain" line specifies a default zone
number of the domain (bequest of a 2D/3D-addressing schemes). You may use a
directory set x:\bink\outbound\fidonet.XXX for domain FIDONET and
x:\bink\outbound\quartz.XXX for domain QUARTZ:
domain fidonet x:\\bink\\outbound 1
domain quartz x:\\bink\\quartz 16
(or domain quartz x:\\bink\\quartz 320)

Please read a Binkey style outbound specification presented in the manual of
the BinkleyTerm or you may look the proposal for standartisation a modified BSO
("advanced BSO" named by author of the proposal) - FSP-1034.001 document in the
FTSC file archive.

ml> how do i tell binkd what zones are covered by the quartz network?
ml> fidonet has 1 thru 6 and i guess that is hardcoded? what about others?

Not hardcoded :), but configurable.


Stas
Jabber-ID: ***@grumbler.org
GPG key 0x72186DB9 (keyserver: hkp://wwwkeys.eu.pgp.net)
... Golded+, Husky & RNTrack maintainer, Binkd developer&webmaster

[mark lewis]

ml> how do i tell binkd what zones are covered by the quartz network?
ml> fidonet has 1 thru 6 and i guess that is hardcoded? what about others?

SD> Not hardcoded :), but configurable.

i've not found configuration verbs for this :/

or is it because of the domain lines and outbound directory names?

eg:
domain fidonet x:\\bink\\outbound\\fidonet 1
domain quartz x:\\bink\\outbound\\quartz 123

X:\BINK\OUTBOUND\FIDONET
X:\BINK\OUTBOUND\FIDONET .002
X:\BINK\OUTBOUND\FIDONET .003
X:\BINK\OUTBOUND\FIDONET .004
X:\BINK\OUTBOUND\FIDONET .005
X:\BINK\OUTBOUND\FIDONET .006
X:\BINK\OUTBOUND\QUARTZ .07B
X:\BINK\OUTBOUND\QUARTZ .07C
X:\BINK\OUTBOUND\QUARTZ .07D

the above indicates fidonet is zones 1,2,3,4,5,6 and quartz is 123,124,125??

and if i have foobar net with zone 124 (duplicate zone, different domain)
then...

domain fidonet x:\\bink\\outbound\\fidonet 1
domain quartz x:\\bink\\outbound\\quartz 123
domain foobar x:\\bink\\outbound\\foobar 124

X:\BINK\OUTBOUND\FIDONET
X:\BINK\OUTBOUND\FIDONET .002
X:\BINK\OUTBOUND\FIDONET .003
X:\BINK\OUTBOUND\FIDONET .004
X:\BINK\OUTBOUND\FIDONET .005
X:\BINK\OUTBOUND\FIDONET .006
X:\BINK\OUTBOUND\FOOBAR .07C
X:\BINK\OUTBOUND\QUARTZ .07B
X:\BINK\OUTBOUND\QUARTZ .07C
X:\BINK\OUTBOUND\QUARTZ .07D

the above indicates fidonet is zones 1,2,3,4,5,6... foobar is 124... quartz is
123,124,125???

i have read the BT-REF.TXT from BDOC_260.ZIP but the examples confuse me and
don't seem to be consistent... especially the alternet parts and the examples
of what to tell your packer :/

i /think/ i have a handle on this || much of it IF i have the above correct...


)\/(ark

[Stas Degteff]

Hello mark.

25 Jul 12 17:04, you wrote to me:

ml> eg:
ml> domain fidonet x:\\bink\\outbound\\fidonet 1
ml> domain quartz x:\\bink\\outbound\\quartz 123

ml> X:\BINK\OUTBOUND\FIDONET
ml> X:\BINK\OUTBOUND\FIDONET .002
ml> X:\BINK\OUTBOUND\FIDONET .003
ml> X:\BINK\OUTBOUND\FIDONET .004
ml> X:\BINK\OUTBOUND\FIDONET .005
ml> X:\BINK\OUTBOUND\FIDONET .006
OK
ml> X:\BINK\OUTBOUND\QUARTZ .07B
Invalid, should be:
X:\BINK\OUTBOUND\QUARTZ
ml> X:\BINK\OUTBOUND\QUARTZ .07C
ml> X:\BINK\OUTBOUND\QUARTZ .07D
OK
ml> the above indicates fidonet is zones 1,2,3,4,5,6 and quartz is
ml> 123,124,125??

Zone 123 specified as "default for the domain quartz" and outbound directory
for 123:*@quartz should be without number in suffix.

ml> and if i have foobar net with zone 124 (duplicate zone, different
ml> domain) then...

ml> domain fidonet x:\\bink\\outbound\\fidonet 1
ml> domain quartz x:\\bink\\outbound\\quartz 123
ml> domain foobar x:\\bink\\outbound\\foobar 124

ml> X:\BINK\OUTBOUND\FIDONET
ml> X:\BINK\OUTBOUND\FIDONET .002
ml> X:\BINK\OUTBOUND\FIDONET .003
ml> X:\BINK\OUTBOUND\FIDONET .004
ml> X:\BINK\OUTBOUND\FIDONET .005
ml> X:\BINK\OUTBOUND\FIDONET .006
OK
ml> X:\BINK\OUTBOUND\FOOBAR .07C
ml> X:\BINK\OUTBOUND\QUARTZ .07B
Invalid, should be:
X:\BINK\OUTBOUND\FOOBAR
X:\BINK\OUTBOUND\QUARTZ

ml> X:\BINK\OUTBOUND\QUARTZ .07C
ml> X:\BINK\OUTBOUND\QUARTZ .07D
OK
ml> the above indicates fidonet is zones 1,2,3,4,5,6... foobar is 124...
ml> quartz is 123,124,125???

Stas
Jabber-ID: ***@grumbler.org
GPG key 0x72186DB9 (keyserver: hkp://wwwkeys.eu.pgp.net)
... Golded+, Husky & RNTrack maintainer, Binkd developer&webmaster

[Andrew Leary]

Hello Stas!

Friday August 03 2012 01:00, Stas Degteff wrote to mark lewis:

ml>> X:\BINK\OUTBOUND\QUARTZ .07B
SD> Invalid, should be:
SD> X:\BINK\OUTBOUND\QUARTZ
ml>> X:\BINK\OUTBOUND\QUARTZ .07C
ml>> X:\BINK\OUTBOUND\QUARTZ .07D
SD> OK
ml>> the above indicates fidonet is zones 1,2,3,4,5,6 and quartz is
ml>> 123,124,125??

SD> Zone 123 specified as "default for the domain quartz" and outbound
SD> directory for 123:*@quartz should be without number in suffix.

Yes, this would be ideal. However, there are several tossers that don't
completely support this. FastEcho, for example, always appends the zone
extension to all outbounds except for that of the primary address. That's why
the way BinkD handles it is so useful; it can work around almost any quirk in
the software used with it.

Andrew

[Stas Degteff]

Hello Andrew.

02 Aug 12 23:05, you wrote to me:


SD>> Zone 123 specified as "default for the domain quartz" and
SD>> outbound directory for 123:*@quartz should be without number in
SD>> suffix.

AL> Yes, this would be ideal. However, there are several tossers that
AL> don't completely support this. FastEcho, for example, always appends
AL> the zone extension to all outbounds except for that of the primary
AL> address. That's why the way BinkD handles it is so useful; it can
AL> work around almost any quirk in the software used with it.

binkd checks outbound/quartz.7B and outbound/quartz if both are exists.

Stas
Jabber-ID: ***@grumbler.org
GPG key 0x72186DB9 (keyserver: hkp://wwwkeys.eu.pgp.net)
... Golded+, Husky & RNTrack maintainer, Binkd developer&webmaster