Notifications just are not sent

Strange - suddenly I got one! Did someone magically fix it because of my request? ;)

I ran into this one as well. Particularly vexing was the fact that emails would send as expected from the stage environment, but not from the live environment. After many hours of troubleshooting, I performed a diff of values in the variables table between the two environments. On live, a variable called "notifications_content_per_type" had not been set. I navigated to /admin/messaging/notifications/content, clicked save without changing any values, and emails on live began working as expected.

I'm having the same problem. I have tried navigating to /admin/messaging/notifications/content and saving, but it did not resolve the issue for me.

Nothing ever gets added to notifications_queue. Immediately after adding new content that should trigger a notification, here is what I see:

mysql> select * from notifications_queue;
Empty set (0.00 sec)

Subscribing. See: http://drupal.org/node/466920

either notifications or notifications_extras is buggy.

I installed both modules on 2 nearly identical sites (a multisite running on same code base). First neither one worked. Then "magically" one site started working. But carefully matching the settings from the working site to the non-working site failed to get custom subscriptions working on the second site. Then about a day later, the second site started working (i.e., sending emails for custom subscriptions).

I documented every single step I took over 2 days of debugging, including the contents of various database tables every time I made a change to either site. I am sure that the problem was not due to a wrong settings. Furthermore, I am sure that the solution was not because of anything I changed.

The only thing I can see that happened is that the watcher module sent some notices and then the notifications module seemed to start working part way. Then I dropped all subscribers and added them back and saved settings (no real changes were made) and "magically" the second site started working.

I smell a challenging bug here...

If I can help (based on my good documentation of my problem) please let me know.

If it helps, in my own case the notif's go out to my email addresses if the addresses are not in the site domain. I've only tested this on two or three email addresses, so maybe it's a fluke, but I was getting no notifies on myemail@mydomain.com but I do get them at myotheremail@gmail.com.
(Hurrah for gmail?)

And so far, most of my users are not reporting problems... just me as developer. This might also fit the "not the site domain" theory since just about none of the users have an email address that is @mydomain.

A colleague and I are able to verify that we do not receive notifications as admins, but that other users (who are in our same e-mail domain) are still receiving notifications. Could this be a permissions issue?

Don't know what sort of monkey wrench this throws in but... we have a vbulletin forum going at the same domain and I found that system email from vB wouldn't go to my email address at the domain either, but would go to gmail.
So maybe what we're really looking at here is a (not uncommon) server config. issue?
Or maybe it doesn't mean a thing.

In my case, this turned out to be a server config problem. Had something to do w/the fact that we were using Google Apps for email rather than the server email stuff and things were not configured properly.
Once that was corrected, started getting notifications just fine at the domain email address (in fact, now I'm getting two or three for every post, but that's another issue)

I too have this issue, not working for gmail or any address. Messages are in profile but no email sent when new content is created/published, have tried all send methods to no avail.

In my case, notifications are being sent for comments, thread subscriptions and broadcasts, but not for node creation or updates in groups, even though all events are checked on admin/messaging/notifications/events page.

Have spent hours since the problem occurred quadruple-checking that all the other various option chains are as correct as I can, but to no avail. All I can think of is that it may have broken somewhere when I was crawling around configuring available subscription options, and creating mime_mail templates.

Using latest releases of core, messaging, notifications, og_notifications, og, mime_mail, etc. (all is green on Available Updates).

aharown,

My server is also set to use google apps instead of the regular server mail. I was wondering how you'd fixed your issue with Notifications?

The sever people said they had to set my domain to "remote"... I'm not sure what that means. They knew what to do right away though when I told them the emails would go out to to non-domain addresses but not to @mydomain.com addresses.
That's about all I know besides
a. this "remote" setting is not a setting in the mx tables
b. I asked how I could do this myself and they said root access was required (which I didn't have at the time... if I had--as I do now--I still wouldn't know what to do with it)

I don't have this issue now after trying Mail method, sends to any email. One thing I noticed was that after changing default send method the Users default send method was unchanged and so was the send methods for individual subscriptions, I changed them to Mail and works. Good luck!

Subscribing...

Some test results (follow-up to my last post #11):

- Using standard Drupal "Mail" send method, all notifications are sent out OK
- Using MimeMail send method, node create and node update notifications are NOT sent
- However, comment notifications are sent out OK via MimeMail send method
- with Messaging Debug active, all messages appear in the dblog, including MimeMail node create and update events

This tells me that something may be failing in the mimemail module, the mimemail hooks in the notifications API, or possibly the OG notifications module, or something of that nature. (The various possible relationships between these modules seem quite complex.)

Or maybe there's a problem with the MimeMail message templates for OG notifications, which I was working on around the time the problem started. Something there (such as a token) may be causing MimeMail to choke silently, but wouldn't that cause the messages to fail to appear in the debug dblog as well?

My message templates for all node events and comments were pasted in from the same source, with only minor changes to the text and tokens to indicate node events, groups, content types etc.

Any other parameters to test? Any related MimeMail issues that may be relevant? I've run out of ideas.

Not working here too. I had seen an error message "sendmail was not found on the server". Maybe that's the problem. So i try PHPMail Messaging and that works.

If i activate the module "Notifications Add-ons" standard "Drupal Mail" is not avaiable in the drop down menu in Custom subscriptions for some reason.

Messaging 6.x-2.1
Notifications 6.x-2.1
Notifications Add-ons 6.x-2.0-beta2
Drupal 6.14

Sounds like you might want to open a separate issue on the specific problem of "drupal mail not avail. in drop down"
But if you got "sendmail not found on the server" you may want to talk to your host admin & find out what that's about.

Nothing is sent, at all, with no error messages.

I think half the people here should check the 'Notify poster of own posts' http://drupal.org/node/252700

For the rest, if having issues with a specific sending method only (mimemail), fill an issue for Messaging module.

Anyone left?

Automatically closed -- issue fixed for 2 weeks with no activity.