[...]
 
MH> There is only one location in the DB config for session password.  It is
MH> located under "Advanced/Misc Security".
 
MH> There is a separate location for a "Packet Password" that is located
MH> under "Packet/Mail Control".
 
MH> I have verified that I only have "Session Passwords" setup with no
MH> "Packet Passwords".  The Packet Password field is totally
blank - never
MH> has been used.
 
MH> I can also verify that my hub instance is sending echomail with a packet
MH> password - using what I have setup under "Session Password".
 
That is what has been going on for about 3 months now.  The ultimate
solution to this should be coming in the next few months. unless you just
simply cave in and add a session password to your config.
 
MH> I'm assuming that packet passwords were previously ignored in both
MH> Synchronet and Mystic.  That's an assumption, but I have no other
MH> explanation as to why we just recently started noticing this issue.
 
Right.
 
MH> The solution was simple.  I just asked my uplinks to add a Packet
MH> Password to match our session password.
 
I don't blame you for doing that, but I'd like to know what happened.  I
want to know if my mailer is doing that, but I don't think it is.  Joe and
I tested this by removing the session password and so everything began
working again.  Once a session password in placed, however, the problem
begins anew.  I have never had a packet password for him and many others,
whom, I might add, do not have this problem.
 
 
...If you take life too seriously, it ceases to be funny.
 
 
Regards,
 
Roger

--- DB 3.99 + Windows 10