Sending Accounts
Add, import, test, pause, and maintain SMTP accounts and optional proxy assignments.
Sending accounts connect RSender to SMTP infrastructure you are authorized to use.
Add one account
- Open Sending Accounts.
- Choose Add account.
- Enter the sender address and display information.
- Configure SMTP host, port, username, and TLS mode.
- Store the credential through the password field.
- Add Reply-To or other supported sender settings.
- Save, then run Test connection.
- Send a test to an inbox you control.
Match TLS mode and port to the SMTP provider’s documented submission settings. A TCP connection alone does not confirm authentication or message acceptance.
Import accounts
Use the import workflow when the source file follows the fields shown by RSender. Before committing:
- inspect the preview and mapping;
- verify ports and TLS values;
- avoid duplicate sender addresses;
- confirm every account belongs to authorized infrastructure;
- protect the source file if it includes credentials.
Delete or securely archive credential-bearing import files after use according to your security policy.
Account health
The account list and detail view can show connectivity, authentication, DNS state, quota use, delivery outcomes, and linked activity. Investigate a degraded account before assigning more traffic.
Pause an account to prevent new assignments while preserving its configuration. Before deleting one, review active campaigns and choose another sender where required.
Bulk maintenance
Use bulk pause, resume, or supported field updates only after filtering and reviewing the selected accounts. Test a representative account after any common SMTP, rate, or proxy change.
Proxies
If your approved topology requires a proxy:
- Add or import the endpoint.
- Test connectivity.
- Enable it and bind it to the intended account.
- Monitor latency and failures during a small send.
Keep proxy passwords out of exports and screenshots.
Sender identity
Use a recognizable display name and a monitored Reply-To address. Rotating or variable display names should remain truthful and consistent with the recipient’s relationship to the sender.
RocketsSend Docs