Bug 350959 - Reminder sends mails (with wrong text) even if another reminder type occours - (kontact vers 4.14.10)
Summary: Reminder sends mails (with wrong text) even if another reminder type occours ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: reminder daemon (korgac) (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-04 12:03 UTC by Giuseppe Vinci
Modified: 2018-01-31 17:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Giuseppe Vinci 2015-08-04 12:03:22 UTC
On some appointments I set a mail reminder to confirm my participation in addition to display and audio reminders. For the mail reminder I set mail address, message text and when the it should be sent.
Regrettably Kontact does anything a bit different as planned.
a) Instead of the configured message it sent a remind note to.
b) This remind note is sent every time an other reminder is falling due. Example, an audio reminder is set 2 hours before event start - so at the same time (2 h before) with this a remind note will be sent. Embarrassing in face of customers and suppliers.

Reproducible: Always

Steps to Reproduce:
1. Configure a future appointment with some reminders. One of them must be a "Send email" reminder type.
2. For this one choose when, the email of the partner (it can also be your own) and edit a message (i.e.: I'm appreciate to participate on the next briefing) 
3. Wait for the set reminders and you will note what happens wrong.

Actual Results:  
A email reminder (not the message edited) is sent and that also when other kind of reminders falling due

Expected Results:  
1. The email sent contains the edited message (not a reminder note)
2. The email should be sent only for the "Send email" reminder (not also for other reminders)
Comment 1 Denis Kurz 2017-06-23 19:57:56 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 17:13:39 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.