Text 758, 61 rader
Skriven 2007-04-11 15:07:12 av Stas Degteff (2:5080/102)
    Kommentar till text 751 av mark lewis (1:3634/12.0)
Ärende: Re: BinkD.txt
=====================
Hello mark.

10 Apr 07 12:09, you wrote to me:

 SD>> zone number in the "domain" statement is declares default zone of
 SD>> the domain, Zone number don't needs to append into the outbound
 SD>> directory for default zone:

 ml> yes, i know all this...

 SD>> Examples:
 SD>> domain fidonet  z:\\binkd\\outbound\\fidonet 1
 SD>>  outbound directory is: z:\binkd\outbound\fidonet for zone 1, and
 SD>> z:\binkd\outbound\fidonet.2 for zone 2

 ml> this works for most implementations...

 SD>> domain spacenet z:\\binkd\\outbound\\spacenet 11
 SD>>  outbound directory is: z:\binkd\outbound\spacenet for zone 11 and
 SD>> z:\binkd\outbound\spacenet.12 for zone 12

 ml> however, this doesn't and that is due to the mail tosser...

if tosser "known" about 5D FTN addressing then this tosser uses described
outbound directories. But several tossers isn't compatible with 5D :(


 ml> i know they are illegal right now... i am suggesting a feature to be added
 ml> so that folk don't see and experiance the problems with binkd saying that
 ml> it is contacting 71:123/456@fidonet when it should be 71:123/456@scount...
 ml> this problem is all too common and i see it all the time... this is one of
 ml> the reasons, also, why many folk have simple given up trying to get binkd
 ml> to say/use the proper domain and we see such garbage as 71:123/456@fidonet
 ml> which is plainly incorrect...
......

 ml> domain fidonet  z:\\binkd\\outbound 1-6
 ml> domain s2net    z:\\binkd\\s2net    63,81
 ml> domain zenet    z:\\binkd\\zenet    92
 ml> domain stn      z:\\binkd\\stn      111
 ml> domain micronet z:\\binkd\\micronet 618
 ml> domain scout    z:\\binkd\\scout    71,1907
 ml> domain quartz   z:\\binkd\\quartz   1024-1026,2547

 ml> the whole idea, as stated before, is to be able to tell binkd the
 ml> zones covered by a domain and not have the problems like are being
 ml> discussed where you have to remember to add it onto the end of the
 ml> address of a connecting system...

Your "feature request" may be implemented using new config-statement, like:
domainmatch quartz 1024-1026,2547
domainmatch scout 71,1907
domainmatch micronet 618
domainmatch stn 111
domainmatch zenet 92
....

Stas

--- GoldED+/W32-MINGW 1.1.5-b20070221
 * Origin: Grumbler: E-burg, Russia (2:5080/102)