New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SparkPost doesn't send bbPress subscription notifications -- might be bcc issue?? #31
Comments
Hello @cfk4spk |
Following up about the issue, I see there is a reason why HTTP API not working. However, if it's the same issue, SMTP version should work. Have you tried SMTP? |
The cause of the issue may be similar to what I noted in #32 |
Hi rajumsys - Regarding MichaelPereiralUK's suggestion, I'm unsure whether it applies for me or not. I know that BuddyPress uses bbPress, but also that the two work differently, in some ways, at least. Unfortunately, I am not a programmer / developer, and I am not sure that I understand well enough to confirm or deny. I am happy to try anything -- and / or to provide any info that might be helpful -- if you / he can tell me what you'd like to see?!? With Mandrill we used HTTP API --- and that led me to believe that I should be using HTTP API with SparkPost also. If I can / should be using SMTP, I am happy to make the change -- if I can figure out how. SparkPost IS working for us -- using HTTP API --- for our bbPress forums . . . IF I do not update bbPress beyond version 2.5.3. When I update bbPress to its current version: 2.5.8 --- the subscriptions no longer work (and they stopped at bbPress2.5.4). When bbPress was updated to version 2.5.4 -- one of the changes includes this: I'm not sure if that is 'why' SparkPost works with version 2.5.3 and does not work with version 2.5.4 - 2.5.8 --- I am merely hoping to help provide info. I will try here, to provide a few more details about our setup, in case it is helpful: We have a fairly small, private organization of approx 250 members that uses bbPress forums (we do not use BuddyPress) All of that works with Mandrill Our setup: Our site does use other plugins too, but I THINK these are the only relevant ones here. To reiterate: While it might seem logical to conclude that there is something 'wrong' with bbPress2.5.8 . . . . my confusion continues because Please let me know what I can do to help. I would really like to get this working! Chris |
addendum: |
@cfk4spk - I went ahead and downloaded 2.5.8 to look for a similar mailer implementation which is causing the issue with BuddyPress emails not sending and it seems not to be the case. I'm guessing it's related to #23 which is what rajumsys is referring to as why SMTP should work. Have you tried switching to SMTP and testing that sends before looking to see if the subscription emails send? Since the API key needs different permissions in that scenario. |
For any developers coming here, you could likely create a temporary solution for the HTTP mailer by manipulating the filters available towards the end of the subscription email function.
ref: \bbpress\includes\common\functions.php L:1161 |
Hi MichaelPereiraUK As to the temporary solution you suggest -- I don't think I'm good enough at PHP to manipulate the filters. If there's any chance that you might want to send me any hints about just how I might play around with it, I'd appreciate any insight. Presently, it is very late here, and I need to grab a couple hours of sleep - but I will be back to this as early as possible in our AM. Chris |
@MichaelPereiraUK yes, exactly that's the reason I found. bbpress sends to noreply and puts everyone else in BCC. But HTTP mailer doesn't have BCC support yet. |
Thanks rajumsys |
@cfk4spk - Just re-looked at the snippet I put through earlier. Clearly hadn't had my coffee ☕ It's not going to work as you'll be able to get the $headers variable which has all the contacts you need but you won't be able to mail out as you won't have the $message. What you could probably do however which fixes the whole BCC thing temporarily is hook onto the wp_mail filter.
Since at this point you have all the details you'll need so you can just check the headers value for BCC contacts and strip them out into an array for the to value. Again, this is just speculation and I can't say I'm too confident that it'll work out as described. |
Thanks Michael - |
Update - maybe this will help others too . . . (?) |
Just wanted to follow up if anyone else is still facing any issues regarding bcc (in bbpress) or sending with buddypress. Recently I've provided a solution to buddypress problem in #32. I'm closing this ticket for now but please feel free to re-open if necessary. |
Merge pull request #31 from wpcomvip/develop
Currently, this works with Mandrill but does NOT work with SparkPost:
Our website (WordPress) uses bbPress (forum plugin).
It allows members of our site to "Subscribe" to forum topics if they choose.
That works with Mandrill.
It does not work with SparkPost.
Can you help to figure out what SparkPost needs --- so that this will work?
Here is some info that MIGHT be 'helpful' . . .
We had needed to use a workaround ("Sudar-Fix") to make Mandrill work for the subscriptions when bbPress was at an earlier version (I can figure out the exact version, if helpful - let me know).
bbPress has apparently "incorporated" the "Sudar-Fix" into it's core, and we no longer need it, for Mandrill to work with bbPress subscriptions.
SparkPost does not work for bbPress subscriptions -- with or without the Sudar-Fix.
You can find the "Sudar-Fix" here:
http://bulkwp.com/using-wpmandrill-to-send-subscription-notification-from-bbpress/
and github info:
https://github.com/sudar/bbpress-subscription-in-mandrill
It DOES appear that SparkPost DOES work for bbPress subscriptions - when using an old version of bbPress (bbPress 2.5.3) -- but does not work with the current bbPress 2.5.8 -- I do not know for certain, at which version it stopped working, but I can try to determine -- if it might be helpful. (?)
Any advice / help / etc would be GREATLY APPRECIATED!
Please let me know if I can help --- I will try to provide any info that might help!
Thanks in advance,
Chris
The text was updated successfully, but these errors were encountered: