If emails sent from your WordPress site aren't reaching your inbox, the Post SMTP plugin fixes this by sending your mail through Titan's servers instead of WordPress's default (and often unreliable) mail function. This article is for Titan users whose domain is hosted with Heart Internet. After completing these steps, your WordPress site's emails — like password resets, contact form notifications, and order confirmations — will be delivered reliably.
Before you start
You'll need:
A Titan email account registered through Heart Internet.
Admin access to your WordPress.com site.
Access to your Heart Internet cPanel, to update Email Routing and your domain's DNS.
Install and configure the Post SMTP plugin
1. In your WordPress.com dashboard, install and activate the Post SMTP plugin.
2. In the Post SMTP setup screen, click Configure manually.
3. In the Transport field, choose SMTP.
4. In the Outgoing Mail Server field, enter localhost.
5. In the Outgoing Mail Server Port field, enter 25 or 587.
6. In the Envelope From Address field, enter an email address on your domain (for example, admin@yourdomain.com). This should match the sender address in your WordPress admin settings.
7. In the Security field, choose None.
8. In the Authentication field, choose None.
9. Click Save Changes.
You'll see a confirmation message once your settings are saved.
Update cPanel Email Routing
Once Post SMTP is configured, each domain that needs mail relayed through it must have its Email Routing setting updated in cPanel.
1. Log in to cPanel through the Heart Internet control panel.
2. In cPanel, open Email Routing.
3. For each domain, select Remote Mail Exchanger.
You'll see Remote Mail Exchanger marked as the active option for each domain once saved.
Update your domain's SPF record
An SPF record is a DNS entry that tells other mail servers which senders are allowed to send email for your domain. Updating it confirms Titan is an authorized sender, which helps your emails avoid spam folders.
1. In the Heart Internet control panel, open your domain's custom DNS settings.
2. Under TXT Record, remove any existing TXT record for SPF.
3. Under Create New TXT records, leave Subdomain empty.
4. In the Text field, enter: v=spf1 include:spf.titan.email include:secureserver.net ~all
5. Click Update DNS.
DNS changes can take up to 24–48 hours to fully propagate, so this step won't show an immediate visible change.
Confirm it's working
Send a test email from your WordPress site (for example, trigger a password reset or submit a test contact form entry). If delivery is working, the email will arrive in the recipient's inbox within a few minutes, and Post SMTP's activity log will show the message as sent successfully. If you don't see it arrive, check the Troubleshooting section below.
Troubleshooting
Test email doesn't arrive
Problem: You sent a test email but it never arrives, and Post SMTP's log shows a failure.
Cause: The SMTP settings (port, security, or authentication) don't match what your mail server expects.
Fix: Double-check each field against Step 3–8 above, particularly the port number, then save and resend the test email.
Remote Mail Exchanger option isn't available
Problem: You don't see Remote Mail Exchanger as a choice under Email Routing.
Cause: The domain may not yet be fully set up in cPanel, or you may not have the required account permissions.
Fix: Confirm the domain is listed under your Heart Internet account, or contact Heart Internet support to confirm your permissions.
Emails still land in spam after the SPF update
Problem: Test emails arrive, but in the spam folder rather than the inbox.
Cause: DNS changes take time to propagate, so the new SPF record may not be visible to other mail servers yet.
Fix: Wait up to 48 hours after updating your SPF record, then send another test email.