bbpnns Reply By Email (RBE for short) is a powerful plugin. It gives your forum participants the ability to reply to new forum posts without having to log into your site. They can even dictate their emails on their phones, so no typing is required.
However, getting it set up initially can be a little tricky if you don’t understand the concept behind it. Keep reading if that felt close to home.
RBE is an extension of bbpnns. It relies on bbpnns to send the notifications to your users. When it sees a notification going out, it will change the reply-to email header of that outgoing message so that any replies go to a mailbox it has access to.
From time to time (more on that later) it will check that mailbox, parse the headers and body of each message and create the reply under the correct topic. It even respects nested replies!
By the end of this article you’ll:
As you just read, RBE needs to have access to all of the email replies so it can do its thing. To do its thing, it needs to know a few pieces of information: who’s the user posting, and what’s the forum, topic, and parent reply (if any) it should take into consideration when posting the body of the message.
There aren’t many reliable ways for it to do that without putting a huge performance hit on the WordPress database. Enter Plus Aliases (aka Dynamic Aliases).
Plus Aliases (we’ll stick with that name for convenience) are a handy feature that Gmail and a few other email providers came up with. It allows one mailbox to act as pretty much infinite mailboxes. How? By using a simple character, the + sign, to identify the actual mailbox (before it) and any combination of characters (except @) after it and send all messages to the actual mailbox.
So let’s take the email address [email protected] as an example. There are 2 parts to it: foo, the account, and foobar.com the server. What Plus Alias support does is let you send a message to something like [email protected] and still get the message as if it was sent to [email protected].
That’s really handy! Common applications for this are: reduce the number of mailboxes you need when applied in conjunction with mail rules; know which site is selling your email to spammers by using a special alias for each site you give your email to; and allow Reply By Email to know the meta data required to post a message.
So how do I get my hands on a Plus Alias, you ask?
So far there are 2 large email providers that support Plus Aliases: Gmail and Hotmail/Outlook. Oddly enough, Outlook 365 does not support them – not easily at least. The good news is that those that do are free.
You’ll find the Mailbox connection settings under
Admin > Settings > bbPress Notify (No-Spam) – Reply by Email Settings > General tab
Connections to Gmail/G Suite are NO LONGER done via oAuth. Google made changes on their end that would require site owners to go through an absurd amount of steps to get it to work. Connections now require Application Passwords. Follow these steps to set one up and simply use it in the password field of the Gmail/G Suite/Google Workspace form.
And that’s it! The connection is complete. Go ahead and click Test Connection just for kicks and let us know if something pops up other than a success message.
Until August 2023, it was my understanding that Office 365 did not support Plus Aliases without some fiddling in the Exchange server’s settings. It has come to my attention that this is no longer the case, but connection attempts using username/password fail. If this is happening to you, please try setting up an Application Password.
Post SMTP is a very handy plugin but unfortunately it’s been known to drop the reply-to header. This effectively breaks the Reply by Email add-on entirely as the reply-to header is its back-bone, so to speak.
Now that you’ve got your mailbox set up, it’s time to take RBE for a spin. The first thing you’ll need to do is to make sure bbpnns is working properly. Without it, RBE cannot set the headers that it needs to do its thing.
Setting up bbpnns is pretty trivial, if you’re working on a brand new wordpress install without any real users. Things get tricky if you have real users and don’t want to spam them with test notifications. We strongly recommend setting up a staging site to test out the settings, or you’ll run the risk of having some very angry users.
If you must test on a live site (please don’t!), then at least temporarily set the notification role to Administrator (or some custom role created just for testing) and disable Override Subscriptions to Forums and Override Subscriptions to Topics in the Topics and Replies tabs of bbpnns, respectively. Don’t forget to turn off background notifications during testing.
You may find it tedious to create new topics in the front-end for testing. We find it, too! And with that in mind we created the Send Notifications metabox in the Topics and Replies back-end. Just check the box and click Update and the notifications will be triggered.
Once you get the message out, check your test mailbox (the one that usually receives the notifications, not the one you set up for RBE). Once the notification arrives, make sure RBE modified it for its needs. This is what you should look for:
##- If you want to reply, type it above this line -##
If you’re seeing that, then things are looking good. If you’re not, feel free to contact support and we’ll take a look.
Go ahead and reply to that message. The To field should show the special RBE address. If it doesn’t and you’re using Gmail, refer to the warning above. Write anything you want in the message above that special paragraph and send the message. Check the RBE mailbox to see if the message gets there, but don’t open it! RBE looks for unread messages for performance reasons.
So you now have a message waiting in the RBE mailbox. How do you test if it’s going to work?
That’s actually quite simple. First make sure your Check Method is set up for Webhook (save the settings!). Then copy the Webhook URL (blurred in the image above) and paste it in a new browser tab/window. You should end up with a message depicting how many emails were processed. If none were processed and you saw the unread message in the RBE mailbox, please contact support. If you had too many unrelated messages in the mailbox, it could be that the script timed out while sifting through the pile looking for the emails to post. That’s why it’s important to have a dedicated mailbox just for RBE.
Go to the topic where you expect your reply to be and see if it’s there.
Depending on the email client that you used to send your reply, you may see some spurious text after the reply. That’s because some email clients add weird stuff between the actual message and the special paragraph. We have lots of code working to remove that weird stuff, for most of the common email clients actually, but some more obscure ones may still pose an issue. If that’s happening to you, please contact us so we can adjust the plugin accordingly.
Feel free to reply to your reply in the front-end and send another reply to the reply to the reply… (I lost count) via email. Once you’re satisfied with the functionality, it’s time to automate it.
RBE will let you automate it in several ways. They all involve either Cron Jobs or third-party integration (with
IFTTT, Zapier, etc.). You can even use the WordPress Cron by itself if you want, but we don’t recommend that unless you have LOTS of traffic.
You can follow this link to read up on how to set up this section, but the simplest thing is to use a Real Cron job along with the Webhook URL. Most hosts offer some sort of real cron job interface (such as cPanel). Siteground (my favorite host so far) has a good tutorial on how to set up real cron jobs in cPanel for WordPress. The steps for the webhook are pretty much the same, but the actual command that’s run is different. It’s a good idea to follow the steps outlined in that tutorial to replace the WordPress internal Cron job (just follow the steps to the letter), and then follow them again (skipping the DISABLE_WP_CRON part, which is done only once) and using the following command instead of the original one:
wget -q -O - https://yourdomain.com/?bbpnnsrbe-run=thesecretkey >/dev/null 2>&1
https://yourdomain.com/?bbpnnsrbe-run=thesecretkey in the command with your Webhook URL.
Make sure that you still have Webhook set as Check Method or you’ll get an HTTP 400 error when the cron job runs.
Only use the WordPress Cron method if you’re NOT going to use the Webhook URL anywhere and will depend on WordPress to try to respect the check frequency.
If you managed to get this far unscathed, the rest is smooth sailing. The remaining settings in this section and in the Message Processing section are pretty much self explanatory. If you choose not to delete read messages, RBE will try to move them to a special folder in your mailbox (if you’re using IMAP which is the default for Gmail and Outlook) so as to be able to process newer messages faster.
The options in the Message Processing section are mostly site owner preferences to limit what can or cannot be posted into the forums.
Version 1.9 of RBE introduced the ability to create topics via email. You’ll have to enable it in the General Settings tab.
Once you do, your users will start seeing little envelopes in the forum list screens with “mailto:” links. The email address is unique for each forum/user combination, so it won’t show up unless the user is logged in.
Any email sent to the special email address will end up becoming a new topic in that forum.
The special address also shows up in the back-end Edit Forum screen, inside the metabox where you find forum type, status, parent, and order.
You will *not* see it in categories or the new forum screen.
This part helps RBE notify everyone who needs to be notified when a reply to a new topic is posted.The section fully explains what each option does. We recommend setting this to Use bbpnns Rules, if you’re happy with your bbpnns setup and don’t have any membership plugins installed.