SMTP Manager — Authentifizierte E-Mail & Protokoll — Installations- & Konfigurationsanleitung

1. Requirements#

• OpenMage LTS 19.x/20.x (best on >= 19.5 / 20.1) or Magento CE 1.9.x
• PHP 7.2–8.3 with the ionCube Loader enabled (most hosts have it; check with a phpinfo() page or ask your host)
• SMTP credentials from your provider (host, port, username, password or API key)

2. Install the files#

1. Download the package from your Imavio account (Downloads) after purchase.
2. Unzip it and upload the contents over your Magento root — it merges into app/code/local/Imavio/Smtp, app/etc/modules/Imavio_Smtp.xml and the admin layout. No core files are overwritten.
3. Flush the cache: System → Cache Management → Flush Magento Cache. The setup script creates the imavio_smtp_log table automatically.
4. The extension ships disabled by default — installing it changes nothing about how your store sends mail until you turn it on in step 4.

3. Activate your license#

1. Go to System → Configuration → Imavio Extensions → SMTP Manager → License.
2. Paste the license key from your Imavio account and save.
3. Sending never depends on license state — the license only unlocks updates and support (validated in the background).

4. Configure & test — before you enable#

1. Choose the sending channel. SMTP is the classic connection on ports 587/465/2525. HTTP API sends through your provider's API over HTTPS (port 443) and needs only an API key — pick it if your host blocks the SMTP ports (see step 6). Supported API providers: Brevo, SendGrid, Mailgun, Postmark, Mailjet, Resend.
2. On the SMTP channel, pick your provider from the presets to autofill host, port and encryption, then enter your credentials. Set HELO/EHLO name and Envelope-From if your relay needs them. On the API channel, pick the provider and paste the key — the form shows exactly which key each provider wants and its usual pitfalls.
3. Configure a failover route. The most robust pairing is an external provider as the primary route and your server's own mail server as the backup (host localhost, port 25, no encryption, no authentication) — the local server keeps working even when outbound SMTP is blocked.
4. Open the dashboard at Imavio → SMTP Manager and send a test email. The step-by-step diagnostics validate the config (including the 465+STARTTLS mismatch), check connectivity and perform a real send, with friendly hints on any failure.
5. Only once the test succeeds, flip the Enabled switch to route your store's mail through SMTP Manager.

5. Verify#

• Place a test order and trigger a newsletter — confirm both arrive from your sending account.
• Open Imavio → SMTP Manager and review the log grid: successful sends and any failures appear with the raw server reply. Use resend, CSV export or the detail view (body shown in a sandboxed iframe) as needed.
• Run the deliverability doctor on the dashboard to check MX / SPF / DMARC for your sender domain and apply the suggested DNS fixes.

6. Emails stopped arriving — what to check#

SMTP Manager warns you before your customers do: when several sending attempts fail in a row, every admin page shows a warning with the last error, and the log records the exact server reply. The warning clears itself on the first successful send.

The classic case: sending worked for weeks, then stopped overnight. On cPanel hosting this is almost always the SMTP Restrictions feature, which blocks outbound connections from user accounts to ports 25, 465 and 587 and forces all mail through the server's own mail system. Because cPanel updates itself nightly, a restriction that was not being enforced can start being enforced from one day to the next — your settings never changed, but the port is now closed. The log shows Connection timed out or Could not open socket.

Three fixes, best first:

1. Switch the channel to HTTP API. Sending then goes over HTTPS on port 443, which no SMTP restriction can touch. This is the permanent fix and needs nothing from your host.
2. Ask your host for an exception for your provider's server. It works, but the exception may not survive a panel update or a server migration.
3. Add the local mail server as failover (host localhost, port 25, no encryption, no authentication). Deliverability is lower than a dedicated provider, but emails keep going out instead of stopping completely.

Other frequent causes: an expired or revoked API key (log shows HTTP 401), a sender address that is no longer verified at the provider (HTTP 403 or 422), or a daily sending quota reached (HTTP 429 — set a pause between queued emails in the sending rules).

7. Updates & support#

New versions appear under Downloads in your account while your update window is active. An expired license never stops your emails — it only shows admin notices and pauses updates. Need help? Open a ticket from your Imavio account — support is included with your license.