Darshana

Hi @slier,

Thanks for reaching out!

At the moment, WP Mail Logging does not include a built-in feature, filter, or constant to store email logs in a separate or remote database. The plugin is designed to use the same database as the WordPress installation.

That said, I’d be happy to pass this along to our developers as a feature suggestion.

Thanks again for the feedback, and please let us know if you have any other questions.

Hi @developermr,

Thank you for getting in touch!

Per the ww.wp.xz.cn forum guidelines, we aren’t able to move support conversations to private email channels, as support must remain transparent here on the public forums.

I’ve discussed this behavior with our development team to see how we can best assist. Because One Click Demo Import is an open-source framework integrated with thousands of custom themes, it is difficult for us to provide direct support for individual themes. Our policy is to step in only if the OCDI plugin itself is explicitly causing the issue or failing to trigger a hook correctly.

Because of this, we won’t need you to send over the actual theme files. Instead, to help us determine whether this is an OCDI core bug or a separate third-party conflict, could you please share the relevant text from your debug.log or the specific code snippet used to register the import?

You can safely paste the log text here, or share it via a public link using a service like Pastebin or GitHub Gist.

Specifically, our developers would like to see:

• The PHP fatal error or stack trace
  Does the trace pass through an OCDI core file, such as /wp-content/plugins/one-click-demo-import/, or is it contained entirely within the Cost Calculator Builder plugin or the theme directory?
• The JSON/XML payload error
  Is there a specific function in OCDI that is failing to parse the file or hand off the data correctly?

If the logs show that an OCDI core function is breaking or improperly halting the sequence, we will accept it as a bug and work on a fix for our plugin.

When you get a chance, please share the debug logs or error traces, and we’ll be happy to take a closer look.

Thank you!

Hi @joelo246,

Thanks for reaching out! If your Gmail authorization suddenly stopped working, the most common cause is that the existing Google connection expired or needs to be reauthorized. Google can show an “This app isn’t verified” warning during the custom Google app setup flow, so seeing that screen by itself does not necessarily mean WP Mail SMTP is broken.

A few things to check:

1. Go to WP Mail SMTP > Settings
2. Remove the current Google/Gmail connection
3. Reconnect the mailer and complete the Google authorization flow again

If you changed your Google password or enabled 2FA/MFA after the original setup, that can also require reconnecting the account.

Alternatively, you can also try creating a new Google app and reconnecting the Gmail mailer by following our guide here: https://wpmailsmtp.com/docs/how-to-set-up-the-gmail-mailer-in-wp-mail-smtp/

Sometimes recreating the Google app and going through the setup again resolves authorization issues like this.

Let us know how it goes. Thank you!

Hi @developermr,

Thanks for reaching out! I’ll check your request with our developers and get back to you once I receive more information from them.

I appreciate your patience in the meantime. Thank you!

Hi @btork,

Thanks for reaching out, and I’m sorry for the trouble.

The error you’re seeing means that your site is unable to connect to Google’s OAuth server:

cURL error 28: Failed to connect to oauth2.googleapis.com port 443

Since you also mentioned that the WP Mail SMTP settings page takes around 10 minutes to load, this points more to a server-level connection or timeout issue rather than a problem with your WP Mail SMTP configuration itself.

Because you’re using GoDaddy hosting, I’d recommend contacting their support team and asking them to check whether your server is able to make outbound connections to:

oauth2.googleapis.com on port 443

You can let them know that your WordPress site is timing out while trying to connect to Google’s OAuth endpoint, and ask whether there are any firewall, DNS, or outbound connection restrictions on the server.

You can also share your Site Health info (WordPress Tools >> Site Health) with them.

I hope this helps. Thank you!

Hi @roman123234,

I hope everything is going well! Since we haven’t heard from you in a while, we’re going to go ahead and close out this thread.

However, if you still need assistance, just respond back at any time and it will reopen this thread.

Thanks!

Hi @caitlin33,

Thanks for reaching out! It is great that your test email is already working. That is always the biggest hurdle! However, to keep your deliverability high and prevent future issues, we do highly recommend double-checking both the From Email and Return Path settings.

Here is a quick breakdown of why they are important, even for a basic setup:

Force From Email: We generally recommend checking this box. Many contact form plugins default to sending notifications using the website visitor’s email address as the “From” address. Strict email providers (like Gmail or Yahoo) will flag this as “spoofing” and block the email entirely. Forcing the From Email ensures all emails are sent from your authenticated address, which keeps them out of the spam folder.

Return Path: We also recommend checking the box to Set the return-path to match the From Email. If an email fails to deliver (for example, if you send a reply to a user who made a typo in their email address), the bounce notification needs a place to go. Setting the return path ensures those bounce messages come back to you, and it also helps align your emails with standard anti-spam policies.

Double-checking these settings will help ensure your setup runs smoothly in the background without triggering any spam filters.

I hope this helps. Thank you!