WordPress (or another plugin) is currently handling email delivery, not Postman.

Look in the Diagnostic Test at WordPress wp_mail Owner. You need to deactivate the plugin which is the other owner. For example:

WordPress wp_mail Owner: /wordpress/wp-content/plugins/sendgrid-email-delivery-simplified/lib/overwrite-sendgrid-methods.php

Sometimes the Owner shows “pluggables.php”, this means that a plugin is loading a WordPress core file directly which is wrong and in order to find which one you’ll have to deactivate all of them and reactivate one at a time.

See https://www.ads-software.com/tags/wp_mail-conflict

Thanks….ultra fast response. I need all my plugins so I guess I’ll not be able to use this. Thanks though ??

I’m curious to know which one so I can notify the other author of the error.

Hi Jason, i also face the same problem, after postman update, i can’t configure email, i have deactivate all plugins, still not work, does it error from the postman plugin itself?

Post your Diagnostic Test.

Fyi: In my case, I had the same mail handling message and a iconv library missing. Installing the library cleared up both notices.

Thanks for the tip, @serenine!

Same issue. Diagnostics test:

OS: Linux gator4231.hostgator.com 3.12.44-94.ELK6.x86_64 #1 SMP Fri Jul 10 17:53:38 CDT 2015 x86_64
HTTP User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
PHP: Linux 5.4.45 C
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=Yes
WordPress: 4.2.5 en_US
WordPress Theme: Beaver Builder Theme
WordPress Plugins: Akismet, BackupBuddy, Beaver Builder Plugin (Developer Version), Captcha by BestWebSoft, Easy Google Fonts, Photo Gallery by Supsystic, Gallery by BestWebSoft, Google Sitemap by BestWebSoft, Jetpack by WordPress.com, Postman SMTP, Simple Facebook Connect, Gallery by Supsystic PRO, UpdraftPlus – Backup/Restore, Visual Form Builder, WP Featured Content Slider
WordPress wp_mail Owner: /home3/sneakypanda/public_html/wp-includes/pluggable.php
WordPress wp_mail Filter(s): wp_staticize_emoji_for_email
Postman: 1.6.24
Postman Prevent Message Sender Override (Email|Name): No | No
Postman Transport URI: smtp:ssl:plain://smtp.mail.yahoo.com:465
Postman Transport Status (Configured|Ready|Connected): No | No | n/a
Postman Deliveries (Success|Fail): 0 | 0

I see above the “pluggable.php” suggestion to deactivate my other plugins to locate the culprit, and I was reading in the “plugin not working declared by another plugin” thread a mention of a plugin by Supsystic, I use their pro version gallery plugin -so is that most likely the issue? Is this a irreconcilable conflict?

Thank you for any help.

There’s no way to fix it. Supsystic is breaking the pluggable API.

I submitted a patch to them for their Popup plugin and they may have used it. I suggest you submit the issue to them on the Gallery by Supsystic support forum and request a similar fix.

https://www.ads-software.com/tags/postman-supsystic

Ok gotcha. Thanks for your help!

If they refuse to do anything about it, is there another smtp plugin I could use or will this be an constant issue?

I was using WP Mail SMTP and that just stopped working the other day, which is why I’m trying to get your plugin to work.

There are two classes of SMTP plugins. Those that use PHPMailer, bundled with WordPress:

1. WP Mail SMTP
2. WP Easy SMTP
3. Configure SMTP
4. Mail Bank

And those that re-write the pluggable wp_mail function:

1. Postman
2. Mandrill
3. SendGrid
4. Cimy Swift

None in the second class will work for you while the Supsystic plugin is installed. And it’s unlikely any in the first class will solve your problem, if WP Mail SMTP couldn’t.

Hi,

I have the same issue, but I’ve removed all plugins. Here is the diagnostic:

OS: Linux redhead 4.1.5-x86_64-linode61 #7 SMP Mon Aug 24 13:46:31 EDT 2015 x86_64
HTTP User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/601.2.7 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.7
PHP: Linux 5.5.18-1+deb.sury.org~precise+1 C
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=Yes
WordPress: 4.3.1 en_US
WordPress Theme: tdJournal Child Theme
WordPress Plugins: Postman SMTP
WordPress wp_mail Owner: /srv/www/fromoktogreat.com/public_html/wp-includes/pluggable.php
WordPress wp_mail Filter(s): wp_staticize_emoji_for_email
Postman: 1.6.24
Postman Sender Domain (Envelope|Message): fromoktogreat.com | fromoktogreat.com
Postman Prevent Message Sender Override (Email|Name): No | No
Postman Transport URI: gmail_api:https:oauth2://www.googleapis.com:443
Postman Transport Status (Configured|Ready|Connected): Yes | No | Yes
Postman Deliveries (Success|Fail): 0 | 0

Could it be coming from my child theme?

Working now. Just some permission issues with Google.

Just a quick question though. I can’t get the sender address to be wordpress@xxx. It is put like this in Postman SMTP and in Contact Form 7, but the send from always ends up being my envelope address whatever settings I put. Any idea? Thanks in advance!

Hi @glo-1

but the send from always ends up being my envelope address whatever settings I put

If you check the session transcript, you will find that wordpress@xxx is being used as the From address/sender address.

What’s happening here is Google is changing the From address back to you when it receives the email. What you want to do is known as Email Spoofing and is generally frowned upon. For example, if you set your name and email address to mine, and send a message to my mom, she will think it’s from me, and that’s phishing.

However! If you can prove you own the sender address (wordpress@xxx) Google will allow it. See Gmail Help: Send mail from a different address or alias.

Reference: https://www.ads-software.com/tags/send-mail-as

Hey Jason,

Thanks a lot for all your explanation!
Actually I guess it doesn’t really matter, I just wanted to understand why. The wordpress@xxx email doesn’t even exist in reality, but in the past it would still worked fine until Gmail decided it was spam. Thanks again, I will keep using my personal email instead of the wordpress@xxx one.