Yes, but collective.ifttt is triggered per content action instead of scheduling the curation of all related content that should be sent out. Think of it as a newsletter but instead, it is sent to discourse. Use some form of scheduling (celery + redis) to utilize the power of the Collection content type to get all related content is what I'm gearing towards. Using Collection as the content driver, it allows multiple use cases.
At the moment, I'm using Mail chimp with Discourse inbound email for new topics... However, I'm running my own Mail Server using Mailu docker image and Discourse server. I'm using Mailu to create unlimited email boxes and email aliases. In addition, each member of JaD gets an email alias, e.g. oshane@jamaicans.dev, to anonymized their personal email address, while still providing a public email address to be contacted through.
I want to eventually stop using MailChimp and use something like Products.EasyNewsletter, but to update that plugin, it is not worth it. Plus, MailChimp is great and it is geared towards newsletter....
Reference
Mailu is a simple yet full-featured mail server as a set of Docker images. It is free software (both as in free beer and as in free speech), open to suggestions and external contributions. The project aims at providing people with an easy setup, easily maintained and full-featured mail server while not shipping proprietary software nor unrelated features often found in popular groupware.
Main features include:
- Standard email server , IMAP and IMAP+, SMTP and Submission
- Advanced email features , aliases, domain aliases, custom routing
- Web access , multiple Webmails and administration interface
- User features , aliases, auto-reply, auto-forward, fetched accounts
- Admin features , global admins, announcements, per-domain delegation, quotas
- Security , enforced TLS, Letsencrypt!, outgoing DKIM, anti-virus scanner
- Antispam , auto-learn, greylisting, DMARC and SPF
- Freedom , all FOSS components, no tracker included