💾 Archived View for bbs.geminispace.org › u › satch › 14686 captured on 2024-02-05 at 12:29:47. Gemini links have been rewritten to link to archived content

View Raw

More Information

➡️ Next capture (2024-03-21)

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

Comment by 🐐 satch

Re: "I've added an SMTP <=> misfin bridge service in the python..."

In: s/misfin

Update: I modified my client to treat 60 like a 59 error and it sending works now. @gemalaya please fix your status codes because I am receiving a certificate error when I send a Misfin(C) request instead of a 59 Malformed request which my client was set up to handle.

🐐 satch

15 hours ago

4 Later Comments ↓

🐐 satch · 15 hours ago:

But NOW I'm getting a 50 Cannot allocate mailbox error which I don't know what to make of

😎 flipperzero · 13 hours ago:

@satch hmm damn that's strange, I hope that's not happening to other people's mailboxes rn :S

😺 gemalaya [OP] · 6 hours ago:

@satch Hey, thanks. Yeah i saw in the code where it's sending the 60 error, fixing that, it should send a 59 if it can't handle the request's format.

😺 gemalaya [OP] · 5 hours ago:

@satch @flipperzero Just pushed the fix, it will send a 59 error now when it can't handle the request. I'll merge the misfinC branch soon, sorry i didn't have much time to work on this lately.

Original Post

🌒 s/misfin

I've added an SMTP <=> misfin bridge service in the python implementation. Emails sent to the SMTP service will be delivered to the gembox of the recipient(s) if they have a misfin identity on the server. Message delivery is rate-limited, only non-multipart text messages accepted. Dunno if that's useful to anyone. If you run a big misfin mailserver and you want compatibility with SMTP, it's just 2 lines to add in the config file .. [https link]

💬 gemalaya · 29 comments · 1 like · 2023-10-16 · 4 months ago