Connect IMAP and SMTP to a WordPress Support Inbox

Understand the two connections

IMAP synchronizes messages from the mailbox into the support workflow. SMTP submits outgoing replies through the mail server. A successful IMAP test does not prove that SMTP works, and the reverse is also true.

Treat them as separate connections with separate ports, encryption settings, and failure messages.

Use mailbox-specific credentials

Create or use the password for the support mailbox itself. Do not provide a master cPanel, hosting, WordPress administrator, or domain-registrar password.

Some providers require the full email address as the username. Others publish a specific mail host such as mail.example.com. Copy the secure settings from the mailbox provider rather than guessing.

Choose encrypted ports

Common secure combinations include IMAP over SSL on port 993 and SMTP over SSL on port 465, or SMTP with STARTTLS on port 587. Your provider’s documented values are authoritative.

Avoid disabling certificate validation to make a failed connection disappear. A hostname or certificate mismatch should be corrected.

Test incoming synchronization first

Send a new message from an unrelated address to the public support mailbox. Confirm that it arrives at the provider, appears once in the WordPress ticket view, and preserves the sender and subject.

Repeat imports should not create duplicate tickets. If they do, stop and fix message identification before relying on scheduled synchronization.

Test replies and authentication

Reply to the test conversation and inspect the received message. Confirm the visible From address, Reply-To behavior, mailed-by domain, and signed-by domain when available.

If delivery lands in spam, inspect SPF, DKIM, and DMARC alignment with the hosting provider. Do not create a blanket rule that allows all forwarded mail through spam filtering.