[SOLVED] Appwrite's Mail worker exposed as an Email service with an interface?

Hey, I actually just want to confirm if there's any way to interact with Appwrite's Mail Worker (or "email service") via any (REST/SDK/whatever) interface?

Eg, if you would like to send an Email in an Appwrite Function, do you need to implement your own SMTP service (and the needed libraries), even though there's already one configured for Appwrite to use "internally"?

TL;DR

The user asks if there is a way to interact with Appwrite's Mail Worker (email service) through an interface. The response states that currently, the Mail Worker is internal-only and cannot be accessed through the REST API. Users need to implement their own SMTP service if they want to send emails in an Appwrite Function. However, the Appwrite team is actively researching ways to simplify sending emails and SMS and it is planned for future releases. The user expresses interest in subscribing to an issue/roadmap to stay updated on the feature's release. No solution is provided in the thread.

Hey there 👋 We didn't expose mail worker to REST API. The worker is internal-only, and you would need to use your own smtp client library.

We are actively researching ways for an API to simplify sending emails and SMS in general (alongside push notifications feature). This will most likely come with a way to also send custom messages in them. Stay tuned 🤞

Thank you, that sounds very promising - exactly what we need.

Where can I subscribe to an issue/roadmap to keep an eye on the issue/feature so that we'll know immediately when it has been released... (or made available for testing)?

Not sure, let me ping @Jake , he might have more insights. I know for sure it won't be part of Appwrite 1.3. For Appwrite 1.4 it's possibility but no promises. I know for sure it's planned for this year.

We're working on making a public roadmap.

Here's a related discussion on Messaging: https://github.com/appwrite/appwrite/discussions/905

Sound like you don't need help with implementing this, since you already have a team, but rather time to discuss and agree upon how it gets implemented? I just want to mention that we can make time available for such a feature implementation if you actually do need help.