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

 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 find a contactable
 ml> number in that field or "-Unpublished-"...

 DD> As documented in which version of Policy?

ermmm... policy doesn't speak to this so why bring policy up? this is a
technical situation not a social or political one... however, you and
others of similar mind desire only to confuse the issue(s) and stir the
fecal matter in the barrel...

should i also mention that =you= have a(n annoying) habit of trying to put
policy into things where it doesn't belong...

)\/(ark