On Tue, 16 Dec 2014, at 09:09 AM, Patrick Goetz wrote:
I hope I got that right. The SMS/XMPP thing could be useful if it weredocumented. I'm not sure I'm seeing the utility of the sievenotifiersetting (send an email to let you know an email has been sent?).
Its useful if you want to notify another address that a message arrived. FastMail's notifyd allows extra options like summarising the email. Imagine sending it through to bridging service like IFTTT.
But yes, the SMS and IM options are far more useful.
I still have no idea how the Fastmail notifyd
This part is the same, just with more options. The various notify options we have are documented here:
works or how this is integrated with calendar functionality.
Calendar notifications are generated through mboxevents, which still arrive via the notifyd channel but with a slightly different format. The event has all the information about the calendar item in it, and we use that to create an email or generate an eventsource push to the web client.
For the alarms themselves, we keep a global database of the "next" alarm for each item, which gets updated when a calendar item is saved. There's a separate daemon (calalarmd) which periodically processes this database and sends the mboxevents.
mboxevents are in Cyrus master (unsure about 2.4, I've never actually looked at it) and of course calendar support is there. The alarm support is (currently) specific to the FastMail branch. And yes, this is all woefully undocumented.
I am being a little vague about all of this because I'm not quite sure if you're just curious or seriously looking to hack on or deploy this. If you ask specific questions we'll try to help out :)
Cheers,
Rob N.
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
