3 ms·
Is it more or less the same problem as running a GNU Mailman listserv in 2022? That is to say, a fairly hard problem of staying on top of security patches, avoi
by deepdriver 4y ago
Is it more or less the same problem as running a GNU Mailman listserv in 2022? That is to say, a fairly hard problem of staying on top of security patches, avoiding getting marked as spam, and avoiding getting put on the big email provider's badlists. In theory, the problem seems simple: replace a manually-managed BCC list with an alias to said list, so it's less hassle for the user/sender. Maybe the answer is an email client plug-in that just autofills BCC to-addresses? Assumption would be the user's sending this email from a known provider like GMail or Fastmail.
I imagine it would be easier for the completely self-hosted email system if signup gave receivers a from-address they could whitelist, if their email provider allows it. Maybe you already do this.
Edit: I'm also assuming email is sent one-way to whoever signs up, maybe with a link to the dynamic chat server/app/platform of the moment. Slightly different from a GNU Mailman list, which enables back-and-forth conversation.
- philip1209 4y agoYes, a little bit. I'm working on a different project that's more of a refreshed Google Groups / GNU Mailman listserv, and that has even more complexity for allow-lists: https://booklet.community https://booklet.community > I imagine it would be easier for the completely self-hosted email system if signup gave receivers a from-address they could whitelist, if their email provider allows it. Maybe you already do this. Yeah, that could be possible. I'm not opposed to releasing a self-hosted version of Postcard - but it's been useful to not have that constraint from the beginning. For instance, email sending happens in an async queue backed by Redis - and that might just be unnecessarily complex for a self-hosted tool!