Support for Multiple Sender Addresses in SMTP Configuration

[SELISE-Rafeed-Mohammd-Sultan]

**Corteza’s current SMTP configuration allows only a single sender email address. This presents challenges for organizations that require multiple users to send emails from different addresses while maintaining email reputation, ensuring high deliverability, and preventing emails from being flagged as phishing attempts.

We propose a feature that enables sending emails from multiple authenticated sender addresses while ensuring security, compliance, and deliverability best practices.**

### Problem Statement

1. Single Email Limitation: Currently, only one email address can be used for sending emails, limiting flexibility for teams that require multiple sender addresses.
2. Email Reputation Impact: All emails being sent from a single account can impact the domain’s email reputation, making it difficult to manage sender authenticity across different use cases.
3. Phishing & Spam Risks: Changing the "From" field without proper authentication can lead to emails being marked as spam or phishing attempts.

Proposed Solution

Enhance Corteza’s SMTP configuration to support multiple authenticated sender addresses while ensuring compliance with email security standards.

Key features of this enhancement:

✅ Flexible SMTP Authentication
Support for multiple SMTP credentials, ensuring proper DKIM, SPF, and DMARC alignment for all sender addresses.
Allow authentication via OAuth2 or App Passwords (depending on the email provider).

✅ Dynamic FROM Header Selection
Users should be able to choose a sender address dynamically when sending emails.
System should validate if the selected sender address is authorized before dispatching the email.

✅ Reputation & Deliverability Protection
Ensure emails sent from different addresses do not impact the primary email’s reputation.
Implement mechanisms to prevent emails from being flagged as phishing or spam.

Use Case Example

Imagine a scenario where two users, User A and User B, work under the same organization but need to send emails from different accounts:

User A: Sends emails from [email protected]
User B: Sends emails from [email protected]
Both should be able to send emails from their respective addresses without impacting the primary sender's reputation and without causing phishing concerns.