New nPOPuk Release + OpenSSL / CE Testers Needed!

Okay, that's a rub: the 2.0 version is not SSL-ready and there are no SSL links available for 2.0

I did test on HPC2000 and once I used an google-generated app password, I was able to log-in and download mail. However, upon sending, I get a "Verify of SSL failed" and when I disable "Verify the server certificates," I get "Server disconnected."

Jake

@Jake Hi can you make a test account for outlook email, make sure pop is enabled and try that?
Someone told me gmail is a little more funky
Also don’t use the Npopuk .ins files I think they’re out of date. Make sure to use the outlook.com settings and or the gmail settings

Hi, torch,

Took your suggestion and I'm getting different errors upon send: Initialisation of SSL failed/error: 140770FC:SSL/routines:SSL23_GET_SERVER_HELLO:unknown protocol.

Did change Port from 465 to 587

Jake

Edit: wait, I missed something in your last post--not sure why/how I would set up outlook email on J720. The errors above are from npopuk 3.05 and HPC2000

Edit2: I did setup pop.gmail.com on Outlook Classic Pro, which does work, and it appear their outgoing port is 465, which does send mail successfully

Edited by Jake 2022-12-27 5:33 PM

Jake: sorry I just suggested to try outlook.com email only because that’s the common outlier that we were testing in ssl thus far.
Anyway,
I tried Npopuk 3.05 Windows CE 5 SSL x86 on my x86 HP t5540 CE6 thin client and I got that error message that you got on your sharp Mobilon about Initialization failure of npopssl.dll

I also tried Npopuk 3.05 Windows CE 2.11 MIPS SSL on my MobilePro 790 HPc2000 and I got a different error saying “verify of ssl failed unable to get local issuer certificate” error(20)

Edited by torch 2022-12-27 5:42 PM

Yeah, I've gotten that verify error as well. If you disable "Verify the server certificates," you might get error "Server disconnected."

Jake

Can you try:
Keeping the same.ini file and trying version 3.04 on both of your devices? I want to see if there’s some issue with 3.05’s OpenSSL
Edit: note I don’t know how secure that is

Edited by torch 2022-12-27 5:52 PM

I actually had played with 3.04 sometime ago so had it ready on the cf. I can't even get in to check the mail--"Verify of SSL failed"

Jake

Unfortunately, this goes beyond my expertise - last thought I had - is your TinyBook T-706 in your signature still functional? I wonder if you could try soju's ARMV4_012 version with watamario's .exe with your .ini file and see if it connects
here's watamario's exe post



and here's soju's armv4_012 version: And make sure you put that ca root certificate file in your root directory (i.e. not in \Windows, in the root folder that contains \Windows)

I will try to dig up that TinyBook and experiment. It's not a total loss--for one thing, I'm getting gmail on the J720 and that's new, at least.

It would be nice to see gmail on a 2.0 device but precisely b/c of these SSL issues, not to mention ports, I still use Earthlink and its good ole insecure 110 port.

I just want to help out here, as gmail isn't my main driver.

You folks are heroes to soldier on like this.

Jake

Even though it's not your main driver, thank you so much for trying this out and seeing what needs to be fixed! Appreciate all of your help.
In regards to Windows CE 2.0 + nPOP + SSL: it appears even the inaugural release of nPOPuk 2.00 did not seem to support SSL for CE 2.0. However, the readme for Nakka's version of nPOP 1.06 for CE 2.0 (has EN and JP versions) seems to imply SSL support. It's in the SCL here but don't know how scary/insecure running a 2005-2006 SSL build is.

Edited by torch 2022-12-27 9:31 PM

May I ask you to check if the resource problem is fixed?
ARMv4_013: https://www.dropbox.com/sh/6fnagmjunsinsjy/AAB4qlCuqYNPyd2uIIRiPACva...

Yes! All back to normal! thank you looks great

This is a test build that makes more log to unvail why your SSL connection is stuck while loading. Torch, please reproduce the problem using this build, and share me the log. Please do not forget to redact your personal informations included in the log before sending it.
ARMv4_014_log: https://www.dropbox.com/sh/crquy9ciiu1mvbc/AAC357HEO_74TZ_J1yjl0EKAa...

Here's my log

Did you reproduce the same problem? I think there should be "verify: ok" in the log, but actually it isn't.