Enhancement: email service provider integration about litestar HOT 3 CLOSED

I agree that this would be useful, but I still don't see why this unified API has to be Litestar specific?

from litestar.

The issue title is misleading I guess.

For Litestar Fullstack it would be pretty helpful to have some Litestar plugin which abstracts ESP specifics behind a unified API. This enables swapping out a console email backend used in development with a test server e.g. provided by mailtrap.io in staging and a email backend suitable for production like e.g. AWS SES in production. In Django swapping out the email implementation for development, staging and production is super easy using dedicated settings files + ENV vars (host, etc.).

from litestar.

I don't think that this is something that makes sense to have, as there's virtually zero framework integration necessary. Could you elaborate what features that are specific to Litestar would be useful here? The way I see it, there's nothing from preventing a 3rd party ESP library to work inside a Litestar app just like it would anywhere else.

from litestar.