-- Leo's gemini proxy

-- Connecting to bbs.geminispace.org:1965...

-- Connected

-- Sending request

-- Meta line: 20 text/gemini; charset=utf-8

Hol up a second. Yall mean to tell me that somebody's cooking up an actual mail protocol inside geminispace?


BRUH.


Now I wanna try actually messing with implementing a protocol spec from the ground up for once, instead of watching and thinking "Wow that would be cool."


Because email is a pain. Port 25 is a gateway to sadness as a sysadmin.


This, however, seems simple and clean enough to actually be fun to handle and use, AND just might work for this environment.


Nice!


Posted in: s/misfin

🍩 wholesomedonut

2023-10-03 · 8 months ago · 👍 alexlehm, flipperzero, Supernova


10 Comments ↓


😎 flipperzero · 2023-10-03 at 06:05:

Give it a go, it's exciting new yet oldschool technology. I'm in the middle of making sure I'm all set to configure a sort of misfin host for anyone to sign up and receive mail. I'm still experimenting around tho, I'm using cipres/@gemalaya 's implement for that, which is found here:

— https://gitlab.com/cipres/misfin


There's also another implement including a mailinglist/newsletter feature available via clseibold's implement which is found here:

— https://gitlab.com/clseibold/misfin-server


🔭 Supernova · 2023-10-05 at 02:03:

OK I think I got a misfin-server instance up and running. I've still got to figure out how to use a client to send and read gemmail, but now at this time of night my brain is fried. If anyone wants to try to send me a gemmail you can try at mail@supernovas.space


🔭 Supernova · 2023-10-05 at 10:46:

Woohoo! I got messages from @clseibold and @flipperzero! I just did a cat on the gembox file to see them. Now I need to get a client going (tonight or maybe this weekend).


😎 flipperzero · 2023-10-05 at 11:05:

@Supernova just to make sure, did you send a message back? I had my server down for a bit so apologies if you sent anything and I didn't see it. TBH I have no idea where to find my gembox at!! LMFAO anywho cheers, can't wait to hear more from ya :D


🔭 Supernova · 2023-10-05 at 23:29:

@flipperzero, I did not attempt to send misfin mail yet, I have yet to figure that part out. How are you sending mail? The gemini server feature of the misfin-server sounds not to hard, I just need to spend time getting it going.

I am running on Ubuntu 22.04 which doesn't have the newest version of golang. So I ended up setting up a docker of golang:alpine and running it with a volume that contains the misfin-server data. Your mailbox file should be in the mailbox-dir defined in your misfinserver.conf @flipperzero.


🔭 Supernova · 2023-10-05 at 23:48:

@clseibold, Oh that was actually easy to setup the gemini service part! I enabled it in the config, rebooted the server, scp my cert to my local PC, import into Lagrange and viola I see my mail!

Yes I did use your precompiled release binary. But I could probably setup a build stage in docker now that I have one with the proper version. Can you run Snaps on Ubuntu server? Even if you can I think I'd prefer not to. I keep my server install as vanilla as possible and run all my services in dockers.


😎 flipperzero · 2023-10-05 at 23:50:

@Supernova AFAIK on gemalaya's implement, the string is "misfin send-as (--bind adr.ess.ish.ere) cert.pem "message here"


you should get a 20 status code for a successful connection.


🔭 Supernova · 2023-10-06 at 00:29:

@clseibold, OK I am getting hung up on how to use the certificate in the misfinmail client. I did successfully copy my admin.pem certificate from my server and imported it into Lagrange to view the gemini interface of the server. However when trying to use this same file with the misfinmail client I get:

60 This mailserver doesn't accept anonymous mail, and you need to repeat your request with a certificate.


Also, Lagrange extracts a .crt version of the certificate from the .pem file, so I tried to use this as well with the mail client but got the same result. So what certificate needs to be used with the mail client?


Edit:

This is my path to the cert, which does exist. I also tried with the admin.pem file.

sender-cert: ~/Documents/misfin/mail.crt


🔭 Supernova · 2023-10-06 at 01:25:

Couldn't open certificate at location '~/Documents/misfin/admin.pem'. Make sure the cert is configured correctly in '~/misfinmail.conf' and that the cert is accessible by the user.

open ~/Documents/misfin/admin.pem: no such file or directory


But when I changed it to the fully explicit path I was able to send mail! So the ~ doesn't work when defining the cert fle.


🔭 Supernova · 2023-10-06 at 01:40:

@clseibold, I am on Fedora KDE which does provide ~/Documents, ~/Downloads, etc.

Fetch still isn't working. I get output telling me where it is fetching from and to which looks right, but no file is created and no error messages.

-- Response ended

-- Page fetched on Sun May 19 16:05:26 2024