Hello,
I recently set up MailWizz and have run into a few issues I'm hoping you can help with:
I recently set up MailWizz and have run into a few issues I'm hoping you can help with:
- One of my delivery servers, pointed at mail.evisacompany.com:465, fails with a connection timeout (Unable to connect to tcp://mail.abc.com.com:465 (Connection timed out)). I confirmed via openssl s_client directly on the server that outbound TLS to smtp.gmail.com:587 works fine, so it doesn't appear to be a general outbound port block. Could this be an IP whitelisting requirement on that mail server's end, or something in how MailWizz opens the connection?
- I switched my Gmail delivery server credentials to a proper App Password after getting repeated 535/534 authentication errors from Google. Is there anything else in MailWizz's delivery server settings that could still trigger an auth failure even with a valid App Password (e.g., protocol/port mismatch, cached credentials)?
- For the bounce server (IMAP), I corrected the hostname to imap.gmail.com with SSL on port 993 (it was previously misconfigured as gmail.com with NOTLS). Is this the correct recommended configuration for Gmail-based bounce handling, or is there additional setup needed?
- How can bounce, open, and click tracking data be reliably tied back to the correct sending domain/website when using a shared Gmail account across multiple delivery servers for different domains?