• Hello,

    I’m getting this since a couple of weeks with several sites but doesn’t really seem to affect messages after a while.

    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.

    Sites are on version 2.1.10
    Is it enough to switch Mailer Type from PostSMTP to PHPMailer or do recent versions correct this if I only update the plugin to 2.2.3 ?

    • This topic was modified 2 years, 2 months ago by John.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support M Haseeb

    (@haseeb0001)

    @dsl225 Hi,

    I hope you are doing well.

    Please share Post SMTP diagnostic test report.

    The Mailer type will be Post SMTP, and you can update the plugin; there will be no issues.

    Also try to disable the plugin then reset the plugin and configure it again.

    Thanks

    Thread Starter John

    (@dsl225)

    Thanks for your feedback.

    Do you mean that I can leave PostSMTP as it is and just update, right?

    This is my report after updating one of the sites.

    Mailer: postsmtp
    HostName: ------------.com
    cURL Version: 7.84.0
    OpenSSL Version: OpenSSL/1.1.1p
    OS: Linux sg1-ss13.----.com 3.10.0-962.3.2.lve1.5.70.el7.x86_64 #1 SMP Mon May 30 08:45:55 UTC 2022 x86_64
    PHP: Linux 7.4.33 C
    PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
    WordPress: 6.1.1 en_US UTF-8
    WordPress Theme: GeneratePress
    WordPress Plugins: ManageWP - Worker, Post SMTP, TablePress, FooGallery, BackWPup, iThemes Security, Code Snippets, Dashboard Notepad, Disable Gutenberg, Duplicator, Enable Media Replace, Error Log Monitor, Find Posts Using Attachment, Flying Pages, FooBox Image Lightbox, Forminator, GP Premium, Lightweight Grid Columns, Lightweight Social Icons, Local Google Fonts, MetaSlider, Official StatCounter Plugin, Plugin Notes, Really Simple SSL, Sassy Social Share, Simple CSS, Spacer, Advanced Editor Tools (previously TinyMCE Advanced), User Role Editor, Yoast SEO, WP Fastest Cache, WP Show Posts
    WordPress wp_mail Owner: /home/----/public_html/---/wp-content/plugins/post-smtp/Postman/PostmanWpMailBinder.php
    WordPress wp_mail Filter(s): wp_staticize_emoji_for_email, PostsmtpMailer->get_mail_args
    WordPress phpmailer_init Action(s): PostsmtpMailer->phpmailer_smtp_init
    Postman: 2.2.3
    Postman Sender Domain (Envelope|Message): -----------.com | ----------.com
    Postman Prevent Message Sender Override (Email|Name): No | No
    Postman Active Transport: SMTP (smtps:plain://mail.------------.com:465)
    Postman Active Transport Status (Ready|Connected): Yes | Yes
    Postman Deliveries (Success|Fail): 383 | 1
    
    Plugin Support M Haseeb

    (@haseeb0001)

    @dsl225 Yes, you can update the plugin.

    This issue comes when there is any plugin conflict with our plugin, you can try to disable and then enable the plugin and check.

    Thanks

    Thread Starter John

    (@dsl225)

    OK thanks, will see how it goes after update.

    But this happens only now after running Post SMTP since the early days and only at some sites and it’s difficult to find which plugin creates the conflict..

    Plugin Support M Haseeb

    (@haseeb0001)

    @dsl225 I am trying to reproduce this issue; also I am discussing it with my team, will try to reproduce this case, and then we will release the updated version soon.

    Thanks

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal error with PostSMTP mailer type’ is closed to new replies.