WP 7.1.1 compatibility?

  • Aharon

    (@spaceling)


    1 week, 3 days ago

    Hi Erik,

    I’m troubleshooting some recent CF7 form sumbmission errors on our site and just wanted to check-in whether SMTP for Contact Form 7 was compatible with WP 7.1.1. I’m noticing that our first batch of form failures began on 17 September when the v.7.1.1 rolled out. The message we’re getting on sending a test email is “OOOPS something went wrong!” which is far less verbose than what I remember receiving when sending test emails months ago. (My other troubleshooting suspect is Cloudflare in case there is some additional DNS issue that we need to address.) Attaching a screenshot.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Aharon

    (@spaceling)

    1 week, 1 day ago

    The good news: while troubleshooting, I was able to get SMTP working again with the “SMTP Mailer” plugin. Still not sure why SMTP for Contact Form 7 is choking…

    Plugin Author Erik

    (@codekraft)

    1 week ago

    Hi Aharon,

    thanks for reporting this.

    I don’t think WordPress 7.1.1 itself is the cause. There haven’t been any relevant changes to the WordPress mail handling in the recent updates, and I’ve also tested the plugin with 7.1.1 without experiencing this issue.

    Could you please enable WordPress debugging (WP_DEBUG and WP_DEBUG_LOG), reproduce the failed test email, and check the resulting wp-content/debug.log?

    CF7 SMTP also writes additional information there when debugging is enabled, so hopefully the log should tell us quite quickly whether the problem is coming from the SMTP connection, the plugin, PHP, or something in between such as Cloudflare.

    If you can paste the relevant part of the log here (removing any credentials or sensitive information), I’ll take a look.

    Thanks!
    Erik

    Thread Starter Aharon

    (@spaceling)

    1 week ago

    Unfortunately, I haven’t seen anything reported to our debug.log (with WordPress debugging active and writing to it). We are now using WordPress 7.1.2 with AIOS and Cloudflare. Like I wrote, SMTP Mailer is working with the same SMTP plugin settings (insofar as those are accessible via the plugin’s admin page). Here’s the message followed by the debug options:

    Logs has been started in Tue Sep 22 2026 15:08:53 GMT-0400 (Eastern Daylight Time)Let's start a new server connection… OOOPS something went wrong!

    Debug Options{ "version": "1.1.2", "enabled": true, "custom_template": false, "report_every": false, "report_to": "***@***.***", "preset": "custom", "host": "░░░.opensiddur.org", "port": 465, "auth": "ssl", "reply_to_email": "", "insecure": false, "user_name": "***@***.***", "user_pass": "***", "from_mail": "", "from_name": "", "log_retain_days": 30, "auth_type": "basic", "auth_method": "smtp", "oauth2_provider": "", "oauth2_client_id": "", "oauth2_client_secret": "", "oauth2_access_token": "", "oauth2_refresh_token": "", "oauth2_expires": "", "oauth2_user_email": "", "oauth2_connected_at": "", "form_templates": { "3882": "none", "3883": "none", "44960": "none" }, "smtp_mode": "cf7", "oauth2_tenant_id": "" }

    Since there isn't a result I can copy from a failed test email aside from what I shared above, I'll add the result of the successful test email relayed via SMTP Mailer. (I may have over-redacted the information here, so let me know if it'd be better to send anything to you privately.)

    2026-09-22 19:14:47 Connection: opening to ssl://░░░.opensiddur.org:465, timeout=300, options=array()
    2026-09-22 19:14:47 Connection: opened
    2026-09-22 19:14:47 SMTP INBOUND: "220-░░░-░░░.░░░.com ESMTP Exim 4.100 #2 Tue, 22 Sep 2026 19:14:47 +0000"
    2026-09-22 19:14:47 SMTP INBOUND: "220-We do not authorize the use of this system to transport unsolicited,"
    2026-09-22 19:14:47 SMTP INBOUND: "220 and/or bulk e-mail."
    2026-09-22 19:14:47 SERVER -> CLIENT: 220-░░░-░░░.░░░.com ESMTP Exim 4.100 #2 Tue, 22 Sep 2026 19:14:47 +0000 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
    2026-09-22 19:14:47 CLIENT -> SERVER: EHLO opensiddur.org
    2026-09-22 19:14:47 SMTP INBOUND: "250-░░░-░░░.░░░.com Hello opensiddur.org [ ]"
    2026-09-22 19:14:47 SMTP INBOUND: "250-SIZE 268435456"
    2026-09-22 19:14:47 SMTP INBOUND: "250-LIMITS MAILMAX=1000 RCPTMAX=50000"
    2026-09-22 19:14:47 SMTP INBOUND: "250-8BITMIME"
    2026-09-22 19:14:47 SMTP INBOUND: "250-PIPELINING"
    2026-09-22 19:14:47 SMTP INBOUND: "250-PIPECONNECT"
    2026-09-22 19:14:47 SMTP INBOUND: "250-AUTH PLAIN LOGIN"
    2026-09-22 19:14:47 SMTP INBOUND: "250 HELP"
    2026-09-22 19:14:47 SERVER -> CLIENT: 250-░░░-░░░.░░░.com Hello opensiddur.org [162.244.93.16]250-SIZE 268435456250-LIMITS MAILMAX=1000 RCPTMAX=50000250-8BITMIME250-PIPELINING250-PIPECONNECT250-AUTH PLAIN LOGIN250 HELP
    2026-09-22 19:14:47 Auth method requested: UNSPECIFIED
    2026-09-22 19:14:47 Auth methods available on the server: PLAIN,LOGIN
    2026-09-22 19:14:47 Requested auth method not available:
    2026-09-22 19:14:47 Auth method selected: LOGIN
    2026-09-22 19:14:47 CLIENT -> SERVER: AUTH LOGIN


    2026-09-22 19:14:47 SMTP INBOUND: "235 Authentication succeeded"
    2026-09-22 19:14:47 SERVER -> CLIENT: 235 Authentication succeeded
    2026-09-22 19:14:47 CLIENT -> SERVER: MAIL FROM:<░░░@opensiddur.org>
    2026-09-22 19:14:47 SMTP INBOUND: "250 OK"
    2026-09-22 19:14:47 SERVER -> CLIENT: 250 OK
    2026-09-22 19:14:47 CLIENT -> SERVER: RCPT TO:<░░░@░░░.░░░>
    2026-09-22 19:14:47 SMTP INBOUND: "250 Accepted"
    2026-09-22 19:14:47 SERVER -> CLIENT: 250 Accepted
    2026-09-22 19:14:47 CLIENT -> SERVER: DATA
    2026-09-22 19:14:47 SMTP INBOUND: "354 Enter message, ending with "." on a line by itself"
    2026-09-22 19:14:47 SERVER -> CLIENT: 354 Enter message, ending with "." on a line by itself
    2026-09-22 19:14:47 CLIENT -> SERVER: Date: Tue, 22 Sep 2026 19:14:47 +0000
    2026-09-22 19:14:47 CLIENT -> SERVER: To: ░░░@░░░.░░░
    2026-09-22 19:14:47 CLIENT -> SERVER: From: Open Siddur Project <░░░@opensiddur.org>
    2026-09-22 19:14:47 CLIENT -> SERVER: Subject: testing after temporarily deactivating SMTP Mailer
    2026-09-22 19:14:47 CLIENT -> SERVER: Message-ID: <░░░@opensiddur.org>
    2026-09-22 19:14:47 CLIENT -> SERVER: X-Mailer: PHPMailer 7.1.1 (https://github.com/PHPMailer/PHPMailer)
    2026-09-22 19:14:47 CLIENT -> SERVER: MIME-Version: 1.0
    2026-09-22 19:14:47 CLIENT -> SERVER: Content-Type: text/plain; charset=UTF-8
    2026-09-22 19:14:47 CLIENT -> SERVER:
    2026-09-22 19:14:47 CLIENT -> SERVER: testing
    2026-09-22 19:14:47 CLIENT -> SERVER:
    2026-09-22 19:14:47 CLIENT -> SERVER: .
    2026-09-22 19:14:47 SMTP INBOUND: "250 OK id=1x95x3-0000000BfLL-1haF"
    2026-09-22 19:14:47 SERVER -> CLIENT: 250 OK id=1x95x3-0000000BfLL-1haF
    2026-09-22 19:14:47 CLIENT -> SERVER: QUIT
    2026-09-22 19:14:47 SMTP INBOUND: "221 ░░░-░░░.░░░.com closing connection"
    2026-09-22 19:14:47 SERVER -> CLIENT: 221 ░░░-░░░.░░░.com closing connection
    2026-09-22 19:14:47 Connection: closed
    • This reply was modified 1 week ago by Yui. Reason: privacy edit
    Plugin Author Erik

    (@codekraft)

    1 week ago

    Hi Aharon,

    thanks — just to clarify, the log I was asking for was the WordPress debug.log, not the SMTP transaction log generated while sending an email.

    That said, the log you sent was still very useful because it made me realize where the problem is in CF7 SMTP’s diagnostic flow: the current test can hide the underlying wp_mail() / PHPMailer error behind the generic “OOOPS” message, so at the moment we’re not seeing the real cause of the failure. I’m fixing that part so the actual error is properly exposed.

    There is one useful difference in the information you sent, though: CF7 SMTP currently has an empty From Mail, while the successful SMTP Mailer test is sending with an explicit From address.

    Could you please try setting CF7 SMTP’s From Mail to exactly the same sender address used by SMTP Mailer — ideally the same address used for SMTP authentication — and run the test again?

    That will help us rule out a sender/envelope restriction on the SMTP server while I fix the error reporting.

    By the way, I contacted the WordPress.org forum administrators because I noticed that the SMTP credentials in the log are written in Base64. So even though they may have looked obfuscated and weren’t immediately obvious, they were actually exposed and publicly visible for a while.

    The administrators have now removed that part from the post, but I would strongly recommend changing the SMTP password anyway.

    Thanks again, your report has already uncovered a couple of things in the test/debugging path that need improving.

    Thread Starter Aharon

    (@spaceling)

    6 days, 20 hours ago

    Thanks Erik. I get it that the specific log you’re asking about concerns the WordPress debug log and CF7 SMTP’s output to the debug.log as a result of my sending the test message. As I wrote, nothing was written to it by CF7 SMTP, so there’s nothing I can share with you from it. (Other things do get written to it, so I can assure you that our debug.log is active.) The lack of any expected text written to the active debug.log might be indicative of whatever might also be causing the OOOPs message for all I know.

    In the advanced options of CF7 SMTP, I added the same email and name as I added to SMTP Mailer’s settings. Nothing has changed; same OOOPs message with nothing written to the debug log. One thing to note: clicking the [ Check DNS now ] button resulted in a DNS error message just below that field. In AIOS, we Disallow unauthorized REST requests, but I don’t have any idea whether that would affect this DNS test in CF7 SMTP.

    Thank you also for noting the exposed credentials and your due diligence in getting that removed, and warning me to change our SMTP password. (Done.)

    • This reply was modified 6 days, 20 hours ago by Aharon.
Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

Tags