Yes, I replied to an echomail message from Khronos at 21:2/153. He was
looking to do some testing.
I am not sure if that is his own node or another he was visting but I don't >> see any 21:2/153 in the nodelist.
Yes my node is 21:2/153
I thought that was probably the case.
I don't know if this can be done, but a possibl solution to this would be to have a node list and then if the node you want is not in the list to then route back to the generic 21:x/xxx route as a fall back.
I never sent that message directly but that wouldn't work either since 21:2/153 is not in the nodelist currently, so it would get stuck in my outbound. I'm sure that Avon will get that sorted soon.
I can turn that feature off in BBBS but it does save a lot of undeliverable messages bouncing around between the hubs.
I have at times entered a typo in the to: address of messages and if sent out it would just bounce around until someone, somewhere deletes it.
--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)