Hi Michiel,

> [ INA flag ]

>>>> Yes, but this proposal destroys any chance of backward
compatability.

>>> As was said about any other.

>> So 3 nets lose connectivity IP wise for the sake of one
>> system to use a format that no software supports anyway....

>That is the problem with this way of doing things. I am sure it is well meant,
> but it is obviously not well thought through. One has to have the software
> FIRST.

Actually we do have the software, from what I understand.  The problem was
being patient in hearing whether David Hallford was still available to
create his binkp lists, etc., in the IP-Nodelist fdn, or whether he was
giving up that fdn.  All netmail and e-mail posts to him have failed in the
last 2 weeks, so I am about to have the author of this other software take
over and release the nodelists for IP-Nodelist fdn, or start another FDN. 
He's just waiting for the
'go ahead'.

Other software like BBBS's mailer may even support the new INA flag and  I
intended to test it more thoroughly this weekend. It was rough to think of
doing the testing before our holiday on Thursday (Thanksgiving), and I've
been a little ill recently (getting better now, though ).

The statements I've seen about 'broken software' haven't explained exactly
what the problem was that breaking anything.

If these nodes are using a mailer like Argus, the information in their
config hasn't changed.. if they're using a mailer like BINKD, that hasn't
changed either.  If they're using something that reads a person's node info
from the nodelist I'd like to know what software that is. I could be wrong
here.

Take care,
Janis

--- BBBS/LiI v4.01 Flag-4