Open oparoz opened 13 years ago
ari
commented
13 years ago I don't quite see the point. They should do one of two things:
What would be in the daily email? How would you reply to it? How would it be formatted?
This is a little bit of work since we'd have to keep another flag to record what was sent out in the last email.
oparoz
commented
13 years ago If you filter them out, then you don't have access to the information on the go. It's not convenient to use the system from a phone.
The daily email would only contain a list of changes for that day (new, modified, deleted tasks). It could contain simply the clickable titles or also include the summary for each task. You would not reply to it. No flag would need to be maintained, it would purely be informational.
My example above was wrong, the PM will need to get every email, but a stakeholder not necessarily.
It's just something that got suggested to me. Some people want to keep an eye on things without being snowed under or to have to configure thins specifically for a project they're involved with.
ari
commented
13 years ago Is it a list of all the changes, or a list of tasks assigned to that user? Perhaps you could write up a short section of how you see such an email formatted
oparoz
commented
13 years ago Just like a mailing list daily digest
List of topics at the top and all the messages underneath.
I can't find a copy of one right now, but I'm sure you know what they look like :)
ari
commented
13 years ago No I don't know, sorry. Two messages ago you said "It could contain simply the clickable titles or also include the summary for each task." That is a completely different technical problem than "all the messages underneath." The latter requires a flag per user, per message so that we know who has received the digest version. Using a date range (everything before midnight) is prone to lots of problems (timezones, clock drift, cron failure and restart).
oparoz
commented
13 years ago Please find below an example of what I mean. The way I see it, the first version could be just like this example. Instead of sending emails one by one, you queue them and send one email containing everything that is in the queue.
The queue could be full when:
There wouldn't need to introduce any special flags since messages would just be queued. No need for links either since they would already be there, at the end of every message.
I haven't looked at the code, so I apologize if this sounds like a difficult thing to do with the current classes. I just thought that since you already had a queuing system and knew who was getting which message, it was a simple matter of building a timed aggregation that could be useful to some.
Today's Topics:
Message: 1 Date: Fri, 14 Jan 2011 08:15:18 -0200 From: Andre Nathan andre@digirati.com.br Subject: Re: [Dovecot] Best Cluster Storage To: Jonathan Tripathy jonnyt@abpni.co.uk Cc: dovecot@dovecot.org Message-ID: 1295000118.5180.6.camel@andre.mz.digirati.com.br Content-Type: text/plain; charset="UTF-8"
On Fri, 2011-01-14 at 03:48 +0000, Jonathan Tripathy wrote:
ocfs2 seems to work quite well with lots of small files (typical of maildir). I'm guessing that since ocfs2 reboot a system automatically, it doesn't require any additional fencing? We have a two-node active-active DRBD+OCFS2 Dovecot cluster. We're currently unable to fully use it due to (what I believe is) an OCFS2 bug:
http://oss.oracle.com/bugzilla/show_bug.cgi?id=1297
so while DRBD is in a dual-primary setup and the dovecot volumes are mounted read/write on both cluster nodes, I had to remove one of them from the load balancer, and thus only one of them handles connections while the other is sitting there as a failover node.
HTH, Andre
Message: 2 Date: Thu, 13 Jan 2011 21:59:44 +0000 (UTC) From: Paul Provost paul-dovecot@bouzou.org Subject: [Dovecot] Virtual mailboxes do not look into subfolders To: dovecot@dovecot.org Message-ID: loom.20110113T225501-275@post.gmane.org Content-Type: text/plain; charset=us-ascii
Hi all,
I have virtual mailboxes set up as "Smart Folders" to show me messages
tagged with certain keywords. For example:File MailingLists/* KEYWORD @fwp
Messages get picked up from the File mailbox, but not for the sub-mailboxes inside the MailingLists mailbox. What am I doing wrong? Wrong separator?
And how can I debug this? Everything else is working fine.
Thanks a lot!
Paul
etc. etc.
ari
commented
13 years ago Ah, got it! Basically you are saying "delay sending of queued messages to certain users until a particular time of day, then send them as a digest." Yes, technically that isn't hard to do at all.
So this isn't a summary of everything that changed in the last 24 hours, just a digest of messages they would have received anyway.
Personally I still can't see the point compared to creating another mailbox and having the mail sorted into that automatically, but it isn't that hard to do.
oparoz
commented
13 years ago Yes, a digest of messages. 1 vibration instead of 40 during the day. Less stress ;)
If you're on a corporate network, you only get that one mailbox and you get everything that reaches the inbox.
I, personally, find digests much more manageable when I subscribe to a mailing list. I can keep an eye on things and get involved when I need to.
For a company owner or a PM, it could be useful to get a daily email listing all the changes. I know some people with instant email will filter out the messages because otherwise they keep getting disturbed.
Thoughts?