| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Squish TODO |
Hello Bob! 18 Jun 03 21:32, Bob Jones wrote to Bo Simonsen: BJ> If you try to use "ROUTE NOARC NORMAL 1:234/567.8 1:234/*" BJ> and then have a line that does something like default route (from BJ> memory, something line "ROUTE CRASH 1:140/1 1:ALL 2:ALL 3:ALL 4:ALL BJ> 5:ALL 6:ALL"), then the mail that you packed for 1:234/567.8 gets BJ> retargted and sent to 1:140/1 (in this example). Actually, it doesn't BJ> need to be a default route. It just needs to be a command that ends BJ> up reprocessing node 1:234/567.8's outbound mail packets..... I don't see the bug. The first step changes the address but retains the routable flavor. The new address and existing flavor still meet the criteria specified for the second step. Using in Step1 prevents it from being a candidate for being routed to 140/1 in Step2. You could add Step3: CHANGE NORMAL 1:234/567.8 to end up with NORMAL again if that's your objective. Instead, you could also use some address with a fictional zone that is not in Step2's criteria, for Step1 and Step3. How would you want to change Squish's current behavior to "fix" it? Prevent more than one routing command from ever being applied to the same mail in the same run? .\\ike --- GoldED 2.50+* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61) SEEN-BY: 633/267 270 @PATH: 382/61 140/1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.