I'm encountering an issue with SendGrid email delivery in my application when deployed to Azure. The problem occurs specifically in a layered (multi-tier) architecture, while the same code works perfectly in a single-layer setup and also functions correctly in local development environments.
Do we need configure an Extra in Layred solution
1 Answer(s)
-
0
In a layered (multi-tier) ABP solution, email sending (including SendGrid or SMTP) must be configured in the correct layer—typically in the Web or HttpApi.Host project, not just in the Application or Domain layer. This is because background jobs or email services may run in different processes or containers, and each must have access to the correct configuration.
Ensure that your email settings (such as SendGrid API key, SMTP host, port, username, and password) are present in the appsettings.json of the deployed Web/Host project, and not only in the shared or application layer. In Azure, also check that these settings are present in the App Service Configuration (Application settings) if you override them there.
If you use background jobs for email sending, verify that the Background Worker or Job Host also has the correct configuration.
For SendGrid, if you are using the ABP Emailing system, you may need to implement a custom IEmailSender or use MailKit as described in the documentation. Make sure the dependency injection is set up in the correct module (usually in the Web/Host module).
Double-check that the correct settings provider is used and that the settings are not being overridden or missed due to the layered deployment.
Review logs in the deployed environment for any exceptions or configuration errors related to email sending.
Sources:
- https://docs.abp.io/en/abp/latest/Emailing
- https://docs.abp.io/en/abp/latest/MailKit
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
