💾 Archived View for bbs.geminispace.org › u › clseibold › 5591 captured on 2023-12-28 at 16:20:29. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-14)
-=-=-=-=-=-=-
Re: "I tried to send a message to rfc@misfin.org with the python..."
So, I might have found the problem, but I'm not sure. When the python program asks for your hostname, it's asking for the address you want to bind to, and assuming it's also the hostname people should use to email you with. I have been putting in "auragem.letz.dev", which I set to resolve to "127.0.0.1" in my hosts file. Additionally, in the make_cert command, the python program seems to run "x509.DNSName(hostname)" for the SubjAltName of the cert. This assumes that the hostname you listen on is the same as your DNS SubjAltName in your cert. This probably breaks for everyone that doesn't have loopback.
I changed the python program to listen on all available IP addresses instead (by using "0.0.0.0" in the bind function). @gemalaya Thanks for helping me figure this out!
@lem-two @lem I suggest making the python program simpler by using the "hostname" argument into the script as the SubjectAltName of the cert, and using "0.0.0.0" as the bind address so that it binds to all addresses.
I haven't tested this yet, but I think the changes I made will solve my issue... hopefully.
Edit: The changes fixed me being able to send to another computer from within my own network. Now I just need someone else to try to send to clseibold@auragem.letz.dev
Sep 26 · 3 months ago
📷 billsmugs · Sep 26 at 19:10:
@clseibold That seems to have fixed it - I've just sent a message and received a success response
🚀 clseibold · Sep 26 at 19:16:
@billsmugs Yay! Thanks! This is a good lesson for all developers, don't use the SubjAltName of the cert as the same as the bind address! Not everyone supports loopback! Imo, they should be handled completely separately.
I tried to send a message to rfc@misfin.org with the python client but it blocks when trying to connect.