• Resolved fooey

    (@fooey)


    I noticed our error log filling with this error:

    FATAL Postman: Postman: wp_mail has been declared by another plugin or theme, so you won’t be able to use Postman until the conflict is resolved.

    We do not have any other SMTP plugins and the plugin is working fine. Do you know what is causing this? We have Version 2.8.5 and looks like the errors started around Oct 20, 2023.

    thanks,

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi @fooey,

    I hope this message finds you well.

    Thank you for contacting us regarding the issue you are facing. To assist you more effectively, could you please provide us with the diagnostic test report? You can access the diagnostic test report from here.

    This information will help us to resolve the issue faster.

    Thanks and Regards,
    Support Team-WP Experts.

    Thread Starter fooey

    (@fooey)

    Mailer: postsmtp
    HostName: sitename.org
    cURL Version: 8.4.0
    OpenSSL Version: OpenSSL/1.1.1w
    OS: Linux usc253.lightningbase.com 3.10.0-962.3.2.lve1.5.73.el7.x86_64 #1 SMP Wed Aug 24 21:31:23 UTC 2022 x86_64
    PHP: Linux 8.2.12 C
    PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
    WordPress: 6.4.1 en UTF-8
    WordPress Theme: Salient Child Theme
    WordPress Plugins: Advanced Database Cleaner, Classic Editor, CookieYes | GDPR Cookie Consent, Duplicate Page, Envato Market, EWWW Image Optimizer, Gravity Forms, Smash Balloon Instagram Feed, 3D FlipBook – Lite Edition, Salient WPBakery Page Builder, MainWP Child Reports, MainWP Child, Mega Addons For WPBakery Page Builder, Metricool, Perfmatters, Popup Builder, Post SMTP, Redirection, Salient Core, Salient Nectar Slider, Search & Replace, UpdraftPlus – Backup/Restore, WebP Express, Yoast SEO, WP Rocket
    WordPress wp_mail Owner: /home/grahamwi/public_html/wp-content/plugins/post-smtp/Postman/PostmanWpMailBinder.php
    WordPress wp_mail Filter(s): PostsmtpMailer->get_mail_args
    WordPress phpmailer_init Action(s): PostsmtpMailer->phpmailer_smtp_init
    Postman: 2.8.5
    Postman Sender Domain (Envelope|Message): sitename.org | sitename.org
    Postman Prevent Message Sender Override (Email|Name): No | No
    Postman Active Transport: Other SMTP (smtp:tls:login://smtp.office365.com:587)
    Postman Active Transport Status (Ready|Connected): Yes | Yes
    Postman Deliveries (Success|Fail): 865 | 21

    Hi @fooey,

    Could you kindly deactivate the plugins one by one and switch the theme to the default theme? Keep a close eye on the notice and observe when it disappears. Initially, try deactivating the plugin or theme updated or installed before or on October 20, 2023.

    Thanks and regards,
    Support Team – WPExperts

    Thread Starter fooey

    (@fooey)

    Unfortunately I cannot do this on the live site to test if/when it stops due to disruption. I set up a staging site but it is not throwing the error there.

    I sent some test emails and everything seems to be working fine but the error log is full of these on live site. Do you know of any other reason to throw that error? There are no other plugins that utilize SMTP. thanks

    Hi @fooey,

    This error arises because wp_mail has been declared by another plugin. You can try changing the Mailer Type from PostSMTP to PHPMailer in Settings < Accounts Tab. It might resolve your issue. If the issue persists after this change, please share the details of your live or staging site on our technical support channel?so that we can connect you directly with our Technical team.

    Looking forward to getting your issue resolved.

    Thanks and regards,
    Support Team – WPExperts

    Thread Starter fooey

    (@fooey)

    I tried changing the setting from PostSMTP to PHPMailer in Settings < Accounts but it failed to send so that will not work. Since I cannot recreate this on staging I am not sure sending creds would help. Please advise.

    Plugin Support M Haseeb

    (@haseeb0001)

    @fooey

    The issue seems to be caused by a plugin conflict. To address this, I recommend cloning your website into a staging environment and systematically disabling plugins one by one; test it and let me know the outcome.

    Thanks and regards,
    Support Team – WPExperts  

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Fatal error in error log’ is closed to new replies.