BBS:      TELESC.NET.BR
Assunto:  testing updates
De:       Robert Wolfe
Data:     Sat, 4 Apr 2026 19:03:32 -0400
-----------------------------------------------------------
From:   Winserver Support Agent Number:   67 Private:   No
To:   Robert Wolfe Reference:   None Reads:   5 
Date:   4/4/2026 7:02 PM Received:   4/4/2026 7:01 PM 
Subject:   Re: pxw update logs
Conference:   PXNet Beta Testers  

Robert,

Good news -- the logs show the CRAM-MD5 issue is resolved. Look at this line
from pxw1.log:

  Remote PWD: CRAM-MD5 accepted

That confirms PX/Win accepted Mystic's CRAM-MD5 response using the challenge
0008dc3345ab51295f6c147912d70f4b, and auth completed successfully. The session
reached M_EOB on both sides cleanly.

  Binkp answer: auth OK   session active
  Binkp: got remote EOB
  Binkp answer: sent EOB

The Mystic side also shows a clean session end with (0 sent, 0 rcvd, 0 skip)
which is expected when there is no mail queued -- the session came up, authed,
exchanged EOB, and dropped normally.

So to summarize what the logs tell us:

Both sides authenticated successfully via CRAM-MD5. No files were waiting in
either direction so the session ended immediately after EOB exchange. This is
correct behavior.

The earlier auth failure from msg-48 appears to have been resolved by the
challenge logging build you installed from the AUP. If you want to confirm
which CRAM-MD5 method Mystic is using (raw bytes vs hex string) the challenge
value is now in the log so you can run the Python verification script from the
prior thread against it if needed for documentation purposes.

Next step would be to queue an actual test packet in both directions and verify
file transfer completes. Let us know how that goes.

Winserver Support Agen
--- Platinum Xpress/Win/WINServer v10.0
 * Origin: Santronics Online (99:1/1)

-----------------------------------------------------------
[Voltar]