Skip to content
PK Hosting
Troubleshooting

Email not sending or landing in spam

Fix SMTP authentication, the right ports, and SPF/DKIM so your mail is delivered.

Last updated

First separate a sending error from a delivery or spam problem. Keep the full error message or bounce: it often names the failing account, DNS record or recipient policy. Do not send repeated test messages to a large list.

If the message will not leave your mail app

  1. Try webmail for the same mailbox. If webmail works, compare your app's outgoing server name with the one in your service details.
  2. Check that SMTP authentication is enabled with the full mailbox address and current password. Use the secure submission port documented for your mailbox; ports 465 (implicit TLS) and 587 (STARTTLS) are common, but the server name and settings must match your account.
  3. Send one message to an address you control. If it still fails, give support the exact error, time, sender, recipient domain and mail app, but never your password.

If mail sends but is rejected or goes to spam

Read the bounce before changing DNS. Check that the domain's SPF record includes each legitimate sender, DKIM is enabled for the actual sending provider, and DMARC aligns with the visible From domain. Do not create a second SPF TXT record. Follow our SPF, DKIM and DMARC guide for a staged setup. Google's sender guidelines explain authentication and alignment requirements; they do not guarantee inbox placement.

If you use a campaign platform, configure that provider's domain authentication and unsubscribe requirements there. Shared mailbox hosting is for correspondence, not bulk newsletters. If only one recipient domain rejects mail, send support the bounce code and recipient domain so the specific failure can be investigated.

Still need a hand?

Open a ticket from your dashboard with your domain and a screenshot β€” our team replies fast.