💾 Archived View for bbs.geminispace.org › s › misfin captured on 2023-09-28 at 15:47:43. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-08)
-=-=-=-=-=-=-
Discussing the Misfin mail protocol
I am not sure if there is a issue tracker for the misfin python implemenation, I would like it if the script receive-as had a parameter to set the local bind IP, e.g. I have used it with a port forwarder from my shared host to my local windows and then binding to 127.0.0.1 is necessary regardless of the cert data
I have received a misfin message that does not identify the sending domain, so I do have any way of replying and connecting to the client IP address returns a zertificate but does establish a TLS connection. The username is @flipperzero, so if anybody knows them, I have received the mail Ok, i take that back, a previous message identifies the domain as hashnix.club, so i know the user, i will just send them an email
💬 5 comments · 1 like · 8 hours ago
Misfin Golang Client Library — I have created a very simple misfin client library adapted from makeworld's go-gemini. It will let you send a request to a misfin server and get the response back, and that is pretty much it. It will also punnycode the hostname, do very simple server cert verification (check that hostname matches) if this feature is not disabled (which is an option), and handle sender certs (I prefer this name over "client cert"). Most of the credit goes to makeworld who created a...
Python client subscript error — Here is what I see from a fresh install of the python client from [https link] $ misfin listen-as k0stk.pem Traceback (most recent call last): File "/usr/local/bin/misfin", line 5, in <module> from misfin.cli import run File "/usr/local/lib/python3.7/dist-packages/misfin/cli.py", line 10, in <module> from misfin.service import serve_multi File "/usr/local/lib/python3.7/dist-packages/misfin/service.py", line 11, in <module> from misfin.letter...
Mailinglists and Recipients Line — I was thinking of how mailing lists should be implemented in a space-efficient way in misfin, and I think we could do mailinglists without mails becoming very long by using the traditional mail concept of BCC instead of CC. So, when someone sends to a mailinglist, the mailinglist will add their sender line and then send out the gemmail to each recipient, but it *does not* need to put a recipients line, because a reply then would send back to the mailinglist...
💬 2 comments · 1 like · 23 hours ago
There's now experimental support for a multi-mailbox server mode. It's possible to deliver the messages to a mbox file or a gembox file. To use the gembox format, add this in the misfin.toml: [preformatted] [https link]
💬 7 comments · 2023-09-27 · 1 day ago
I wonder how misfin messages are replyable, the client does not have to run on the same address as the server and the sender domain is not provided in the client cert unless it is set in a SAN field
💬 4 comments · 2023-09-27 · 1 day ago
My Misfin Server Gitlab Repo — I have put my misfin server up on gitlab for anyone who wants to experiment with it. It is in very early stages of development atm and doesn't support a multi-user setup yet.
💬 2 comments · 2 likes · 2023-09-27 · 1 day ago
Misfin Server Ideas — I believe I have written a basic solo-mailbox server in golang. It is running now, so people should be able to test it at my same misfin address (clseibold@auragem.letz.dev). I wanted to outline some ideas that I have for the server: 1. I want it to support both solo-mailbox and multi-mailbox setups. 2. An interesting idea came up when I compared the spec to gemini. Gemini has this proxy ability, I believe, so that it could actually proxy other gemini servers. This led...
💬 18 comments · 1 like · 2023-09-27 · 2 days ago
So, I just wanted to write here what I noticed about the spec allowing for two different server configurations. I think thinking of it in this way helped me to start figuring out how I should write my misfin server. 1. One-mailbox server. The (self-signed) server certificate has a mailbox name in its USER_ID field, as per the spec. 2. Multi-mailbox server. There's one (self-signed) server certificate that acts as a CA that signs each mailbox certificate. Does the server certificate still need...
💬 1 comment · 2023-09-27 · 2 days ago
I've changed a few things in the misfin code: - pass flake8 test - rename the main package from "transponder" to "misfin" - Add a setup.py: "pip install ." will install all the required dependencies - Add a "misfin" command-line program (it uses the "click" module), everything can be done with this command Git repo link below [https link] misfin gitlab repository (cipres)
💬 16 comments · 2 likes · 2023-09-26 · 2 days ago
— bbs.geminispace.org/u/clseibold/5591
I think I may have fixed my server. Can someone try sending to clseibold@auragem.letz.dev? That would be very much appreciated. Thanks! Also, you can find more info about my situation below: Edit: As I was typing this, I already got a message! It works!
💬 3 comments · 1 like · 2023-09-26 · 2 days ago
SNI for misfin: I am getting a "you didn't provide SNI" error in one misfin server when I try to access it via the Python client, apparently that uses a different ssl library. I wonder if that is intended, to work it has to be active in both the client and the server
💬 20 comments · 2023-09-26 · 2 days ago
I tried to send a message to rfc@misfin.org with the python client but it blocks when trying to connect.
💬 23 comments · 2023-09-25 · 3 days ago
I have updated to the current script on sourcehut but not it is not running anymore, not sure if that is a python version issue C:\Projects\python\misfin (master) λ c:\Lang\Python38\python -m transponder.debug Traceback (most recent call last): File "c:\Lang\Python38\lib\runpy.py", line 194, in _run_module_as_main return _run_code(code, main_globals, None, File "c:\Lang\Python38\lib\runpy.py", line 87, in _run_code exec(code, run_globals) File "C:\Projects\python\misfin\...
💬 5 comments · 2023-09-25 · 3 days ago
Setup My Misfin Server — I believe I've set up a misfin server, but I was unable to send to rfc@misfin.org. Not sure if your server is down @lem-two , or if it's on my end. However, my misfin address should be clseibold@auragem.letz.dev, in case anyone wants to send me something :)
💬 5 comments · 2 likes · 2023-09-25 · 4 days ago
The return — Hi sup I'm the guy who wrote Misfin. Took a little break if you couldn't tell. The outline: 1. Life events happen 2. Spend time in the woods (metaphorical) 3. Spend time in the woods (literal) 4. Get an email that jerks you back to reality Glad to see people doing things with Misfin still. I'll be responding to things over the next couple days - feel free to hit me up.
💬 6 comments · 2 likes · 2023-09-25 · 4 days ago
Questions about verification — I'm slightly confused by the verification flow on the receiving side for misfin(B). Apologies if some of these questions are already obvious in the spec/best practices/reference examples and I've just missed/misunderstood! I'm specifically trying to implement the case where the server's certificate is a self-signed CA and there may be multiple mailboxes (each with certs signed by that CA). My understanding My understanding of the process, starting from the end of...
💬 3 comments · 1 like · 2023-07-17 · 2 months ago
Message Size — How did this limitation of 2048 bytes happen? I am personally not sold on this size; I have generated some lorem ipsum text and even without characters using 2 or even 3 bytes... emoticons and accent letters or complex letters (Asia, India etc.) ... the 2048 bytes are about two or three longer paragraphs. If the point of Misfin is to gain wider traction, maybe look at 4096 bytes? Then there would be a big counter-argument less, and I presume acceptance would be better....
💬 14 comments · 2 likes · 2023-07-04 · 3 months ago
Just read through the spec. It is interesting. I will give that it _is_ simple enough for an average developer to grok pretty easily. Unlike gemini, though, it does not seem to do much to counteract some email negatives. Ex: Since you don't need a mailserver to write outgoing mail (like smtp) it can lead to the folks writing scripts that gen a throwaway cert and spam a bunch of addresses, then gen a new cert: repeat; eventually leading to IP blocking. So we end up blocking certs and IP...
💬 4 comments · 2 likes · 2023-07-03 · 3 months ago
just took some time to read up on this project after it came up on discogem. pretty excited for an initial release to test out.
💬 View post · 2023-06-29 · 3 months ago
As I'm working on my Misfin implementation, I'm also working up some ideas for how to best make a multi-user and possibly remote setup work, with respect to users being able to read their own mail (and only their own mail). I'm going to describe some half formed thoughts I've been kicking around and see if anyone has any thoughts on the subject. This is all going to be pretty much outside the spec, as I'm thinking in terms of storage and access to it. Note that this is all in the context of...
💬 4 comments · 2023-06-10 · 4 months ago
Verification of Sender Certificate — Greetings, maybe I oversaw this in the spec, but if a client connects with a TOFU / self-signed certificate for chuck@norris.com is there any verification done to ensure that the client is not spoofing the sender address? I could think of something like a back-connection to a kind of "misfin MX" record (well SRV record would be perfect for that) and checking if the presented client certificate is signed by the norris.com server certificate.
💬 7 comments · 2023-06-07 · 4 months ago
SRV records — Any thoughts on making SRV records part of the spec? I think it adds a lot of flexibility for the server operator without much cost and can be pretty beneficial when your ISP does something boneheaded like block port 1958.
💬 7 comments · 1 like · 2023-06-03 · 4 months ago
So I have a question about GemText in Misfin. The whitespace separating the < and the address is optional. This clarifies things for the sender line, but not receiver. Should the receiver line be accepted if the whitespace following the ':' is omitted? I like to err on the side of permissiveness for the sake of interop, but it would be great to have little holes in the spec like this plugged.
💬 1 comment · 2023-06-02 · 4 months ago
Page 1 of 2