@RoiEX Unlikely, given it's Thanksgiving week here in the US.
Maybe we should just renew the domain for another year and only let it expire once everything has been migrated?
@scousemart The past Outlook/Hotmail PBEM issue you mentioned (https://github.com/triplea-game/triplea/issues/2595) doesn't appear to be related. Your opponent's issue looks like a simple authentication failure, whereas #2595 was due to a non-Outlook/Hotmail email being used as the From address.
I'd ask your opponent to verify their own PBEM settings after they load the save game, especially the Login and Password
fields. If those are correct, one other thing to ask your opponent is if they have two-factor authentication enabled on their Outlook/Hotmail account. If so, they'll probably have to generate what's typically known as an application password in order for TripleA to be able to send the email. We can research that further if it turns out 2FA is enabled.
I see from the above postings that "common files" have been inspected before, but maybe not "i4j_jres" (?).
And if you install TripleA as a non-admin, the bundled JREs go someplace under your user profile. I think the i4j_jres folder gets placed in C:\Users\<username> (possibly with a leading period), but it might be somewhere under C:\Users\<username>\AppData\Local.
@Icelander So, both of those saves seemed to work fine with MARTI on my box with a 184.108.40.206.12226 client and Java 1.8.0_181.
However, I dug into the dice roller settings stored in each of those files and think I know why newer saves fail for you while older ones do not: the newer save (Ger0) is using HTTPS to connect to MARTI, while the older save (Ger3) is using HTTP to connect to MARTI. So, that's good in a sense, because it means your HTTPS connections were probably never working, and it has nothing to do, per se, with the latest version of TripleA (other than it enabled HTTPS by default).
The next step will be to take a look at your system properties, as discussed above. If that shows the version of Java TripleA is using is good, then the most likely candidate is you have some kind of TLS/SSL proxy running on your local machine/network (see issue 2821 referenced above).
I can't find the issue right now (probably too tired from the day), but I recall @ssoloff guiding a user through troubleshooting steps to fix this issue.
However, not only I connected to the dice server until a few days ago, but when I load those game files, the connection still works now.
The connection only fails for any game I start now.
I'm trying to upload two game files, the first (new) fails, the second (old) succeeds.
I'll take a look at those and see if there's anything specific in the save games that might identify the problem.