# Troubleshooting technical issues
Technical problems can bring cold email operations to a halt. Understanding how to diagnose and fix SMTP errors, DNS issues, and infrastructure failures is essential for maintaining reliable email operations. This lesson covers common technical issues and systematic approaches to troubleshooting them.
Key Takeaways
- Systematic diagnosis beats trial and error
* - Log everything for effective troubleshooting * - Understand SMTP error codes for quick identification * - Proactive monitoring prevents many issues
SMTP error codes
Common error codes
4xx Temporary failures:
- 421: Service not available, closing connection
- 450: Requested mailbox not available
- 451: Requested action aborted: local error
- 452: Requested action not taken: insufficient system storage
5xx Permanent failures:
- 500: Syntax error, command unrecognized
- 550: Requested action not taken: mailbox unavailable
- 552: Requested mail action aborted: exceeded storage allocation
- 554: Transaction failed: message rejected
Specific common errors:
- 550 5.1.1: User unknown (invalid email)
- 550 5.7.1: Relaying not authorized
- 550 5.7.26: Email rejected due to security policy
- 554 5.7.1: Spam or virus detected
Error diagnosis process
Step 1: Identify the error code
- Extract the SMTP response code
- Note the full error message
- Check if it's temporary (4xx) or permanent (5xx)
Step 2: Understand the cause
- Look up the specific error code
- Identify the underlying issue
- Determine if it's sender or recipient related
Step 3: Implement the fix
- Apply the appropriate solution
- Test the fix
- Monitor for recurrence
DNS issues
Common DNS problems
MX record issues:
- Missing MX records
- Incorrect MX record priority
- MX records pointing to wrong servers
- DNS propagation delays
SPF record issues:
- Missing SPF records
- Incorrect SPF syntax
- SPF record too long (over 10 lookups)
- Missing include statements
DKIM record issues:
- Missing DKIM records
- Incorrect public key
- DKIM selector mismatch
- Record formatting errors
DMARC issues:
- Missing DMARC records
- Incorrect policy (p=none vs p=quarantine vs p=reject)
- Missing alignment requirements
- Incorrect reporting URI
DNS troubleshooting
Verify DNS records: ```bash # Check MX records dig mx example.com
# Check SPF records dig txt example.com
# Check DKIM records dig txt selector._domainkey.example.com
# Check DMARC records dig txt _dmarc.example.com ```
Common fixes:
- Add missing records
- Correct record syntax errors
- Reduce SPF record length
- Update DKIM keys
- Adjust DMARC policies
Propagation considerations:
- DNS changes can take 24-48 hours to propagate
- Some providers cache DNS longer
- Use low TTL values during changes
- Verify propagation from multiple locations
Infrastructure issues
SMTP server problems
Server availability:
- Server downtime
- High load causing timeouts
- Network connectivity issues
- Firewall blocking
Configuration errors:
- Incorrect SMTP settings
- Authentication failures
- Port blocking (25, 587, 465)
- SSL/TLS certificate issues
Resource limits:
- Rate limiting exceeded
- Connection limits reached
- Memory or CPU exhaustion
- Disk space full
Email client issues
Connection problems:
- Incorrect server settings
- Authentication failures
- Network firewall blocking
- Proxy server issues
Sending problems:
- Message formatting errors
- Attachment size limits
- Encoding issues
- Character set problems
Diagnostic tools
SMTP testing tools
Command-line tools: ```bash # Test SMTP connection telnet smtp.example.com 25
# Test with authentication swaks --to recipient@example.com --from sender@example.com \ --server smtp.example.com --auth
# Test TLS connection openssl s_client -connect smtp.example.com:587 -starttls smtp ```
Online tools:
- MXToolbox SMTP diagnostics
- Mail-Tester.com
- GlockApps
- Email on Acid
DNS diagnostic tools
Command-line tools: ```bash # DNS lookup dig example.com
# Trace DNS path dig +trace example.com
# Check all DNS records dig any example.com
# Check from specific DNS server dig @8.8.8.8 example.com ```
Online tools:
- MXToolbox DNS lookup
- DNSChecker.org
- IntoDNS
- DNSstuff
Monitoring tools
Infrastructure monitoring:
- Uptime monitoring
- SMTP response time monitoring
- DNS record monitoring
- Server resource monitoring
Email-specific monitoring:
- Bounce rate monitoring
- Delivery rate monitoring
- SMTP error tracking
- Blacklist monitoring
Common scenarios
High bounce rates
Diagnosis: 1. Check bounce categories (hard vs soft) 2. Analyze bounce reasons 3. Verify list quality 4. Check DNS records 5. Review sending patterns
Solutions:
- Clean invalid email addresses
- Fix DNS configuration issues
- Adjust sending volume
- Improve list hygiene
- Implement verification
Emails going to spam
Diagnosis: 1. Check authentication (SPF, DKIM, DMARC) 2. Review content for spam triggers 3. Check IP reputation 4. Verify domain reputation 5. Test with spam checkers
Solutions:
- Fix authentication issues
- Improve content quality
- Warm up IP/domain
- Reduce sending volume
- Implement feedback loops
Connection timeouts
Diagnosis: 1. Check network connectivity 2. Verify server availability 3. Review firewall settings 4. Check timeout configurations 5. Monitor server load
Solutions:
- Fix network issues
- Increase timeout values
- Adjust firewall rules
- Scale infrastructure
- Optimize server performance
Authentication failures
Diagnosis: 1. Verify credentials 2. Check authentication method 3. Review SMTP settings 4. Test with different tools 5. Check server logs
Solutions:
- Update credentials
- Correct authentication settings
- Use supported auth methods
- Generate new API keys
- Contact support if needed
Prevention strategies
Proactive monitoring
Monitor key metrics:
- SMTP response times
- Error rates by type
- DNS record health
- Server availability
- Blacklist status
Set up alerts:
- Critical error alerts
- Performance degradation alerts
- DNS change alerts
- Blacklist alerts
- Resource threshold alerts
Regular maintenance
Weekly tasks:
- Review error logs
- Check bounce rates
- Verify DNS records
- Monitor blacklist status
- Review performance metrics
Monthly tasks:
- Full infrastructure audit
- DNS record review
- Security assessment
- Performance optimization
- Capacity planning
Documentation
Maintain documentation:
- Infrastructure diagrams
- Configuration details
- Troubleshooting procedures
- Contact information
- Emergency procedures
Update documentation:
- After changes
- After incidents
- When new issues discovered
- Quarterly reviews
Emergency procedures
Critical incident response
Immediate actions: 1. Identify the scope of the issue 2. Implement temporary fixes if possible 3. Communicate with stakeholders 4. Escalate if necessary 5. Document everything
Recovery steps: 1. Restore from backups if needed 2. Implement permanent fixes 3. Verify full functionality 4. Monitor for recurrence 5. Conduct post-incident review
Communication plan
Internal communication:
- Notify team immediately
- Provide regular updates
- Assign clear responsibilities
- Document decisions
External communication:
- Notify affected customers if needed
- Provide estimated resolution time
- Explain impact and mitigation
- Follow up after resolution
Conclusion
Technical issues are inevitable in cold email operations, but systematic troubleshooting and proactive monitoring can minimize their impact. By understanding common error codes, using diagnostic tools effectively, and implementing prevention strategies, you can maintain reliable email operations and respond quickly when issues arise.
Your next step should be to review your current infrastructure and implement monitoring and alerting to catch technical issues before they impact your campaigns.