CS>> Huh?  They dont use an international dialing code in Z3 to reach
 CS>> 000 (emergency like 112 or 911 in other places).

 ml> correct, but they do have to if the 000 is the _country code_ in a
 ml> listing... remember how phone numbers are laid out...

 ml>   countrycode-areacode-citycode-restofnumber
 ml>        1     -  800   -   555  -  0100
 ml>       000    -  192   -   168  -    2   -   1

 ml> and again, this all goes back to "properly configured
mailer" and that
 ml> includes a properly set up "dialing translation table"...
that's where
 ml> you tell the mailer what areacodes are local calls... everything else is
 ml> not local and would get the national or the international dialing code
 ml> prefixed to it... and that, right there, is the point at which it stops
 ml> being a problem...

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

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

 DD> YMMV if you use a shim kludge.

hunh? what shim kludge are you speaking of? my mailer uses a FOSSIL to
contact and converse with remote systems and hardware... this is how it has
always been... just because my FOSSIL driver can speak more than one
language and your's cannot doesn't make me or my system any better than you
or your system and visa versa... my system just happens to have the
capability of doing something that your's doesn't... should i even mention
that i also have an experimental FOSSIL driver that speaks native TCP/IP in
a similar fashion to NFS?? what about the one that does the same thing
except in FTP format? does that make them a shim?? i don't think so...

)\/(ark