Does BBPress Notify work with Mailgun?

Hi kork,

I use Mailgun myself and notifications work just fine. I set it up as SMTP via wp-mail-smtp which doesn’t replace wp_mail(), but just reconfigures it for SMTP.

Try hooking into the failed wp_mail action and printing the logs to see what’s going on.

// Add to functions.php for testing.
function my_log_error( $user_info, $filtered_subject, $filtered_body, $recipient_headers, $wp_error )
{
    error_log( __LINE__ . ' wp_mail failed: ' . print_r($wp_error,1), 3, __DIR__ . '/out.log' );
}

add_action( 'bbpnns_email_failed_single_user', 'my_log_error', 10, 5 );

This will create a file called out.log inside your theme’s directory. It might shed some light into the problem.

Cheers,
Vinny

Got it working, thanks Vinny!

My pleasure. What was the problem?

Mailgun wasn’t configured on the multisite that I was using it with. I moved the settings over and sent the test and all worked as expected. My oversight!

Good to know. Please keep an eye out for mangled messages. I just received one that seems to have been caused by Mailgun changing the Content-Type headers on me.

Cheers!

Yes, the tests I had looked a little bit mangled. Shows below.

This is a MIME encoded message sent by bbPress Notify (No-Spam).

–bbpnns57bca1d4f00b8
Content-type: text/plain;charset=utf-8

Hello!
A new topic has been posted by Kork-7.
Topic title: Second Test from Kork
Topic url: HERE

Excerpt:
This is my second test.

–bbpnns57bca1d4f00b8
Content-type: text/html;charset=utf-8

<p>Hello!

A new topic has been posted by Kork-7.

Topic title: Second Test from Kork

Topic url: HERE</p>
<p>Excerpt:

This is my second test.</p>

–bbpnns57bca1d4f00b8-

Thanks. I’m opening a support ticket with them to see how to bypass this problem.

Here’s the ticket URL: https://mailgun.com/app/support/317284

I’ll update this thread with what they reply.

I’m still waiting on Mailgun’s reply, but in the meantime I released version 1.14.1 of bbpnns. In this version you can choose what type of email to be sent out: Plain Text, HTML, or Both (the multipart).

It defaults to HTML.

Cool – I’ll wait for the update to show through the site.
Thanks Vinny!

1.14.1 was released last night. If you don’t see it yet, please go to your Updates screen and click ‘Check again’.

Cheers,
Vinny

I’ve made the update and changed to plain text. It looks like “periods” are replaced with garbage characters.

Excerpt:
Ia€?m not a skeptic eithera€| Another test plain HTML.

Also, on a different note, the notifications only seem to be going out to one admin email address but there are several. It’s tracking the one (mine) fine in Mailgun and I receive it. But other admins are not? Any ideas?

It’s a multisite configuration if that matters.

Can you please provide the full message headers making sure to redact any email addresses?

Return-path: <bounce+75b9d5.3abb37-XXXXXXXXXX=XXXXXXXXXX>
Envelope-to: XXXXXXXXXX
Delivery-date: Wed, 24 Aug 2016 10:39:39 -0400
Received: from rs232.mailgun.us ([209.61.151.232]:41585)
by XXXXXXXXXX with esmtp (Exim 4.87)
(envelope-from <bounce+75b9d5.3abb37-XXXXXXXXXX=XXXXXXXXXX>)
id 1bcZL9-0003PT-7d
forXXXXXXXXXX; Wed, 24 Aug 2016 10:39:39 -0400
DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=XXXXXXXXXX; q=dns/txt;
s=smtp; t=1472049518; h=Content-Transfer-Encoding: Mime-Version:
Content-Type: Subject: From: To: Message-Id: Date: Sender;
bh=OFjcO+UyddS2H6VB45lPHKnCt3IdzscSjoZTQ8ynX7A=; b=X/27+mk1g8MVDbM3pQRqVkNA7KTOIP6yClbs++U5XOv2AUZj6n54CYA/dfxJRl0Sf8RXi2FR
7LXYYW/sMtVw5McJhAiAWXVf7f0ZcvYMLkMyRtyQewwkPdepTAdy4hC3H+UNToqmvZtVyi5k
nwXrqrMJAPZUZHCgcHOZeekUwo4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=XXXXXXXXXX; s=smtp;
q=dns; h=Sender: Date: Message-Id: To: From: Subject: Content-Type:
Mime-Version: Content-Transfer-Encoding;
b=H0WEwOBjOjN38Tzb2Wj2OS9ZCBaPR1p6FbHBisM/mtW/BxmdK+m1Vy1XM4f3uzChBDGdw5
x2Y7U/aXwDKg5TYhca6FXTo0JGrbKrCHqFAzl0cJyk64TcgYvPOjd+mk8qkn7ZPWMlvUGobF
hO6duUL0iLJ7zDsMbYDyvpUE7ulz0=
Sender: XXXXXXXXXX
Date: Wed, 24 Aug 2016 14:38:38 +0000
X-Mailgun-Sid: WyI5NTA0MiIsICJjc2ltcHNvbkBmb2NhbGl0eS5jb20iLCAiM2FiYjM3Il0=
Received: by luna.mailgun.net with HTTP; Wed, 24 Aug 2016 14:38:36 +0000
Message-Id: <20160824143836.45615.47378.15475DA2@XXXXXXXXXX>
X-Mailgun-Track-Opens: true
X-Mailgun-Track-Clicks: true
X-Mailgun-Campaign-Id:
X-Mailgun-Tag: https://XXXXXXXXXX
To: XXXXXXXXXX
From: XXXXXXXXXX
Subject: =?UTF-8?Q?[Resilient=20Living=20?==?UTF-8?Q?Communi?=
=?UTF-8?Q?ty]=20Reply=20To:=20Started?==?UTF-8?Q?=20as=20a=20sk?=
=?UTF-8?Q?eptic?=
Content-Type: text/plain; charset=”utf-8″
Mime-Version: 1.0
Content-Transfer-Encoding: base64

SGVsbG8hDQpBIG5ldyByZXBseSBoYXMgYmVlbiBwb3N0ZWQgYnkgQ29yYnktNy4NClRvcGljIHRp
dGxlOiBSZXBseSBUbzogU3RhcnRlZCBhcyBhIHNrZXB0aWMNClRvcGljIHVybDogaHR0cDovL2Vt
YWlsLnJlc2lsaWVudGxpdmluZy5jYS9jL2VKeVZqczBLd3lBUWhKOG1Ic1ZfemNGRG9QUTl6Q1ky
Z3BvUVRhRnYzMjJ2UFJXV1lSbS0yWjNGeXpEUDBwTGtCZU9HT2FHNGtrNGFxclRobWlvcnJhTmNL
NnR2a3hnVU85ZVdjbHByei1tWjZvTkNJSnRua2NsUllpeUNYbzNSSXJJWWhGc0VNTU1BSXNsLTZf
MFk1RFNJTzg3dkVUUmhMLVdxcWI5d2pfdDVsZllsal93eHhPaFF5ZW1ocFhLMHZXS1Z1RVBJeUZO
TWt2N1BoemUtbVUySA0KDQpFeGNlcnB0Og0KScOiwoDCmW0gbm90IGEgc2tlcHRpYyBlaXRoZXLD
osKAwqYgQW5vdGhlciB0ZXN0IHBsYWluIEhUTUwu

Those headers have all been modified by Mailgun. Argh! What’s the non-garbled text? Can you copy and paste it between backticks here?

I’m going to try another approach to this whole thing in the meantime. It might fix all of the Mailgun issues.