Subscription email notifications not working
have seen some other posts but still having serious problems. Have the latest versions of WordPress and bbPress but users are not receiving notifications when subscribing to topics or forums. Have tried the patch in 2618 but still not working.
Emails not working can be caused by many factors. Try working through the following :
1. Spam filters
You should be aware that many spam filters strip messages that do not come from the correct address. So if your site is mysite.com and your email address in wordpress settings>general is @gmail.com">email@example.com then it is likely that messages will be dumped in transit. You need to set up email to come from your site eg @mysite.com">firstname.lastname@example.org, your hosting provider can help if needed.
2. Just bbpress?
Then you need to see if this is wordpress wide or just bbpress.
then come back
thanks for the response it is much appreciated.
I have now fixed this for topic subscriptions by following the support thread below and email notifications are being received. However forum subscription notifications are still not working. Would you know why it is working for topics but not forums?
“I have just added a patch, you need r5409 applied before adding 2618.4.diff”
My email in settings is set to my site’s email , and I tested it with the plugin you suggested too, it says its all good:
This test email proves that your WordPress installation at “Mysite” can send emails. Sent: Wed, 11 Feb 2015 08:27:40 +0000
Subscribers also receive email notifications from buddypress- if somebody replies to their comment, or tags them in a post – or a bbpress thread.
Just no email at all if one is subscribed to the forum, topic or replies.
I am not using the mandrill service (wpMandrill), so this solution I think- does not apply to me https://bbpress.org/forums/topic/problem-with-the-default-do-not-reply-email-address/
and my server is bluehost.
The forum is a big part of my site’s community life , so the fact that there are no email notifications is pretty upsetting.
I searched this forum and for days, really hope there is a simple solution.
P.s I also tested it without any plugins but bbpress, default theme and reinstalled bbpress. Still no email are being received.
@netweb I would really appreciate if you could take a look at this thread too.
there is another one that seems unresolved here
thank you so much.
but for some reason the plugins don’t help..
I tested with a few accounts, and no emails for subscribed forums or topics are being received.
can I just clarify something here as my problem is different to milenushkas in that the fix of r5409 applied before adding 2618.4.diff definitely worked for subscribing to Topics and Replies.
However there is still an outstanding issue in terms of subscribing to Forums which is exhibiting some weird behaviour. I worked on this late into the night and found your plugins and was hoping the topic- subscribe would solve the issue when subscribed to a forum but unfortunately it didn’t.
For anyone else following this thread my understanding from @netweb (Stephen Edgar) is that when you are subscribed to a Forum a user will only be notified of New Topics and not to changes within existing ones which you need to subscribe to separately.
So last night I tried the following:-
1. As admin created a new topic in the backend. Absolutely no notifications received by other users subscribed to the Forum to show a new topic has been created but admin notified of pending Topic as expected.
2. As a user created a new topic in the frontend. Absolutely no notifications received by other users subscribed to the Forum to show a new topic has been created but admin notified of pending Topic as expected.
3. Weird behaviour. As admin created a topic in the frontend and this time a message was received by the user and admin !! However both the user message and admin message contained strange text. For the user at the beginning before the normal message of “You are receiving this email because you subscribed to a forum.” it showed the following – nb the items in bold have been changed for security purposes.
Content-Type: text/plain; charset=UTF-8
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname – pxxxxxxxxxx.prod.phx3.secureserver.net
X-AntiAbuse: Original Domain – aol.com
X-AntiAbuse: Originator/Caller UID/GID – [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain – mywebsitename
X-Get-Message-Sender-Via: pxxxxxxxxxx.prod.phx3.secureserver.net: acl_c_authenticated_local_user: myusername
On the Admin notification I am getting the information below. However one thing I have noticed that is different to the email notifications for the topics and reply that is working is that the From details are showing as Website Name <mail@websiteurl> in the Forum notifications instead of Website Name <noreply@websiteurl>.
The To details are showing as <noreply@websiteurl> on both the Forum Notifications and Topic/Replies Notification so somehow there is an issue with the From details picking up my default email address instead of the <noreply@websiteurl>.
A communication failure occurred during the delivery of your message. Please try resending the message later. For more tips to help resolve this issue, see DSN code 5.4.1 in Exchange Online – Office 365. If the problem continues, contact your email admin.
The following organization rejected your message: DB3FFO11FD020.mail.protection.outlook.com.
(NB the proper notification message is also attached within this information)
Hope there is sufficient for you to troubleshoot this but cannot understand why a user creating a topic in the frontend and an admin creating a topic in the backend doesn’t generate any email but an admin creating a topic in the frontend does generate an email but contains spurious information for both the user and admin.
thanks for posting that full description – I have been through it, and only wish I could say “well in that case…”
Clearly subscriptions continue to cause problems. I am only a user of this software who tries to help others, I’m not one of the authors.
I’m not really sure what to suggest next – you would have though this was easy !
Thanks Robin for looking at this for me.
Appreciate this is difficult. Any idea how I can get this to the attention of one of the authors.
Not really they don’t seem to visit here much nowadays !
they mostly communicate on SLACK especially a meeting on Wednesdays.. they do creep the forums sometimes though
Any idea how I can get this to the attention of one of the authors
you could go on slack in the #bbpress channel and notify @jjj , there was another user who had an issue with subscriptions and he might look into it.
@robin-w you might as well check the slack channel too , especially on Wednesdays
Apologies for the delay in getting back to you.
I have had a look at the link provided for slack and not sure if I am being thick or what but it is not that obvious how to get in touch with @jjj. I did click on his name but it is taking me to a buddypress site so cannot work out how to get through to him. In any event it says there was no activity found.
In the interim I have come up with a workaround as my issue is only around the subscription to Forums. As mentioned in the trail above the fix of r5409 applied before adding 2618.4.diff definitely worked for subscribing to Topics and Replies.
Therefore I have just through css removed the Subscribe element on the Forums page. I am happy in that if anyone is that interested in a topic within the forum that they will subscribe to it via the actual Topic and that does work.
Thank you for all your help but it would be really helpful if there was a more transparent way of getting support for the more serious problems. Appreciate the authors will not answer all questions in the forum given the large number but filtering out basic functionality bugs and addressing the issues would be helpful and probably reduce the number of support queries raising the same request.
Kind regards and once again thank you.
- You must be logged in to reply to this topic.