Hi y'all! I just set up my misfin server, would anyone be interested in helping me test deliverability? you can send me to r@bdr.sh

Nov 27 · 3 weeks ago · 👍 roughnecks, curry

12 Comments ↓

I don't have a misfin address, yet, but would be interested in hosting a server.. Can I ask which one did you choose and if you followed any how-to?

I went with misfin-server (https://gitlab.com/clseibold/misfin-server) and followed the install instructions in the readme. It was fairly straightforward.

Some things that weren't in the list that I did that aren't in the readme:

1. Adding the service to firewall-cmd

2. Copying the binary over to `/usr/bin/` and then running `restorecon -Rv /usr/bin/misfin-server` so selinux doesn't complain

3. Create the systemd .service file

Other than that, the `init` is super friendly and easy to follow.

Any idea why in the releases page it says "Version 0.5.2 [DEPRECATED]"? That's the latest version.

I'm not entirely sure about that. On the tags there's 0.5.10c (and 0.9.10c which I'm not sure if it's another branch) from october 2024. I installed from the master branch

just saw that, thanks

Sorry, I haven't made a release on the releases page. After 0.5.2, I just started making tags instead. Also, I think 0.5.10c was accidentally duplicated or something. Not really sure what happened there. 0.5.2 is the old verion without misfin(c) support. The "c" after the version number means it supports both misfin(C) and misfin(B).

Anyways, the best bet is to use the master branch.

Also, you can always upgrade versions (on run, the new version will handle any mailbox and settings file upgrades), but you cannot downgrade.

0.9.10c shouldn't be a version that exists. I think that must have been an accidental tag or something. It's also on an older version than 0.5.10c, lol. Have no idea how that happened at all! Pretend like the 0.9.10c tag doesn't exist, lol :D

I'll get it deleted when I can.

@rbdr I just sent you a message and I got a reply from the "admin" account on your server, but its mesage was empty.

@roughnecks That is how the servers verify each other. When you send a message to a server that has never seen you before, an empty "verification" message is sent to your mailbox to get the cert fingerprint for that mailbox and store it for the TOFU cert system, and then it compares that with the certificate used to send the message.

It basically ensures that every message that is sent is always sent with a valid certificate that has a known mailbox. Empty messages are just the way the servers ask for verifications.

You shouldn't be seeing empty messages in your inbox on the gemini UI, however. If that's happening, then I may need to check things.

@roughnecks message received. Thanks for the correspondence :). And thanks @clseibold for the tooling that made it possible, easy to set up and works great.

You know, you could also reply, so I'll test mine as well.

Nevermind, I received your message as well \o/

I just made an account on Roughnecks misfin server, I'll send you a test email.