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 | |
| 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 |
On successful registration of a sender, you will receive the following:
- Authentication credentials (if user authentication is configured)
- Host names for SMTP configuration
- Ports to be used. You can typically choose one the following:
- 25 - TLS optional
- 587 - TLS compulsary(recommended)
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 |
| 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 |
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. NOTE: When updating the application using ClrStream Outbound service with IP based control, do not provide any authentication details for the sender. |
| User Authentication | Credential-based SMTP authentication NOTE: When using user authentication, the sender has to be the registered sender of your primary domain and the user id and password used for authentication has to be the ClrStream Outbound domain user id and password shared with you. For example, if your sender domain is "Acmecorp.com" and user is "john.smith" and the ClrStream Outbound domain is acmecorp-com.clrstream.com , then your application needs to use following configuration: Sender ID: john.smith@acmecorp.com Authentication id: As provided, typically john.smith@acmecorp-com.clrstream.com Password: As provided |
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
Recipients List Management
- Only send emails to addresses that have explicitly and willingly opted in to receive your messages. Use confirmed opt-in (double opt-in) to verify email addresses
- Remove recipients to which mail are bounced from sending list
Mail Content Creation
- Provide unsubscribe link in mail
- Use Google Postmaster tools to monitor domain sending reputation for domains
- Sender guidelines for bulk senders
- Use Google Postmaster tools to monitor domain sending reputation for domains
Shared Responsibility for Domain and Sender Reputation
Maintaining a healthy sending reputation is a shared responsibility between the customer and Mithi. The responsibilities are broadly classified as follows:
- Domain Reputation — Customer Responsibility
- IP Reputation — Mithi Responsibility
Use Google Postmaster tools to monitor domain sending reputation for domains
References
- https://redsift.com/guides/bulk-email-sender-requirements
- https://mxtoolbox.com/c/landing/gmail-and-yahoo-new-dmarc-spam-sender-requirement
Note: If any issue is identified with the domain or sender reputation that may impact service reliability, security, or deliverability, Mithi reserves the right to temporarily suspend or disable the affected sender or domain from using the service.