[Steven]

Yes, @netweb, thanks for digging into this!

Unfortunately bbPress notification was one of the primary the reasons I searched for and ended up using Mandrill, so bypassing it is not really an option for me.

I really have not delved too deep in the bbPress notification functions for action/filters … are there sufficient actions/filters hooks in place for me to write my own plugin which will restore the pre 2.5.4 notification functionality?

[Steven]

@netweb

Yes, I did both. 2618.4.diff would not affect me though. I did verify the email address was correct in the Mandrill dashboard, noreply@connections-pro.com, but they were still being rejected.

I made sure to deactivate two plugins I’m using to make sure they were not inferring just incase they need to be updated to work correctly with the bcc change.

Those plugins were:
https://wordpress.org/plugins/bbpress-custom-reply-notifications/
https://wordpress.org/plugins/bbpress-new-topic-notifications/

I saw that both @jchristopher and @sudar mention they had to hardcode an email address that wpMandrill knows about. I’m wondering if I need to use one of the new filters to change the noreply address to a real valid address for wpMandrill to send the email without rejecting it. If I could figure out what they did to resolve their issue, but use a filter instead of hard coding it, that seems like it would solve my problem in a update safe way.

For now I’m still using the functions.php file from 2.5.3 (I have 2.5.4 installed).

What I mean by previous method is, in 2.5.4, notifications are sent as a “group” bcc was as in 2.5.3 it was one email per notification (right?).

[Steven]

I’m using wpMandrill too and my emails are still being rejected after applying r5409. I’m guessing this is because I now need to hook into one of the new filters to change the noreply to a valid/real email address. Is that correct? If it is, which filter should I hook into? Right now, the only way I’ve been able to get my notifications working again was to revert the functions.php file the version in 2.5.3. I know this band-aid isn’t the best method but at least I’m up and running again, I’d like to make sure I have this fixed correctly for future updates.

Last question … is it going to be possible to revert to the previous method of send notifications without having to hack core files?