Hi Fabio, I’m testing this functionality also. I think in my case the update to the new time is working, as the most reminders are now scheduled for the next week. But I also have entries from the first week of january.
What I also observed was that the reminder with the default cron job (every minute) was send six times, because the tool uses a 5 minute window (seen it in the source code). I now changed to cron job to run every 6 mins at that is fine now. However, it’s a kind of weird. I think I need more thorough testing here, however I’m short on time at the moment. Regards, Christoph > Am 19.01.2017 um 10:48 schrieb Fabio Onorini (onofa...@gmail.com) > <users@sogo.nu>: > > ... in addition to the previous reporting > I would expect that expired alarms on non-recurring events are deleted from > the table sogo_alarms_folder, but this does not happen. > > 2017-01-19 10:33 GMT+01:00 Fabio Onorini <onofa...@gmail.com > <mailto:onofa...@gmail.com>>: > Hello sogo users, > I have some problems with events alarm. > > After upgrade to version 3.2.5, the system correctly add record in > sogo_alarms_folder table and cron script send mail. > The problem occured on recurring events. The record was not updated with new > alarm_date (next occurence). > > But on bugtracker the issue #1053 (https://sogo.nu/bugs/view.php?id=1053 > <https://sogo.nu/bugs/view.php?id=1053>) was updated to resolved status. > > Have you my same problem? > > -- > > Fabio Onorini > > > > -- > > Fabio Onorini > -- > users@sogo.nu <mailto:users@sogo.nu> > https://inverse.ca/sogo/lists <https://inverse.ca/sogo/lists> -- users@sogo.nu https://inverse.ca/sogo/lists
