What do you mean by “the categories the user actually selected” ?
That plugin does take category permissions and notification mutes into account already.
So it takes all categories by default, except the ones that are muted, but it ignores if a category is watched/followed or not?
It is like that. Cool. Thanks.
But: Is there any way to include the private messages in the daily summary? If one puts “Send me an email when someone messages me” to “never” in order not to receive other emails, one also doesn’t receive private messages via mail at all 
What you’re saying is that if someone says they don’t want to receive emails for PM’s, they don’t get emails for PM’s. That sounds right. Or do I misunderstand?
1 Like
Thanks for reacting. Actually it’s different: As I also mentioned in https://meta.discourse.org/t/send-me-an-email-when-someone-messages-me/ , there are two settings one can put to “always”, “when away” and “never”:
- “Send me an email when someone messages me” (actually means “… when there is a new post in a category I watch/follow”)
- “Send me an email when someone quotes me, replies to my post, mentions my @username, or invites me to a topic”,
When I enable “daily summary”, I don’t want to get every message about every category I watch/follow via mail in parallel, right? Because that’s the point of a daily digest.
In order to achieve that, I put 1 to “never”. Then I only receive emails, when somebody replies directly to one of my posts, mentions me or invites me to a topic (2).
Now when somebody sends a private message, that one is not covered by 2, so I won’t receive it, until I visit the website. Why would I do that, since I receive all post via daily digest?
When I deactivate “Send me an email when someone messages me” I don’t receive any notifications for any groups anymore. Is there maybe some other setting that interferes here?
Do you mean “any emails” or “any notifications” ? Sorry for the hair-splitting but it makes a big difference. The settings we’re discussing right now determine whether a notification generates an email. They should not interfere with the actual notifications being generated.
I suppose that “someone messages me” also includes group messages.
any emails.
Even if they not directly address you, but you’re just watching/following a category, yes.
Question remains: How does one receive one digest email per day, no separate mail for every topic and some kind of mail for personal messages send directly to himself/herself? 
Again: no. First drop down is for everything we call a “message”, second drop down is for everything that happens in categories/topics.
- Install the MLM Daily Summary plugin.
- Send me an email when someone messages me: only when away
- Send me an email when someone quotes me, replies to my post, mentions my @ username, or invites me to a topic: never
- Watch/track categories:
my/preferences/categoriesand select all categories you want to include in the daily digest
It seems to be, this plug-in isn’t compatible with this theme component: Search banner theme component - #61 by awesomerobot
The problem appears at the 2.9.0.beta1 Discourse version. It’s described in the last posts of the topic. After turning discourse-mlm-daily-summary plug-in off, search banner started working correctly.
2 Likes
I have fixed the issue with the plugin and made a pull request to the original repository.
EDIT which has been merged already 
1 Like
Does this plugin include reply-to addresses for each of the topics included? In our community, we have a number of email-only users who actually do not wish to visit the forum via the Discourse web interface, but they would like to be able to reply to a particular topic if they choose to do so.
Currently, the only way to do this is if they have a notification email to reply from. Presently, I am instructing such users to enable the “Send me first post notifications” on all categories that they might wish to reply to.
However, it would seem cleaner if that functionality existed from within this plugin, without requiring them to receive additional “starting-point” emails they don’t otherwise want. For example, if they wish to modify the notification status for a particular conversation (by replying track, watch, or mute,) can they do so from summary emails generated by this plugin?
It worked. With these settings I receive daily digests and notifications of private messages. I still receive digest entries for every category, that I didn’t explicitly mute, but I guess that’s just a feature, right?
Does this mean the plugin will not work with 2.8? I am still on that version due to the hosting we have (yunohost).
If yes, would the sent daily summary appear here: https://MY_DISCOURSE.COM/admin/email/sent ?
Would it be sent if only new activity is by me?
I am trying to figure out why the plugin does not work on my test instance (daily digests are sent just fine) - any ideas?
If I get it correctly, this is the only settig in settings>e-mails, right:
If your Discourse is at 2.8, on what commit of the plugin are you?
That said, 2.8 has security issues, you should update ASAP. Tell your host to get their sh*t together 
I am on latest git, should I try to downgrade to GitHub - procourse/discourse-mlm-daily-summary at 9135fda73104cffc6a113a985c905425195f08b7 ?
Yes, I hope we get the upgrade soon.
Technically I would pick the commit that was current when 2.8 came out which is ab6ccad.
But :
- it seems like the last three commits there are exactly the same.
- they are client side fixes so I doubt that they are causing the emails not to be sent out.
If I had to guess right now, this might be your issue: No summary emails received · Issue #4 · procourse/discourse-mlm-daily-summary · GitHub
Well, we are on 2.8.13, I guess I was unclear.
I cannot manage to make rake work and while trying to fix it, I completely messed up the ruby installation (I am playing on a test server). The ./launcher enter app is docker specific, right (yunohost does not use docker so I guess we are on our own :-(). If I understand it correctly, these values need to be checked in the console, right?
When 2.8.13 was released, 2.9 was far underway already as well, so if you’re on 2.8.13 you should normally search for plugin code that is compatible with 2.8.0 (since 2.8.13 is 2.8.0 plus bug fixes).