Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀: transactional email only mode #1168

Open
1 task done
shleeable opened this issue Feb 6, 2025 · 2 comments
Open
1 task done

🚀: transactional email only mode #1168

shleeable opened this issue Feb 6, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@shleeable
Copy link

shleeable commented Feb 6, 2025

Which feature or improvement would you like to request?

Hello stalwartlabs team,

I run a mastodon / pixelfed instance and I pay a saas provider a few coins to send our transactional emails.

Image

I'd love to move to stalwart or similar to connect my fediverse instance to a email server I control.

Once the domain is trusted, I could offer the free email hosting to other fediverse email providers.

Does that fit the stalwart model/usecase? I have no intention of ever receiving an email from this service.

Is your feature request related to a problem?

I'm having a problem with... moving from a saas transctional provider.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@shleeable shleeable added the enhancement New feature or request label Feb 6, 2025
@mdecimus
Copy link
Member

mdecimus commented Feb 6, 2025

Hi,

If you need to send emails over HTTP, you could try using the JMAP API. However, if you need to keep track of clicks, opened emails, etc then yes, that is currently out of scope.

@shleeable
Copy link
Author

I have no interest in click tracking or any interactive stuff. I just want to be able to send email to users of 2-50 different fediverse instances.

My requirements for my mastodon instance is sending the outbound messages for password resets/operational emails. These are sent from [email protected] etc. I don't receive any inbound email... and I think as mentioned, If I'm looking to offer this as a service to multiple different mastodon administrators.

I could setup mox as a single domain with a mailbox for each instance ([email protected])... or maybe [email protected]

I'd require the admin portal to allow me to quickly spin up tenants with the username/password for their config.

Figure you disable the webmail/anti-spam and any other service only required by the inbound email.

finally, I'd be interesting in handling the reputation of the primary/subdomain and IPs attached to my outbound mail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants