💾 Archived View for bbs.geminispace.org › u › Supernova › 5933 captured on 2023-11-04 at 16:21:15. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Hol up a second. Yall mean to tell me that somebody's..."
@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
2023-10-06 · 4 weeks ago
@Supernove Hm... that shouldn't be happening. Somehow it's not able to open your cert.
Also, it needs to be the full file, the cert and private key, because the private key in the file is required so SSL knows that you are the owner of that certificate. If your crt file contains the cert and the private key, then that should be fine.
@Supernova I have released a new version of misfinmail that will now properly error out when the sender cert cannot be opened. Not sure if this might be what you encountered, but it was an update that needed to be done regardless. Honestly can't believe I overlooked this, lol.
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 Ah, interesting! I thought I made ~ work correctly (on all platforms), but looks like I need to look at that code again. Thanks! I'll try to fix this bug as soon as I can.
@Supernova One question, are you on Linux or Windows? (Looks like Windows from the "Documents" folder, but just want to make sure)
@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.
@Supernova Ok thanks, I will look into that as well. The problem could be the path that it's trying to save the gembox in, which is default to "~/.gembox".
I think the "~" was having a problem because I had to disable CGO as CGO links with a version of Glibc that not all platforms have, apparently, and so I think the native golang implementations of file opening might not handle "~" properly on linux, idk. It's a simple fix by just doing the same thing that I do with Windows, which is to replace "~" with the user's home directory, although I should do testing to see if the golang implementation actually gets the user's home directory correctly, lol.
@Supernova I have released a new version, version 0.4.6, with some bug fixes: https://gitlab.com/clseibold/misfinmail/-/releases/0.4.6
I've also tested it this time on my WSL instance, so hopefully the fetching, and everything else, will work this time.
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!
💬 wholesomedonut · 19 comments · 4 likes · 2023-10-03 · 5 weeks ago