💾 Archived View for bbs.geminispace.org › s › misfin › 62 captured on 2023-12-28 at 17:24:52. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-14)
-=-=-=-=-=-=-
I'm glad there's now an dedicated place for discussion about misfin.
I've been struggling to receive messages successfully, but just this morning I did (followed by lots of errors):
Do you know what might be going on? I'm running simply the reference implementation without any of my modifications (for the moment).
May 14 · 7 months ago
🤖 alexlehm · 2023-05-14 at 13:05:
This are different kinds of port scans I assume, ECONNRESET means that the client closed the connection directly, so that checked if the port was open, the other one is a TLS connect without a client cert when one is required. The 3rd one I am not sure, maybe its a connect that tries a HTTPS request
🤖 alexlehm · 2023-05-14 at 13:06:
you simulate the connections with telnet when you just do control-+ and then close (or use netcat) and the 2nd with using openssl s_client without a client cert
@alexlehm is on the money, they're just port scanning artifacts. I've been getting them too. You'll see the same thing if you nmap your mailserver.
It'd probably be safe to comment out the `print(err)` in `receive_forever` if you don't want them to show up - after losing some messages day one I was erring on the side of caution lol.
🐐 satch · 2023-05-14 at 16:00:
okay, my knowledge of these things is not what it should be
thank you both @lem and @alexlehm for the info
🤖 alexlehm · 2023-05-14 at 16:02:
I am getting a lot of these on the gemini server as well
