Hi,
If I send a message to an unknown user on a remote system will I get a bounce message back or will it go into thin air based on the
limitations of the technology?
telnet://bbs.roonsbbs.hu:1212 <<=-
If I send a message to an unknown user on a remote system will I get a bounce message back or will it go into thin air based on the limitations of the technology?
I wrote a netmail to someone yesterday and my own BBS bounced it back to me because the person I wrote to was not in the nodelist.
I wrote a netmail to someone yesterday and my own BBS bounced it back to
me because the person I wrote to was not in the nodelist.
was that a Zone 21 addy Al? I'm hoping we haven't dropped the ball for a new node?
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.
I wrote a netmail to someone yesterday and my own BBS bounced it back to >> me because the person I wrote to was not in the nodelist.
was that a Zone 21 addy Al? I'm hoping we haven't dropped the ball for a new node?
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, 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 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.
Yes my node is 21:2/153
I thought that was probably the case.
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 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 have added the node now and will force an early hatch of the nodelist shortly.
Apologies for the oversight guys :)
I have added the node now and will force an early hatch of the nodelist shortly. Apologies for the oversight guys :)
The new nodelist has arrived and I have compiled it. I now see 21:2/153 listed.
Thanks for the update, I'll send a test or three out now.. :)
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 577 |
Nodes: | 8 (0 / 8) |
Uptime: | 60:24:12 |
Calls: | 10,734 |
Calls today: | 1 |
Files: | 5 |
Messages: | 442,618 |