Fix email from your WordPress site.
Find the saved entry, read the sending error and check a real test before resending. Kibi Forms’ local email tools work without a CRM account.
Follow the setup steps ↓
Follow the task, step by step.
- Open Kibi Forms → Email log. Find the failed notification and read its reason; check the saved entry in the Inbox.
- With your site administrator, configure an SMTP plugin such as WP Mail SMTP, FluentSMTP or Post SMTP. If one is already installed, review that setup first.
- Connect the business’s approved mailbox or sending service using that plugin’s instructions. Set an authorised From address for your own domain.
- Return to Email log and choose “Send a test”. Check the recipient inbox and spam folder, then answer “Did it arrive?”.
- After resolving the cause, use Resend on the relevant failed notification and inspect the new attempt. Test a fresh public form submission too.
Check the saved enquiry before troubleshooting mail
Kibi Forms saves a submitted entry in the WordPress Inbox before sending notification emails. If an email fails, open the entry and check the visitor's request there while you work on the notification. The saved record and the email are separate parts of the workflow. This is not a guarantee against hosting or database loss, so continue to maintain the site's normal backups and access controls.
Give someone responsibility for reviewing those entries while email is unreliable. A business can otherwise repair its mail settings and still overlook the original request. Use the Inbox to identify what needs a response, and keep the troubleshooting discussion separate from the visitor's information. Kibi Forms' local form and entry tools do not require a paid CRM account. Fixing WordPress email does not require connecting the site to Kibi CRM.
Distinguish waiting, failed and sent
Open Kibi Forms' Email log and find the relevant notification by its subject, recipient and time. “Didn’t send” means the site reported a sending failure; read the plain-language reason and use Details when you need the diagnostic code. “Still waiting” points toward scheduled tasks rather than an email already rejected by the mail server. Use the cron guide for that branch instead of changing an otherwise working mailbox password.
“Sent” means the site handed the message to its mail server. It does not confirm arrival in the recipient's inbox. The message can still be filtered, delayed or placed in spam later. The WordPress mail reference makes the same distinction between a successful sending request and receipt. Use “Did it arrive?” to check the recipient side, and keep that observed result separate from the site's sending status.
Use the site administrator and approved mail service
Have an administrator login for this WordPress site and identify who manages the business's email service and domain. If an SMTP plugin is already configured, review it before installing another one. Ask the site administrator which sending route is intended and keep the existing configuration available for reference. Several unrelated mail settings changed together make it harder to identify what fixed the problem or what should be restored.
An SMTP plugin lets WordPress send through a configured email service. Examples include WP Mail SMTP, FluentSMTP and Post SMTP; follow the chosen plugin's current setup instructions for the service your business uses. Hosting, mailbox or sending-service charges may apply separately. Kibi Forms uses WordPress's mail system, so choose the mail setup for the site's needs rather than assuming an optional Kibi CRM subscription supplies a WordPress mail server.
Correct the setting the failure identifies
A “From address isn’t a real email address” message points to the site's sending identity. “A recipient address isn’t a real email address” points to the notification's recipients. “No mail server is set up” points to the site's sending configuration. Check the corresponding setting with the administrator and use the business's approved address, rather than changing the visitor's saved entry to make an invalid notification setting disappear.
If the mail server refuses authentication, review the SMTP plugin's sign-in settings with the service owner. If the site cannot reach the mail server, review the plugin's server settings and the provider's instructions with the host. Do not guess a host, port or password from another provider's example. Enter credentials only in the authorised setup flow and keep them out of screenshots, support messages and the form's notification body.
- Invalid From → check the configured sending address.
- Invalid recipient → check the notification recipient field.
- Authentication refused → check authorised mail-service sign-in.
- Server unreachable → check the provider’s connection settings with the host.
Use the address your service is authorised to send from
Set the sending identity through the SMTP plugin according to its provider's instructions, normally using an address on a domain your business controls. Distinguish the message's From address from the visitor's Reply-To: the website sends the notification, while the reply may need to go to the visitor. Using a visitor's arbitrary address as the site's sender can create a different mail problem even when the form captured that address correctly.
If the site reports sending success but the test never arrives, ask the domain or mail-service owner to review the provider's authentication guidance, including SPF and DKIM where required. Use the actual provider's records and process; this guide does not supply DNS values to copy for every domain. Keep a record of the intended sending address and who manages it so a future staff or service change has a clear owner.
Send one identifiable test and check the mailbox
Return to Email log in Kibi Forms and choose “Send a test”. Use a mailbox you can inspect, note the test time, and check both the inbox and spam folder before answering “Did it arrive?”. Record the observed result accurately. If WordPress reports a failure, return to its reason. If the sending request succeeds but no message is found, investigate the receiving and provider side with the mail-service owner.
After the test arrives, submit a fresh fictional entry through the public form. This checks the actual notification configuration as well as the general mail service. Confirm that the entry is saved, the notification has the intended recipient and the visitor sees the expected response. A general test email can succeed while one form still has an invalid recipient or a different notification setting, so keep this final form-specific check.
- General test: sending result recorded.
- Recipient check: inbox and spam reviewed.
- Form test: fresh entry and intended notification inspected.
- Visitor check: public form confirmation still works.
Resend after fixing the cause
Once the sending problem is resolved and a test succeeds, use the relevant failed notification's Resend button in Email log. Check the new attempt and recipient rather than assuming every older failure has been corrected. If an entry has more than one notification, check which one failed and which one was resent. One successful notification should not be used as evidence that every recipient or message for that entry is now working.
Avoid resending repeatedly while the cause is unknown. If a previous send was interrupted or its result is uncertain, check with the mail-service owner before creating more copies. Keep the visitor's request moving through the team's process while you verify the notification. Review the log after the resend and confirm the intended recipient can find the message; that combines the site's result with a real recipient-side observation.
Leave useful diagnostics without credentials
For support, provide the site, plugin version, time, diagnostic code and a masked description of what happened. Email log's Details are intended for the host or SMTP support, but inspect any screenshot before sharing it because subjects and recipient addresses can still be private. Never include a mail password, API key, verification code or complete customer message. State whether the entry exists, the send failed, or the send succeeded without observed arrival.
Recheck after changing a domain, SMTP service, sending address or form notification. Keep a named person responsible for looking at failed emails and saved entries, so monitoring does not depend on one administrator remembering the original repair. Email is a notification route; the WordPress Inbox remains the place to review the captured submission. If the team later needs shared ownership and planned follow-up in a CRM, evaluate that connection as a separate decision.
Decide with the details.
Does “Sent” prove the notification reached my inbox?
No. It records the site’s handoff to its mail server. Check the actual recipient inbox and spam folder, then answer “Did it arrive?” based on what you observe.
Do I need to buy Kibi CRM to repair WordPress email?
No. Kibi Forms’ local entries and email tools work without a CRM account. Use the site’s approved mail-service setup; third-party service charges may apply separately.