REPLY: 1:340/1101 0031ff07
MSGID: 2:221/1.254 674b527a
CHRS: LATIN-1 2
TZUTC: 0200
TID: FastEcho 1.46.1 1530

30 Nov 24 03:16, Martin Kazmaier wrote to Alan Ianson:

 >> Yes, that is a 5d outbound. That's fine if your tosser is 5D aware.
 MK>
 >> I don't know of a 5D aware tosser off the top of my head. My
 >> tossers have all been 4D. I would put a 1 (your main zone) at the
 >> end of all those domain lines and work in 4D mode.
 MK>
 MK> Fastecho has been in the past.  I don't know what it's doing now...
 MK> I'll see if things still don't go out and then change them to 1.
 MK> fastecho is putting the files in araknet.00a, but binkd is creating
 MK> araknet and looking in there, even though I'm pointing to the 5d
 MK> outbound.  I can remove the domains from fastecho and change the way
 MK> that is handling it.

If you define domain if FESetup address manager, it will use 5d BSO.

I don't use domains, works ok with binkd.

'Tommi

--- FastEcho/2 1.46.1 Revival
 * Origin: =========================>>>> (2:221/1.254)
SEEN-BY: 4/0 88/0 90/0 103/705 105/81 106/201 124/5016 128/187 129/305
SEEN-BY: 153/757 7715 154/10 30 203/0 218/700 221/1 6 242 226/30 227/114
SEEN-BY: 229/110 114 200 206 275 300 307 317 426 428 470 550 664 700
SEEN-BY: 230/0 240/1120 5832 266/512 280/464 5003 5006 5555 282/1038
SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66
SEEN-BY: 341/200 234 342/200 343/107 396/45 423/81 120 460/58 467/888
SEEN-BY: 633/280 712/848 770/1 900/0 102 106 902/0 19 26 930/1 5020/400
PATH: 221/1 280/464 341/66 902/26 229/426