NA> The password system of D'Bridge has remained largely unchanged since
NA> 1987... for a reason. It is this and the mail-tossing code that many
NA> D'Bridge users have grown accustomed to, because it works. Fixing what
NA> isn't broke is largely frowned upon by the few seasoned D'Bridge users.

Agreed.  

I know more about beer than Fido standards.  Trying to piece this together,
there are two different things going on.

1)  Mystic doesn't handle the -R -L on the Subject line following the
AREAFIX password.  That could be added to Mystic as a solution to be more
compatible with existing setups.

2)  Session passwords being used as packet passwords - even when no packet
password is set.  This could be considered normal - I really don't know.
Apparently packet passwords were ignored on some BBS plaforms before and
are now parsing them.  So if they have no password set and are getting one
from the other side, things are failing.  

We can get around each of these things now that we know more about what is going on.

What I'm being told is my D'Bridge hub is sending packet passwords to
uplinks even though I don't have one set.  It is using the same password as
the session password (we found this out by guessing when setting up
fsxNet).

If you want to remote my setup, feel free.  I'm willing to help if needed.

- Mark

--- WWIVToss v.1.51