Thanks for sharing your experience and insights on this. Migrating out of Eudora is no walk in the park! I've often considered taking the IMAP route, but Eudora's support for IMAP feels a little patchy.
Specialised conversion/migration software is probably the better route to go, especially now that the Eudora source code was donated to the Computer History Museum. I'll give Eudora2Unix a shot though!
You mentioned attachment name clashes: Eudora simply appends an incrementing integer to the incoming attachment's filename, for example, it would retain file.jpg for the first email and use file1.jpg in the next email it encounters.
Here in South Africa all the banks I know of moved away from SMS text messages for 2FA ages ago, and perform authentication in-app with biometrics instead. Having a banking app installed on your phone is pretty much mandatory, and criminals have no doubt grown wise to this fact. So what happens when someone holds a gun to your head and forces you to perform a large transfer of funds from your phone? I'm sure the banks will try convince you that their fraud detection systems will come to your aid.
One bank here recently introduced a duress-PIN, which when entered, will commence monitoring and send help, but they still don't offer any guarantee of a refund. Another bank allows you to change their app's icon and name, in an effort to masquerade as something less recognisable.
I'd much rather delete the apps, unlink my devices from my bank accounts and use a TOTP authenticator app instead.
> "JavaScript is also a promising core technology for the new multimedia publishing tool that Macromedia is building."
I believe Bud Colligan may have been speaking about ActionScript in this quote, the scripting language found in their yet to be launched Macromedia Flash product. Of course, Flash is no more... and neither is Macromedia. Time flies!
For your future self: At some point they may ask you for some tech support to get their secure connection to mail servers working again. Start with the HermSSL package available here: https://sourceforge.net/projects/hermesmail/files/
I'm still using Eudora because I can't bear to part with it! Yes, its poor HTML renderer and lack of UTF-8 support, amongst other things, have no place in 2023, but other modern mail clients still seem to fall short on the features Eudora just gets right.
There's hope that the HERMES Mail project, which was formed after the Eudora source code was release, will one day be a viable replacement:
I met a bunch of people here in Stellenbosch, South Africa at a startup called Gourmet Grubb. Their first product is an ice-cream made from insect milk, trademarked EntoMilk - no kidding! Fascinating stuff, check them out here: https://gourmetgrubb.com/
Not sure this is entirely true. RFC 3848 (http://www.rfc-base.org/txt/rfc-3834.txt) covers the implementation detail, and a lot of consideration was given to the prevention of email loops.
Section 4 states that auto-responders should send the response to the email address given by the Return-Path header (usually set to a VERP address for identification of bounces) or if absent then fall back to the email address given in the From header.
Specialised conversion/migration software is probably the better route to go, especially now that the Eudora source code was donated to the Computer History Museum. I'll give Eudora2Unix a shot though!
You mentioned attachment name clashes: Eudora simply appends an incrementing integer to the incoming attachment's filename, for example, it would retain file.jpg for the first email and use file1.jpg in the next email it encounters.