uucp and parity checking

[Russell Lawrence]

We're having a tough time establishing regular uucp connections with one 
of our net neighbors.  After login, we expect the remote system to 
confirm their identity by sending a string like the following: 

        imsg >\ 15 \ 12 \ 20 Shere=xyz\  0  enter...

Instead, we usually get something like this:

        imsg >\215 \ 12 \220 S\350 ere=xyz\  0 \ 12 \ 15,

in which many of the expected ascii characters have their eight
bits turned on.

The upshot is that our machine gets confused and hangs up after 
reporting 'wrong system'.  

Unlike most systems that we communicate with, 'xyz' does parity
checking on their ports.  Could this be the cause of our problem, and
if so, can anyone suggest a work around?  'xyz' does *NOT*
run HDB and I don't think they're too excited about changing the
port definitions in their gettydefs file in order to conform to
our expectations.

-- 
Russell Lawrence, WP Group, New Orleans (504) 443-5000
{uunet,killer}!wpg!russ