@[email protected] i never used mutt (maybe i have), and till today i use alpine.
when i used it, it wasn't for coolness.
there was a undp sponsored project in yerevan, called freenet.am. there was a free dial-up, and telnet access to their unix server.
most people didn't use it, but many youngsters learned how to use telnet and some unix commands, primarily for using talk in console.
and pine was the way to read emails. of course it was also possible to use web mail (not useful at all) and email clients - that's what most people would do.
but mail client would download an attachment on dial-up, and with pine it was easy and fast to check and answer.
@danimrich not only feels like it. Still is (as alpine).
It also handles images reasonably well if you have a keyboard-controllable image viewer configured.
@astro_jcm
I used pine the same year as you! I felt like a l33t haxx0r, lemme tell ya!
This is not Elm.
Hey,
maybe you're calling me some names now, but nowadays I've been using the alpine mailclient for decades and until today. By the way, the configuration file is still called pinerc and in it you can specify the editor for compose and replies, for example. For me, it's called Vim and together with the file manager ranger, a damn fast workflow can be generated from the console without annoying program changes via the desktop gui. You just have to coordinate the configuration files of the programs with each other... for example, to quickly send newly created scripts to a group out of your editor. Another interesting mail client for such work is aerc! So we have quite a choice with Mutt, Alpine, Aerc, Neomutt to move directly from commandline.
@astro_jcm ah back in the days when college email was using telnet (not ssh!) to get a UNIX CLI on a DEC Alpha server.
Even those of us who had Thunderbird (or Eudora) set up on our own PCs needed to use Pine any time we wanted to check in on things from a computer lab.
@[email protected] i also first was using it with telnet, not ssh. the admins of free shell server were afraid of ssh, they told me back then that you can do lots of nasty stuff with it and they just allowed telnet. they already had a restricted shell but well.
good, that they isolated every dialup client but basically everyone who could connect to a phone line could sniff i guess. though i don't know exactly how.
also one of my former coworkers at his other work place where he was an admin, (that was a shipping company) forced all employees to ssh to the email server and use alpine in console. it was his measure to decrease probability of virus infections.
do you remember the vb viruses? there were a lot, and they were feeling very comfortable in outrook, their natural habitat.
it is sad to say but i know exactly two of my contacts that were persistently infected with outlook viruses and i knew i just have to delete most of emails from them. i told them of course but they could not fix the problem. the sad part is that it stopped when they switched to gmail and its web interface.
back to shipping company, i think when they were having an important attachment from out of their network theiy didn't have skills to transfer those so the administrator would do it for them.
otherwise they were using samba to exchange files between windows machines.
@astro_jcm But Pine is not Elm. 🤓
Loved it, good old times.
@astro_jcm Unfortunately killed by the copyright owner changing the license in 1995 from a BSD style to one that prohibited redistribution of modified versions.
Unfortunately 10 years later XFree86 made a similar mistake changing the licence from the MIT one to something with an advertising clause. Once the dust had settled, we had a deaf XFree86 & a lively X.org
"Those who cannot remember the past are condemned to repeat it" -- most likely writer and philosopher George Santayana
I wasn't worried, I used elm until I moved to a GUI based mail client.
@astro_jcm I just closed my latest Alpine session 5 minutes ago. I still use it for my personal email.
I still have the same mail boxes there I've had since 1995.