💾 Archived View for bbs.geminispace.org › s › misfin › 5642 captured on 2023-12-28 at 16:20:22. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-11-14)

➡️ Next capture (2024-02-05)

🚧 View Differences

-=-=-=-=-=-=-

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:

[service.local.storage]
type = "gembox"

https://gitlab.com/cipres/misfin

Posted in: s/misfin

😺 gemalaya

Sep 27 · 3 months ago

8 Comments ↓

🚀 clseibold · Sep 27 at 18:22:

@gemalaya I seen the emails you sent me, but I'm unable to send an email back to you, I think. I don't know if you intended to have a msifin server setup yet or not.

😺 gemalaya · Sep 27 at 18:26:

gembox is now the default storage method. I've added gemboxr, a console gembox reader, it's pretty basic for now.

😺 gemalaya · Sep 27 at 18:29:

@clseibold Nice. No i don't have any server or VPS, i don't intend to run any misfin server, just wanted to contribute to the project.

What's missing for the multi-mailbox mode is to have a gemini interface to create mailboxes and read messages.

😎 flipperzero · Sep 28 at 11:00:

I'm using this version right now for serving single-user on my own certificate atm for test purposes. The cert is set to flipperzero@0.0.0.0 which successfully resolves to the host/domain when I send a message back to myself. I'm also able to send a message out to alexlehm@gemini.lehmann.cx

As I leave the receive server running, I seem to keep getting this message popping up every so often, I imagine as a result of an external message failing to send my way. Maybe my host isn't able to resolve after all?

"Error [('SSL routines', '', 'peer did not return a certificate')]

Aborting due to exception. "

I wonder what or who could this be :x

🤖 alexlehm · Sep 28 at 11:15:

@flipperzero ok, then that was my attempt to connect with openssl, this likely failed due to a client cert being mandatory, i can try to change that

😺 gemalaya · Sep 28 at 12:33:

Just pushed some changes that added command-line options for "receive-as":

Options:
  --listen-on, --bind TEXT  Listen on a specific network address: Examples:
                            "10.0.1.1:1958" or "example.com" or
                            "[0abc:1def::1234]:1958")
  -6, --ipv6                Force the use of IPv6

If you pass an ipv6 address with --bind you don't need to pass -6, it will detect it.

😺 gemalaya · Sep 28 at 14:33:

@flipperzero Use the latest version. Create the cert with "hashnix.club" and use the new --bind option, you can pass 0.0.0.0 too

😎 flipperzero · Sep 28 at 20:12:

ah right right, i've caught your previous comment about only contributing, yet regardless thank you so very much for all your hard work and accomodations, again. everything seems to be running really smooth now. :D