Managing ClrStream Senders
This topic explains how to manage sender accounts in ClrStream Outbound, including sender provisioning, configuration updates, deletion requests, and onboarding workflows.
ClrStream Outbound supports unlimited senders per domain.
Every sender must be registered before they can use the ClrStream Outbound service.
Only sender email IDs belonging to the Primary Domain associated with the ClrStream domain are permitted to send mail through ClrStream Outbound.
Managing Sender Accounts
All sender management activities are handled through the Mithi Onboarding Team.
To add, update, or delete sender accounts, raise a support ticket with Mithi Support and provide the required information based on the requested operation.
Add a New Sender
To provision a new sender account, provide the following details.
Required Information
| Configuration Item | Description |
|---|---|
| Name & Description | Friendly name or purpose of the sender |
| Sender Email ID | Email address to be registered |
| The sender ID must belong to the Primary Domain associated with the ClrStream domain | |
| Access Method | Specify one or more of the following access methods: |
| - SMTP | |
| - Campaign Manager | |
| - API | |
| SMTP Authentication | Select the SMTP authentication method: |
| - IP Control | |
| - User Authentication | |
| Additional Mailflow Configuration | Optional routing and archival settings: |
| - Archive to Vaultastic | |
| - Send a BCC | |
| Maximum Monthly Volume | Maximum number of emails permitted per month for this sender |
Delete a Sender
To permanently remove a sender account, provide:
| Required Information | Description |
|---|---|
| Sender ID | Sender account to be deleted |
Important:
Sender deletion is irreversible. Once deleted, the sender will no longer be able to send email using ClrStream Outbound.
Update a Sender
To modify an existing sender configuration, provide:
| Required Information | Description |
|---|---|
| Sender ID | Existing sender account to be updated |
| Updated Configuration Details | Specify the settings to be modified |
Supported Configuration Updates
| Configuration Item | Available Options |
|---|---|
| Access Method | SMTP, Campaign Manager, API |
| SMTP Authentication | IP Control, User Authentication |
| Additional Mailflow Configuration | Archive to Vaultastic, Send a BCC |
| Maximum Monthly Volume | Monthly sending limit for the sender |
Sender Access Methods
ClrStream Outbound supports multiple methods for sending email.
| Access Method | Description |
|---|---|
| SMTP | Standard SMTP-based email relay |
| Campaign Manager | Bulk and campaign email sending |
| API | Application-based email submission using APIs |
SMTP Authentication Methods
When SMTP access is enabled, one of the following authentication methods can be configured.
| Authentication Method | Description |
|---|---|
| IP Control | Access restricted to approved source IP addresses |
| User Authentication | Credential-based SMTP authentication |
Additional Mailflow Options
Optional mailflow enhancements can be configured for senders.
| Option | Description |
|---|---|
| Archive to Vaultastic | Automatically archive outbound emails to Vaultastic |
| Send a BCC | Deliver a blind carbon copy to a designated mailbox |
Request Processing Workflow
Sender creation, deletion, and update requests are processed by the Mithi Onboarding Team in two phases.
1. Validation Phase
During validation:
Request details are reviewed for completeness
Sender eligibility and domain association are verified
Configuration compliance checks are performed
2. Execution Phase
After successful validation:
Sender provisioning or deprovisioning is initiated
Configuration changes are applied
Access settings are updated
Processing Timelines
Requests requiring onboarding team involvement are typically completed within:
One working day
Actual processing time may vary depending on request complexity and validation requirements.
Best Practices
For efficient sender management:
Ensure sender IDs belong to the configured Primary Domain
Define monthly volume limits appropriately
Use IP-based authentication where possible for controlled environments
Enable archival where compliance retention is required
Review sender deletion requests carefully before submission