Operating a mailing list with email interactions (just like Google Groups) requires running our own mail server or paying for third party.
As of this post, the Oooshiny Google Group contains 854 members
Our activity is about 5 to 10 posts a day. Assuming daily direct-email to all our members (which is an over-estimate as some do journal delivery), this means about 5 to 10k outgoing emails a day., about 300k outgoing emails a month if we are experience high-engagement.
This makes it costly to use a third-party mail server, so investigations on running full solutions such as Sovereign or Mail-In-A-Box are being tested. Spam control -- messages getting lost in spam, and maintenance are large challenges.
We can use a third-party service for this function as long as it's modular enough to switch if said third-party goes defunct, and it's affordable.
Requirements
Incoming/Outgoing SMTP
SPF/DKIM/DMARC
MTA-STS policy
SSL
No database or storage required (all emails are transactional, not archived)
Operating a mailing list with email interactions (just like Google Groups) requires running our own mail server or paying for third party.
As of this post, the Oooshiny Google Group contains 854 members
Our activity is about 5 to 10 posts a day. Assuming daily direct-email to all our members (which is an over-estimate as some do journal delivery), this means about 5 to 10k outgoing emails a day., about 300k outgoing emails a month if we are experience high-engagement.
This makes it costly to use a third-party mail server, so investigations on running full solutions such as Sovereign or Mail-In-A-Box are being tested. Spam control -- messages getting lost in spam, and maintenance are large challenges.
We can use a third-party service for this function as long as it's modular enough to switch if said third-party goes defunct, and it's affordable.
Requirements
Preliminary Candidates / Research: