DD> A "properly configured mailer" expects to find an dialable phone
 DD> number, or "Unpublished" in that field in the nodelist.

 ml> correction... a properly configured mailer expects to 
 ml> find a contactable number in that field or "-Unpublished-"...

 DD> YMMV if you use a shim kludge.

 ml> hunh? what shim kludge are you speaking of? my mailer uses a FOSSIL to 
 ml> contact and converse with remote systems and hardware... 

 PK> The shim kludge of software specifically set up to handle IP
 PK> addresses extracted from a Phone no. field...

hunh?? sorry but frontdoor doesn't require a shim kludge to draw the IP
number from the contact number field in the nodelist... it never has since
the feature/capability was introduced... in fact, at the time that it was
introduced, it was perfectly within developing and existing practise ;)

 PK> So in reality it all comes down to identifying what is meant by "a
 PK> shim kludge"..........;-)

well, i happen to know that DD was trying to go after the use of the
SIO/vmodem package written for OS/2 systems by the creator of x00, ray
gwinn...

 ml> my system just happens to have the capability of doing something 
 ml> that your's doesn't... should i even mention that i also have an 
 ml> experimental FOSSIL driver that speaks native TCP/IP in a similar 
 ml> fashion to NFS?? what about the one that does the same thing 
 ml> except in FTP format? does that make them a shim?? i don't think 
 ml> so...

 PK> I actually think that nicely describes a "shim" or
"kludge". Your
 PK> software is making something designed for one thing think its
 PK> something else so that it can use it...

hunh? so you are saying that the FOSSIL stuff developed by fidonet and its
developers is a kludge? somehow i think they'd all highly disagree with you
on that without failure...

 PK> But all this coems down to what is meant by "shim" and/or
 PK> "kludge"... 

almost :)

)\/(ark