GMX SMTP Configuration
Use these exact values when configuring any email client or application to send through GMX servers.
| Parameter | Value |
|---|---|
| SMTP Host | smtp.gmx.com |
| SMTP Port | 587 (TLS) or 465 (SSL) |
| Encryption | STARTTLS on port 587, SSL on port 465 |
| Username | Your full GMX email address (e.g., user@gmx.com) |
| Password | Your GMX account password |
Note: GMX requires that you access your account via the web interface at least once every 6 months to keep it active. Additionally, GMX may block sign-in attempts from unfamiliar locations or applications. Check your GMX account email for security alerts.
Step-by-Step Setup
Follow these steps in order to configure SMTP access for your GMX account.
1. Ensure Your Account is Active
Log in to your GMX account via the web interface at least once every 6 months. GMX may disable accounts that are inactive for extended periods.
2. Handle Security Settings
GMX may block sign-in attempts from new applications or locations. If you receive a security alert, approve the access in your GMX account settings or via the security email.
3. Configure Your Application
Enter smtp.gmx.com as the SMTP host, port 587 with TLS, your full GMX email as the username, and your GMX password as the credential.
4. Send a Test Message
Send an email to yourself and an external address to confirm delivery. Check your GMX sent folder to verify the message was sent successfully.
Common Errors and Solutions
Most GMX SMTP issues fall into a handful of categories. Here's how to fix them quickly.
Sign-In Blocked by GMX
GMX often blocks third-party application access for security. Check your GMX account email for a "Sign-In Blocked" alert and approve the access. You may need to log in via the web interface first.
Connection Timeout
Port 587 may be blocked by your network. Try port 465 with SSL encryption as an alternative. Corporate firewalls commonly block direct SMTP on port 587.
Account Inactive
GMX may disable accounts that haven't been accessed via the web interface for 6 months. Log in to your GMX account through the website to reactivate it.
Daily Sending Limit
GMX has sending limits that vary by account type and age. Free GMX accounts have lower limits. For any meaningful email volume, migrate to a dedicated email service.
Best Practices for GMX SMTP
Keep your account secure and your messages deliverable with these recommended approaches.
Keep Your Account Active
Log in to your GMX account via the web interface at least once every 6 months. Inactive accounts are disabled and cannot send email via SMTP.
Approve Third-Party Access
When GMX blocks a sign-in attempt, check your account email for the security alert and approve the access. This is a common issue when first setting up third-party applications.
Use a Strong Unique Password
Use a strong, unique password for your GMX account. Don't reuse passwords from other services. Consider using GMX's security features to monitor account activity.
Watch Sending Limits
GMX has strict sending limits, especially for free accounts. For any volume above personal correspondence, migrate to a dedicated email infrastructure service to avoid limits.
When GMX SMTP Falls Short
GMX's SMTP service is designed for personal email correspondence, not application email sending. Strict rate limits, security blocks on third-party access, account inactivity requirements, and no webhook delivery notifications make it unsuitable for production automated email. A dedicated email API provides the infrastructure and observability that production transactional email requires.
For teams needing reliable transactional email at scale, SMTP relay services handle authentication, IP reputation, and routing automatically. Learn more about email deliverability and why sender reputation matters for inbox placement.
Frequently Asked Questions
What are GMX's SMTP sending limits?
GMX limits vary by account type and age. Free GMX accounts typically have 20-50 emails per day. Premium accounts have higher limits. GMX is not designed for high-volume sending.
Why is GMX blocking my SMTP access?
GMX frequently blocks third-party application access for security. Check your GMX account email for a sign-in blocked alert and approve the access. You may need to log in via the GMX web interface first.
My GMX SMTP is being rejected. What should I do?
Check your GMX account email for security alerts blocking the sign-in. Approve the access. Ensure your account is active (logged in via web recently). Try switching from port 587 to port 465 with SSL.
Is GMX SMTP suitable for transactional emails?
No. GMX is not designed for transactional email in production. It has strict rate limits, security blocks on third-party apps, requires periodic web logins, and provides no webhook delivery notifications or bounce handling.
How do I keep my GMX account active?
Log in to your GMX account via the web interface at least once every 6 months. GMX may disable accounts that remain inactive for longer periods, preventing SMTP access.
Ready to move to reliable email infrastructure?
Start free with no card, or talk to sales for high-volume and enterprise.
Start SendingTalk to Sales