A form submission is two events that fail separately. The entry is stored in the database, and the notification is mailed. The archive filling up while the inbox stays empty is the most common report about any form plugin, and it is always the second event.
Why the site's own mail is not enough
WordPress hands mail to PHP's mail(), which hands it to the server's mail transfer agent with no authentication. Receivers have spent twenty years watching that path produce forged sender addresses, so a message that arrives that way is treated as suspect before anybody reads it. It often lands in spam, and sometimes it is refused outright.
SMTP with a real account fixes this because the message is authenticated against a mailbox the provider knows. That is the whole argument. It is not faster and it is not more private.
The settings
On the mail screen, switch SMTP on and fill in the host, the port, the encryption, the username and the password, then the from address and the from name.
The from address is the field people get wrong. It has to be an address the SMTP account is allowed to send as, which usually means the same domain. A from address on a different domain is refused by the provider or rewritten, and the form has no way to know either happened.
Encryption is its own setting rather than a function of the port. Port 587 with TLS and port 465 with SSL are the two normal pairs, and a provider that publishes different numbers is telling you something, so use its numbers.
What the plugin does with them
The plugin hooks into the mail library only while a form email is being sent, sets the connection from your settings, and lets WordPress send. Nothing else on the site is affected, which matters on a site where another plugin also sends mail.
The verdict on whether the message left comes from WordPress's own success and failure signals, not from the value the send function returns. That distinction is the reason a broken send can be reported honestly instead of as a success.
The test send
The diagnostics run before the test, and they are worth reading first. They check the things that break a send without producing an error, such as a from address the account cannot use, and they flag the case where something else is already intercepting WordPress's mail.
That last one matters. If an API mail service or a provider plugin is installed, it takes over before WordPress sends, the test passes, and the mail went through that service rather than through your SMTP settings. The test proves the mail arrived. It does not prove the settings you just typed are the ones that carried it.
When it still does not arrive
Check the archive first, to confirm the submission was stored. Then check the provider's own sent log, if it has one, because a message the provider accepted and then dropped looks identical from inside WordPress.
Then check the spam folder of the receiving mailbox, and check that the from address is not a no-reply address the receiver has learned to distrust.
If the provider accepted it and the mailbox has nothing, the problem is delivery after the handoff, and that is a conversation with the mail provider rather than a setting in the form.
The Blue Raven plugin page describes the rest of the forms feature, and a submission that was refused is a different fault with a different cause.
EnterraHost