Troubleshooting Outlook, Apple Mail and Phone Mail Clients

Setting up a desktop or phone mail client to use iWebVault email usually takes a minute and works perfectly. When it doesn’t work, the failure is almost always one of a handful of specific issues — wrong server hostname, wrong port, wrong encryption setting, blocked IP. This guide walks through the common problems and how to fix each, with notes specific to Outlook, Apple Mail, and iPhone/Android.

The settings that always apply

Regardless of mail client, these are the correct settings:

cPanel → Email Accounts → “Connect Devices” button next to your mailbox shows the exact settings for your specific account. When in doubt, use those.

“Cannot verify server identity” / SSL warning

iPhone/Mac sometimes shows this on first connection. Usually means the SSL certificate’s hostname doesn’t exactly match what you typed.

• If you entered mail.yourdomain.com — make sure that hostname has SSL (cPanel → SSL/TLS Status). Re-run AutoSSL on the mail subdomain.
• If you entered the bare server hostname (something like server.iwebvault.com) — the cert is probably for a different domain. Use mail.yourdomain.com instead.
• Last resort: tap “Continue” / “Trust” — the connection works, just with a warning. Better to fix the underlying issue.

“Cannot send mail” but receiving works

Common asymmetric failure. IMAP (receiving) works on port 993; SMTP (sending) fails. Causes:

Port 25 blocked by ISP

Many ISPs block outbound port 25 from home/mobile networks to prevent spam. Symptom: SMTP fails with timeout or “couldn’t connect”.

Fix: switch your client’s SMTP port from 25 to 465 (SSL) or 587 (STARTTLS). iWebVault accepts both; ISPs don’t block these.

SMTP authentication required, not enabled

Many clients separately configure incoming and outgoing auth. Outgoing must have:

• “Use authentication” checked / enabled.
• “Use same settings as incoming” or username/password explicitly entered.

Without auth, the server rejects all sends (it would otherwise be an open relay).

Wrong encryption type

• Port 465 → SSL/TLS encryption.
• Port 587 → STARTTLS encryption.
• Port 25 → no encryption (and often blocked anyway).

Mismatched port + encryption = silent failure. Match them per the table.

“Wrong password” but password is correct

• Username format wrong. Must be full email address, not just the local part. Use you@yourdomain.com, not you.
• Password contains special characters mishandled by client. Test with a simpler password to confirm. If it works, the original had problem characters — generate new password without ampersands, plus signs, or other URL-special characters as a workaround.
• You changed the password recently and client cached old. Some clients ask for password again on next failure; some don’t and silently retry. Remove the account from client, re-add with new password.
• Your IP got blocked by CSF. Repeated failed logins from the client trip the firewall. From a different network (mobile data), try webmail with the same credentials — works? Then your IP is blocked. See CSF guide.

Outlook-specific issues

Outlook keeps prompting for password

Common Outlook glitch. Fixes:

• Delete the cached credential. Windows: Control Panel → Credential Manager → Windows Credentials → find the entry for your mail server → Remove. Outlook prompts fresh on next start.
• Profile corruption. Outlook → File → Account Settings → remove the account → re-add.
• Check encryption settings match. Outlook is picky about TLS/SSL settings — verify both incoming and outgoing match the table above.

Outlook downloading mail then redownloading

POP3 configured instead of IMAP. POP3 downloads mail and (depending on settings) deletes server copies — devices can fight over mail. Always use IMAP on iWebVault.

Remove the POP3 account; add as IMAP.

Sent items don’t sync to other devices

Outlook stores sent items locally by default even on IMAP. Fix: Outlook → File → Account Settings → click your account → More Settings → Sent Items tab → “Save sent items in” → select the Sent folder on the server (under the IMAP folder list).

Apple Mail / iPhone-specific issues

“Connection to server failed” on Apple Mail

Apple Mail caches settings aggressively. After any change:

• Mail → Preferences → Accounts → your account → Server Settings → verify both incoming and outgoing settings are correct.
• If settings look right but still failing: untick “Automatically manage connection settings” (allows manual port/encryption control).
• Restart Mail.app entirely.

iPhone: “The mail server is not responding”

• Toggle WiFi/cellular — try the other.
• Settings → Mail → Accounts → your account → verify Server Settings.
• Outgoing Mail Server section: tap your SMTP server → verify “Use SSL” on, port 465, authentication on.
• Delete and re-add the account if settings look right but it persists.

iPhone shows unread count that doesn’t match folder

Cache mismatch. Settings → Mail → Accounts → your account → toggle off, then back on. Resyncs from server.

Android-specific issues

Gmail app can’t auto-detect settings

When adding your custom domain email to Gmail’s Android app:

• “Other” account type (not Google).
• “Personal (IMAP)” if asked.
• Enter incoming server mail.yourdomain.com, port 993, SSL.
• Enter outgoing server mail.yourdomain.com, port 465, SSL.
• Username = full email address for both.

Samsung Email app issues

Samsung’s stock email client has quirks. Common fix: delete account, re-add with manual settings (not auto-detect). For persistent issues, switch to Gmail app or K-9 Mail (open source alternative).

Sending mail “as” a different address

Many clients support multiple identities — sending as contact@yourdomain.com from a mailbox configured as you@yourdomain.com:

• Apple Mail: Preferences → Accounts → your account → Email Address field accepts comma-separated list.
• Outlook: Add the second address as an alias of the account.
• Gmail (importing your iWebVault mail): Settings → Accounts → “Send mail as” → Add another email address.

Receiving side: forwarders to your real mailbox handle inbound. Sending side: identity configuration in your client handles outbound. Forwarder strategy guide.

When to switch clients vs. fix settings

If you’ve spent more than 30 minutes troubleshooting one client and webmail works fine with the same credentials, the issue is the client. Quick test:

1. Visit yourdomain.com/webmail.
2. Log in with your mailbox credentials.
3. If webmail works: server is fine, issue is in client config.
4. If webmail fails: server-side issue. Open a ticket.

What’s next

• Initial setup details: Email setup guide.
• If outbound is being filtered as spam: Deliverability guide.
• If you’ve been blocked by CSF for failed logins: CSF guide.

95% of mail client problems trace to four causes: wrong username format, wrong port/encryption combo, ISP blocking port 25, or CSF blocking the client’s IP. Check those four first, fix what’s wrong, and almost everything else falls into place.