Prev Next New Reply Forward Delete
View Text Mode
From: Winserver Support Number: 199 Private: No
To: Robert Wolfe Reference: None Reads: 1
Date: 6/9/2026 1:40 PM Received:
Subject: RE: file correction
Conference: PXNet Beta Testers
Some mailers only support Binkp 1.0, not 1.1 or if they do, they do it wrong or don't
offer a 1.0 fallback (enforce CRAMMD5). Binkp 1.1 needed for CRAM-MD5 support.
What he is saying you don't need it if you have Bink 1.1 with a correct 1.0 fallback.
But some mailers don't have 1.1 or a fallback.
Its working now for you, correct?
On 6/7/2026 8:06 PM, Robert Wolfe wrote to Winserver Support:
On 6/7/2026 6:40 PM, Winserver Support wrote to Robert Wolfe:
@TID: PX/Win v10.0b47 PX35-1001M
@MSGID: 99:1/1 92df6477
@TZUTC: -0400
So what is he/she saying, set it to 1?
On 6/5/2026 12:42 PM, Robert Wolfe wrote to All:
rom the mbse author regarding binkp-compat.ini.
--------------------------------------------------------------------
--
-
; mbcico - VER: mbcico/1.1.7/Linux-x86_64 binkp/1.1
; Unix FTN mailer. CRAM-MD5 behavior unknown.
; Conservative default maintained.
;
--------------------------------------------------------------------
--
- [mbcico] CramMD5=0
Completely unnecessary. Both IRex and mbcico support CRAM-MD5 authentication.
--- Platinum Xpress/Win/WINServer v10.0b47
* Origin: Santronics Online (99:1/1)
I believe what Andrew is saying is, is that this setting is a moot point and doesnt have to
exist at all. And I have to agree because this has always been true.
--- Platinum Xpress/Win/WINServer v10.0b40
* Origin: Over the Brink : Grand Island, NY - brinkbbs.org (99:1/6)
--- Platinum Xpress/Win/WINServer v10.0pr1
* Origin: Santronics Online (99:1/1)