Troubleshooting
Common issues and how to resolve them
Troubleshooting
Solutions for common issues when sending email through NorthRelay. If your issue is not covered here, use the diagnostic tools in your Dashboard or contact support.
Connection Issues
"Connection refused" on port 587
Your network may be blocking outbound SMTP connections.
- Test connectivity from your server:
telnet smtp.north-pipe.ca 587 - If the connection times out, your firewall or hosting provider is blocking port 587. Contact your hosting provider or network administrator to allow outbound TCP on port 587.
- As a fallback, try port 465 (implicit TLS):
telnet smtp.north-pipe.ca 465
"Connection timed out"
- Verify the hostname is exactly
smtp.north-pipe.ca(notsmtp.northrelay.ca) - Check that DNS resolution works:
nslookup smtp.north-pipe.ca - Some cloud providers (AWS, GCP) restrict outbound SMTP by default. You may need to request SMTP access or use an alternative port.
TLS handshake failure
- Ensure your client supports TLS 1.2 or later
- Use STARTTLS on port 587 (not raw TLS)
- For port 465, use implicit TLS (your client should connect with TLS directly)
- Test the TLS connection manually:
openssl s_client -connect smtp.north-pipe.ca:587 -starttls smtp
Authentication Errors
"535 Authentication failed"
Your credentials are incorrect. Double-check:
- Username must be your full NorthRelay account email (e.g.,
you@example.com), not a custom domain address - Password must be a valid API key starting with
nr_live_ - The API key must be active — check Dashboard → API Keys to confirm it has not been revoked
- Copy the API key again; whitespace or trailing characters can cause failures
"553 Authentication required"
You are trying to send without authenticating first. Ensure your SMTP client is configured to use authentication with LOGIN or PLAIN mechanism.
"API key format invalid"
API keys follow the format nr_live_xxxxxxxxxxxx. If your key does not start with nr_live_, it may be a test key or an old key format. Generate a new key from Dashboard → API Keys.
Delivery Problems
Emails landing in spam
This is almost always caused by missing or incorrect DNS authentication records.
- Set up SPF — Add a TXT record to your domain:
v=spf1 include:_spf.north-pipe.ca -all - Verify DKIM — DKIM is auto-configured when you verify your domain in the dashboard. Confirm the DKIM record is published:
dig TXT default._domainkey.yourdomain.com - Add DMARC — Add a TXT record at
_dmarc.yourdomain.com:v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com
See the full DNS Setup Guide for step-by-step instructions.
Domain not verified
You must verify domain ownership before sending from a custom domain (Pro tier and above).
- Go to Dashboard → Domains
- Add your domain and follow the verification steps
- Add the required DNS records (TXT verification record)
- Click Verify — DNS propagation can take up to 48 hours
High bounce rate
A bounce rate above 5% can harm your sender reputation.
- Remove invalid addresses from your mailing list
- Use double opt-in for new subscribers
- Check the bounce reasons in Dashboard → Email Logs
- Monitor your reputation score at Dashboard → Reputation
Emails rejected by recipient server
If the recipient's mail server is rejecting your email:
- Check for a specific error code in the bounce message (visible in Email Logs)
- Run the Pre-Flight Check tool: Dashboard → Tools → Pre-Flight Check
- Check the Blocklist Monitor: Dashboard → Tools → Blocklist — this scans 13 industry-standard RBL providers
Rate Limiting
"451 4.7.1 Rate limit exceeded"
You have hit your plan's sending quota.
- Check current usage at Dashboard → Billing (the usage bar shows percentage consumed)
- Warnings appear at 80% and 100% of your quota
- Quota resets on the 1st of each calendar month
| Tier | Emails/Month |
|---|---|
| Free | 3,000 |
| Starter | 5,000 |
| Micro | 20,000 |
| Pro | 50,000 |
| Scale | 150,000 |
To increase your quota, upgrade your plan at Dashboard → Billing.
Temporary rate limiting (421)
A 421 response means the server is temporarily throttling your connection. This can happen during high-volume sends.
- Wait 30-60 seconds and retry
- Implement exponential backoff in your application
- Spread large sends over a longer time window
Email Rejected
Spam content detected
NorthRelay scans outbound email for content that may trigger spam filters. If your email is rejected:
- Avoid excessive use of ALL CAPS, exclamation marks, and spam trigger words
- Ensure the HTML-to-text ratio is reasonable (include a plain text version)
- Do not use URL shorteners in email body
Blocked recipient (suppression list)
If a recipient previously bounced or marked your email as spam, they may be on your suppression list.
- Check the suppression list in Dashboard → Email Logs → Suppressions
- Remove the address from the suppression list if you believe the issue is resolved
- Re-sending to suppressed addresses without removing them first will result in a silent drop
Diagnostic Tools
NorthRelay provides built-in tools to diagnose sending issues:
| Tool | Location | Purpose |
|---|---|---|
| Pre-Flight Check | Dashboard → Tools → Pre-Flight Check | Validates DNS records, authentication, and sending configuration before you send |
| Blocklist Monitor | Dashboard → Tools → Blocklist | Checks your sending IPs against 13 industry-standard DNS blocklist providers |
| Connectivity Doctor | Dashboard → Tools → Connectivity | Tests SMTP connectivity and TLS configuration from NorthRelay's servers |
Getting Help
If you are still experiencing issues after trying the steps above:
- Check the Dashboard → Email Logs for detailed error messages
- Run the diagnostic tools listed above
- Review the DNS Setup Guide and SMTP Configuration guides
- Contact support at support@northrelay.ca with your account email and the message ID from the Email Logs