[nos-bbs] more WP code and coordination of hierarchical addressing ...
bobtenty at gmail.com
Mon Mar 19 22:32:55 EDT 2012
Ax25 forwarding works indirectly to the end user and that is a big
disadvantage compared to smtp
what is more direct.
At least with smtp I know right away or the far end server is there or
not and that makes it much more reliable.
(From the standpoint of sending smtp server or BBS)
If an intermediate ax25 forwarder somewhere in the cloud has the wrong
settings you are toasted and it might take
a while before you know!
So it depends much more on the human factor.
You compensate by having multiple forwarding partners (sadly nowadays
mostly over Internet)
On 12-03-19 05:21 PM, Maiko Langelaar wrote:
> Good afternoon (local time),
> It's a start, more to do, sorry for the 'note style' documentation,
> which is typical of a person who has very little time. Please have fun
> with it, and please do report any issues, or dislikes, or whatever.
> While we're at it, I'd like to bring up the topic of coordination
> of hierarchical addressing. I think this stuff is really cool (it
> only took me 5+ years to notice it and try it out for a change),
> BUT it is very dependent on people having *correct* entries in
> their 'rewrite' file to send these HADDR'd destinations to where
> they need to go. I mean, think about it, it just takes one system
> to be improperly configured (or not configured at all) for major
> loss of messages, so I'm thinking the ones that are serious about
> this type of routing probably coordinate and talk to each other on
> a regular basis, to make sure messages get to where they need to
> go. Or do they ? I'm sure this can get interesting. Comments ?
> nos-bbs mailing list
> nos-bbs at tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nos-bbs