Your SMTP credentials — a username and password — authenticate your application when it connects to the MigoSMTP relay server. This article shows you where to find your credentials, what they look like, how to test them, and how to keep them secure.
Where to Find Your SMTP Credentials
- Log in to MigoSMTP via the Rackwave portal SSO.
- Click SMTP Accounts in the left sidebar.
- You will see a list of all SMTP accounts on your workspace.
- Click the View Credentials button or the eye icon next to the account whose credentials you need.
- The full username and password are displayed in a credentials panel.
Password security: The SMTP password is only shown when you explicitly click View Credentials, and it is masked by default. If you have lost your password (e.g. the person who created the account has left), use the Reset Password button to generate a new one — then update all applications using the old password immediately.
Your Complete SMTP Credentials
| Credential | Format / Example | Where to Enter |
|---|---|---|
| SMTP Host | smtp.migosmtp.com | SMTP server / hostname field in your app |
| SMTP Port | 587 (STARTTLS) or 465 (SSL) | Port field in your app |
| SMTP Username | smtpuser_a3b2f1c9 | Username / login field in your app |
| SMTP Password | [32-character random string] | Password field in your app |
| Encryption | TLS / STARTTLS | Encryption / security field in your app |
| From Email | yourname@yourverifieddomain.com | From address in your email configuration |
From address requirement: The From address in your email must use a domain that is verified in your MigoSMTP account. If you try to send from an unverified domain, the message will be rejected. See: Setting Up Your First Domain in MigoSMTP.
Verifying Your Credentials Work — Test with Telnet
Before integrating with your application, you can manually verify that the credentials work using the Telnet command-line tool. This confirms the SMTP server is reachable from your server and credentials are valid.
# Step 1: Connect to MigoSMTP on port 587 telnet smtp.migosmtp.com 587 # Expected response: # 220 smtp.migosmtp.com ESMTP ready # Step 2: Introduce your client EHLO yourdomain.com # Step 3: Initiate TLS STARTTLS # Step 4: Base64 encode your username and password # Run in terminal separately: echo -n "your_smtp_username" | base64 echo -n "your_smtp_password" | base64 # Step 5: Authenticate AUTH LOGIN [paste base64-encoded username] [paste base64-encoded password] # Expected: 235 2.7.0 Authentication successful # Step 6: Quit QUIT
Verifying with OpenSSL (Preferred — Handles TLS Properly)
# Connect with TLS openssl s_client -starttls smtp -connect smtp.migosmtp.com:587 -crlf # After connection, run the same AUTH LOGIN sequence as above # The advantage: OpenSSL properly negotiates TLS, unlike raw Telnet
Storing Credentials Securely
| Method | How to Use | Security Level |
|---|---|---|
| Environment variables | Store in .env file (local) or server environment (production); access via getenv(), os.environ, process.env |
Recommended |
| Secrets manager | AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, Google Secret Manager | Best for production |
| CI/CD secrets | GitHub Actions secrets, GitLab CI variables, Bitbucket repository variables | Good for deployments |
| Config file | Stored in an unversioned config file with restricted file permissions | Acceptable with care |
| Hard-coded in source | Directly in code files | Never — serious security risk |
What to Do If Credentials Are Compromised
- Go to SMTP Accounts in MigoSMTP.
- Click Reset Password on the compromised account.
- A new password is generated instantly — the old one is immediately invalidated.
- Update the new password in all applications using this SMTP account before the old one is rotated.
- Review your delivery logs for any suspicious sends that may have occurred during the compromise window.
- If you suspect unauthorised sending occurred, contact Rackwave support immediately.