11–20 of 86 posts
Their default Prosody config looks pretty nice; having an easy way to deploy a local chat service that has reasonable defaults like stream management, carbons (messages you sent are mirrored across all your clients), history, and HTTP-based file sharing is really nice.
I would not put all of this on the same machine. Edit: To clarify - if one line of code is fd in any of the daemons you’re running you’ll lose everything. Practice defense in depth. Minimize the damage possible.
Heads up you should probably never host your own email on the same server as your web/worker servers if you’re worried about IP leakage. Your IP is exposed on outbound mail. Using SMTP services like SendGrid won’t help, either.
What's the problem with leaking your IP address? If you host a website or any kind of API there, your IP is public anyway?
I would not put all of this on the same machine. Edit: To clarify - if one line of code is fd in any of the daemons you’re running you’ll lose everything. Practice defense in depth. Minimize the damage possible.
I can see how that kind of makes sense. But if you ask people to run it from multiple machines chances are they will throw their hands up and say too hard and not self host at all?
For example, driving is convenient. That doesn’t mean someone who has never driven before should just drive. It’s definitely better for them to taxi.
It’s a hard problem - we have to make things easier for people.
When King Sejong saw that people were illiterate, he didn’t try to force everyone to suddenly learn a difficult language - he just made an easier one.
Now korea is 99.9% literate.
Heads up you should probably never host your own email on the same server as your web/worker servers if you’re worried about IP leakage. Your IP is exposed on outbound mail. Using SMTP services like SendGrid won’t help, either.
What's the problem with leaking your IP address? If you host a website or any kind of API there, your IP is public anyway?
I would not put all of this on the same machine. Edit: To clarify - if one line of code is fd in any of the daemons you’re running you’ll lose everything. Practice defense in depth. Minimize the damage possible.
Heads up you should probably never host your own email on the same server as your web/worker servers if you’re worried about IP leakage. Your IP is exposed on outbound mail. Using SMTP services like SendGrid won’t help, either.
That reminds me of the good old days of the Interwebs: Your computer is currently broadcasting an IP address!
Imagine could get away with running this on 1G with light usage/load? Also don't see webmail here, but imagine shouldn't be too difficult to add (I don't have much exposure to the OpenBSD landscape).
Probably is trivial but I figured I'd ask anyway. A one click "email" server which allows you to receive emails from anywhere but only send emails to addresses on the current server. If I don't send emails, I don't need to worry about people not being able to receive my emails, right?
I have a small instance on AWS that forwards my outgoing email and it works great.