PS. I just spotted that I'm using an older version older version 3.9.15218 of EasyBlog. Could that have something to do with it?

Hello Susanne,

The only reason that the emails did not go through is on your mail server. EasyBlog will actually dispatch these emails via Joomla's mailer service (Which is what you configured within the Joomla Global Configuration) area. Perhaps they landed up in the spam box?

Hello Mark,

Thanks for the quick feedback! The emails are unfortunately not in the spam boxes. There is no indication they ever reached our email server, as the log attached attests to. All other email traffic to these accounts function normally. Could there be any other Joomla-related reason why these emails didn't arrive?

Hello Susanne,

Hm, does this happen all the time or does this happened randomly? What you can do is to check the "Email Activities" at the back end of EasyBlog to see the state of the email (whether it is sent or pending)

That sounds like the place to check! But I can't find "Email Activities" in the backend of EasyBlog. Could you point me in the right direction please?

Oh, sorry it's "Mail Activities" and not "Email Activities" as "Email Activities" was used in EasySocial See my screen shot here, http://screencast.com/t/wJmUhi3Gb

Aha thank you! Now I checked it, and there was no email sent to the two people who I know didn't get it, but have subscribed. They have both gotten emails in the past, when I made the blog post from the /administrator-end. Is that a factor or was that just coincidence? Help!

Hello Susanne,

Hm, just out of curiosity, is the blog post posted as "public" or "private"? If it is private, EasyBlog wouldn't notify subscribers.

It's Public, all of our blogs are public.

Hello Susanne,

I had gone through your Joomla backend and found out that both the username that did not get the email is because they are set as superadmin privilege and subscribed at at the same time instead of registered privilege. According to your settings in Backend > EasyBlog > Settings > Notification > Blog
it is redundant.
Screenshot --> http://screencast.com/t/Y3ui2uzV

Thanks:)

Hi Khairul,

Thanks for the help! Yes that could indeed be the solution, they are both super admins. I am too though, and I got the notification emails. I guess that is because it was me who made the blog post? (even though I set it to be published as from one of the other super admins)

With your new settings in your screenshot, will the super admins get the notifications now?

As for the screenshot, I see "notify all members on new entries" is green. I do not want "all members" to get the notifications, as in "all registered members of the website", if that is what that means? (sorry I can't remember if it was set to red or green before ) We have members that are not subscribers to the blog.

Hello Susanne,

I did not touch your settings in my previous screenshot, you may disable them so that not all members receive the emails. If you have more then one admin to send notification please insert their email in Custom Email Address separated by ",".

screenshot --> http://screencast.com/t/ixifoAucCt

Thanks:)

Was this ever resolved? I am having a very similar problem. It appears that when a superadmin posts, no one receives the notifications. When a regular user posts, everyone receives notifications.

I have tried many different configurations of the above mentioned settings, but to no avail.

The above mention of "redundancy" is also unclear, could you please restate that to explain the actual redundancy? That may be the problem, but what I'm guessing you meant by that is not working. It sounded like you meant the superadmin cannot be assigned as a superadmin AND assigned to a category, since the superadmin automatically implies they are assigned to everything. I tried that, along with the notes about custom emails, but nothing is working. Can you maybe explain exactly what a superadmin should have as settings to make it work right?

Thank you!

Hello Neil,

Can you please start a new thread with your issues and provide us with the back end and FTP access to the site so that we can check on this? I think your issue is different than the issue posted here.