Email Testing
Configure your applications to send emails to MailLinter and master professional email testing workflows. From SMTP configuration to advanced preview modes.
SMTP Configuration
MailLinter SMTP Settings
localhost2525NoneNone💡 Pro Tip: Use port 2525 to avoid conflicts with system mail servers running on port 25.
Application Examples
const nodemailer = require('nodemailer');
// Create transporter for MailLinter
const transporter = nodemailer.createTransporter({
host: 'localhost', // Your MailLinter server
port: 2525, // MailLinter SMTP port
secure: false, // No SSL for local testing
auth: null // No authentication required
});
// Send email
const mailOptions = {
from: '[email protected]',
to: '[email protected]',
subject: 'Test Email via MailLinter',
html: '<h1>Hello World!</h1><p>This is a test email.</p>',
text: 'Hello World! This is a test email.'
};
transporter.sendMail(mailOptions, (error, info) => {
if (error) {
console.log('Error:', error);
} else {
console.log('Email sent:', info.messageId);
}
});Email Preview Modes
MailLinter provides multiple preview modes to test how your emails appear across different devices and screen sizes.
Desktop
Full-width email rendering as seen in desktop clients
- Complete CSS support
- Full image rendering
- Interactive elements
Tablet
768px width simulation for tablet devices
- Medium screen layout
- Touch-friendly sizing
- Responsive breakpoints
Mobile
375px width simulation for mobile devices
- Stacked layouts
- Large touch targets
- Optimized fonts
Web Interface Features
Email Tabs
- Preview: Visual rendering with device switching
- HTML: Source code with syntax highlighting
- Text: Plain text version extraction
- Headers: Complete email header analysis
- Attachments: Download and preview files
Interactive Features
- Click links to test functionality
- Zoom in/out for detailed inspection
- Toggle between light/dark themes
- Print-friendly formatting
- Real-time compatibility analysis
Testing Best Practices
Test Early and Often
Send test emails during development, not just before deployment. Catch issues early when they're easier to fix.
- Test every template change
- Verify across all preview modes
- Check both HTML and text versions
Device-Specific Testing
Different devices render emails differently. Use all preview modes to ensure consistency.
- Start with mobile-first design
- Test interactive elements on touch devices
- Verify font sizing across screens
Content Validation
Beyond visual testing, validate your email content, links, and deliverability.
- Check all links are working
- Verify images load properly
- Test with real data, not lorem ipsum