Subj : Re: Seen-by/Paths To : Sneaky From : Bill McGarrity Date : Mon Nov 06 2017 20:25:55 -=> Sneaky wrote to Bill McGarrity <=- BM> Why are you using fd2ftp? Sn> so I can move the echo.pkt from outbound to my links mail box Sn> for itex to sent to my link BM>It's been awhile since I've used IRex but I BM> know at that time I was using *.MSG/attach and Irex handled it BM> properly. Change everything over to that rather than binkley/FLO. BM> sbbsecho will create the *.MSG and put the pkt in your outbound folder. Sn> in sbbsecho.cfg I useing frontdoor/attach in irex in frontdoor mailer Sn> is Sn> set to frontdoor 2.12 OK.. that's fine... BM> Irex will do the rest. You're going to have to create a ROUTE.REX BM> file similar to the following... Sn> okay that sounds good to me so here are my node numbers Sn> timelord link that I send all pkts Sn> 1:340/400 my link fidonet Sn> 10:10/1 league10 Sn> 316:77/1 whispnet Sn> next link Sn> avon Sn> 3:770/1 my link fidonet Sn> 3:770/100 echo mail Sn> next link Sn> 21:1/100 my link fsxnet Sn> 21:1/101 netmail only Sn> my nodes are Sn> 3:770/330 Fidonet Sn> 10:10/116 league10 Sn> 316:64/1 whispner Sn> 21:1/115 fsxnet Sn> If you could lay it out for me them I might beable undrestand it Sn> Sorry I cannot find my irex.doc OK, try this... route-to 1:340/400 1:* 2:* 4:* (route all netmail thru Bob. OPT.) crash-to 3:* crash-to 1:340/400 (crash all mail to that node from your system) route-to 10:10/1 10:* (OPT) crash-to 10:10/1 route-to 316:77/1 316:* crash-to 316:77/1 crash-to 21:1/100 At the end I'll paste the section of the docs on ROUTE.REX BM> route-to 1:261/38 1:* 2:* 3:* 4:* BM> crash-to 1:261/38 BM> except 2:203/* BM> route-to 2:203/0 2:203/* BM> crash-to 2:203/0 BM> crash-to 1:229/300 BM> crash-to 1:266/512 1:266/* 1:13/* BM> crash-to 1:387/22 BM> crash-to 1:3634/1 1:3634/* BM> crash-to 1:298/6 BM> crash-to 618:100/1 BM> route-to 316:77/1 316:* BM> route-to 618:100/1 618:* BM> Look in the docs for IRex to help you with this. So, everytime a *.MSG BM> is addressed to 1:261/38, Irex will crash it to that address along with BM> the attached pkt. Sn> Yes I understand it, it what I am look for. Sn> work with sbbsecho.exe ver2.33 it puts the netmail pkt in the my link Sn> outbound Dir Sn> with the netmail saying d:\fd\outbound\aaaa.mo0 (pkt) but irex won't Sn> sent the Sn> pkt only the netmail, when it gets there it empty (no pkt) but with Sn> my version Sn> of sbbsecho.exe it works fine. BM> Yes, because you're creating FLO style mail. IRex maybe set for BM> Frontdoor style *.MSG/Attach Sn> yes irex it is set on frontdoor 2.12. Sn> before I go any further with this per routing. and seen-by etc as I Sn> think I fixed it and Sn> then another problem came up, samething else after that probaly came up Sn> so I would like Sn> to ask you, do you use icq are a same type of direct messaging. No... sorry.. Sn> Again I would like to thank you for your help, it has been very good Welcome.. Section 10: Routing Internet Rex's routing is controlled by the file route.rex located in the same directory it was installed to. route.rex is a text file which you can edit using your everyday text editing program (edit.com, e.exe, Wordpad: all of these will do fine). Routing for Rex is controlled by routing commands you add to the file. Here is a sample route.rex file: ; This is a quick route.rex file. ; It routes all mail to zone 2 through 2:2/20 ; Any mail to the local region (addresses 2:300/*, 2:302/*, 2:305/* ; and 2:306/*) are not routed. ; It holds all mail to zone 1 and holds any non-mail files to be sent. route-to 2:2/20 2:* 3:* 4:* 5:* 6:* except 2:300/* 2:302/* except 2:305/* 2:306/* hold 1:* hold-files ; In event A, mail to 1:342/806 is now allowed to be sent event A unhold 1:342/806 ; In event B, mail to 1:342/806 is held, but non-mail files can now ; be sent. event B unhold-files Notice that the first three lines of the file are comments. Rex will ignore any line which doesn't start with a routing command it recognizes. Commands you can give in a route.rex file are: event The event command declares a routing block for an event. Rex's usual behaviour when it isn't running an event is to read the route.rex file from top to bottom until it either reaches the end of the file or an event command. So, in the example above, if Rex isn't running an event, mail to nodes in zone 1 will be held (because of the hold 1:* command). However, if Rex is running an event and it finds an event command with a tag which matches the current event's tag, it reads the commands between that event command and the next one in the file. So if Rex were running event A, mail to zone one would still be held, but mail to 1:342/806 wouldn't be. hold ... except ... The hold command tells Rex not to send mail for addresses which match the wildcards given. Addresses can be excluded from the list using the except 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 (c) Copyright 1997-2002 Khan Software and Charles Cruden 65 Internet Rex v2.29 technical manual 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 command. hold-files hold-mail hold-mail signals to Rex that files which match *.PKT, *.SU#, *.MO#, etc. should not be sent. Similarly, hold-files says that any file which doesn't match *.PKT, *.SU#, etc. should not be sent. These commands are useful for scheduling when particular files should be sent. For example, if Rex is using one of your BBS lines to connect to the net, you probably want it to hold-files until later in the evening when you will have fewer callers. route-to ... except ... This command routes mail for any node matching the wildcards to the destination address. The except command after it prevents certain addresses from being routed. For instance, in the example route file, mail to 2:400/101 would be sent to 2:2/20, because 2:400/101 matches 2:*. Mail for 2:300/101 would not be sent to 2:2/20, even though it matches 2:*. It also matches 2:300/*, and the except command takes precedence. unhold ... except ... The unhold command reverses the effects of the hold command. Mail which was on hold is now back to normal. unhold-files unhold-mail These two commands reverse the effects of the hold-mail and hold-files commands. Limits: No line in the route.rex file can be over 512 characters in length. No routing command can include more than 1024 addresses or wildcards: 512 inclusion addresses and 512 exclusion addresses. -- Bill Telnet: tequilamockingbirdonline.net Web: bbs.tequilamockingbirdonline.net FTP: ftp.tequilamockingbirdonline.net:2121 IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697 Radio: radio.tequilamockingbirdonline.net:8010/live .... Look Twice... Save a Life!!! Motorcycles are Everywhere!!! --- MultiMail/Win32 v0.50 * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404) .