The approach that I used is complicated in part because I am sending email for over 350 fossils spread out over 12 different areas with as many as 500 users registered in some of those fossils (although only a very few of whom actually access them). So efficiency is crucial for my situation. I'll summarize what I did and anyone thinks the scripts might be of use to them let me know and I'll make sanitized versions available somewhere.
My approach: 1. Install rss2email from http://www.allthingsrss.com/rss2email/ (this part is easy) 2. Use a wiki page in each fossil (I use "emailnotification") for storing the list of email addresses to send notifications to. Users can update this as desired. 3. Write a script that gets the email addresses and runs rss2email for each. 4. Call the send script on every change to the fossil. A good triggers mechanism would make this much easier but I haven't looked at the current triggers mechanism to see what it can/can not do. On Fri, Feb 21, 2014 at 8:58 AM, Stephen Cripps <9...@queensu.ca> wrote: > Would it be possible to have fossil check for a an available smtp > binary, something like sendmail/msmtp or the like and hand the message > off to to that program for delivery? You could have an option under the > admin menu to select which program to use, and the smtp user auth > specific to the server. > > Stephen C. > > On 21/02/14 10:40 AM, j. van den hoff wrote: > > I've noted there were some related threads recently, but I've not got > > a really clear picture what the best approach would be. we also are > > hit by this problem: a central repo used by some 10 people max. for > > creating tickets and following changes to those through the web gui > > w/o using fossil themselves locally. > > > > it has turned out that the system works just fine _except_ that I get > > many requests for automated email notification since of course > > everybody is too busy to actively check the repo (well, that's how it > > is ...). so the endeavor is in danger of dying a slow death... > > > > question: given that the repo runs on a linux machine, could I please > > get some advice what would be the easiest way (if at all) to implement > > automated email notification of changes to the repo (and considering > > that the repo is served via cgi and https, i.e. content is private and > > password protected on a per user base). I mean without jumping through > > too many loops, if possible. > > > > thanks in advance > > joerg > > > > ps: I also failed to get rss notification running since I have not > > found any rss reader (execept the one integrated in opera 12.x > > browser/mail client) who manages private (password protected/https) > > feeds. is there such a thing (ideally for all platforms)? > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority...
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
