A bit more info on this. If anyone is
willing to research, let me know so I can coordinate.
Basically, we need to know what the
options are, how functional/robust each is, requirements to deploy
and manage each, and migration path from current state. We
currently operate a GNU Mailman listserv and use private services
for business and transactional emails.
We have three primary uses for email
services under chattanooga.digital and members' domains:
- App/service transactional emails - account creation/password
reset type emails and app outputs such as invoices and order
confirmations.
- Eventually C.D may have hundreds or even thousands of
instances of dozens of apps in numerous domains.
- We need this for community services and core/internal
apps, of which we may have a dozen or so.
- Members may use the coop's email service(s) or may have
their own instances. So a member who has an accounting app
may also have their own transactional email server.
- Business correspondence - persons with official
positions/roles in the coop need to have business accounts.
- These accounts must be auditable and owned by the coop.
So, for example, if there is a conflict or some suddenly
drops out of a key role, the board of directors should be
able to access the account for that person/role to address
the issue and/or hand it off to someone else.
- Group/shared accounts are required for major functions:
administration, operations, outreach, and support as well as
the board of directors.
- List messages for discussion and news - we would like to
offer members means to create and manage email lists for
threaded discussions and sending informational/marketing
emails and newsletters; we need both of these for our own
purposes.
- Both of these could be a multi-tenant service we provide
to members but the latter will likely be a member app.
On 7/31/26 8:24 AM, Greg Laudeman via
Advisors wrote:
I've learned the hard way about how weird email services are.
They're also pretty critical for Chattanooga.Digital. We've
tried a couple of options that were less than adequate. What we
have now should work short-term but we need something more
flexible, functional, and robust.
Does anyone know email services really well? Would anyone be
willing to do some research on options? I can give you a good
starting point and reasonably detailed requirements.
Would it make sense to organize a task force/working group on
this?
As I mentioned in a previous email, IAM is one of the next
big apps/services to figure. The two definitely need to work
together.
Thoughts? Suggestions?
_______________________________________________
Advisors mailing list -- advisors@list.chattanooga.digital
To unsubscribe send an email to advisors-leave@list.chattanooga.digital