Your SMTP settings carry every email the platform sends on your behalf to your downline users and signup visitors, including:
- Signup email verification codes on your white-label signup page
- Login OTP codes sent by email
- New account welcome emails with login details
- Forgot-password emails
- Account expiry reminders and expiry notices
- Low balance and re-order point alerts
- Sender ID and message template approval or rejection alerts
- Credit transaction alerts and daily, weekly or monthly usage summaries
- Password change alerts and replies to support tickets
What happens without your own SMTP #
None of those emails reach your users. The platform does not send your users’ email through its own mail server, so there is no fallback to rely on. Every email above simply fails to arrive, which means:
- New users never receive their login details.
- Nobody can complete a password reset.
- Users with email OTP at login cannot sign in.
- Visitors cannot finish signing up on your site when email verification is on.
- Balance, expiry and approval alerts go unseen.
The one exception is a sub-reseller whose account has been given an explicit white-label fallback account: it then uses that account’s SMTP settings. This has to be set up for you by the platform team and is not automatic, so treat your own SMTP as the only thing standing between your users and silence.
Rate Notification SMTP #
Under Email Configs there is a second section, Rate Notification SMTP, with the same fields. Use it only if you want rate-change notification emails to go out through a different mailbox, for example a billing address. If you leave it empty, rate notifications use your main SMTP Connectivity settings.
A note on sender addresses #
The From E-Mail in your SMTP settings should be a mailbox you monitor on your own domain. Some emails set your registered reseller email as the reply-to, so replies from your users reach you rather than the platform.