Bug 307464 - KOrganizer automatically sends mail on changes on events where the user is not the organizer.
Summary: KOrganizer automatically sends mail on changes on events where the user is no...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: invitations (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-26 22:15 UTC by dev
Modified: 2017-01-07 22:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dev 2012-09-26 22:15:01 UTC
I've added an event to the calender which i've recived via an E-Mail in KMail. I'm not the organizer of this event. It has the E-Mail address of an mailing list as participant.

When i tried to remove the reminder settings in this event, KOrganizer asked me if i really want to do this as the event will get out of sync with the organizer. I clicked yes and KOrganizer automatically send an E-Mail to the mailing list with the "From:" address the address of the original organizer. It didn't ask for any confirmation. I consider this a serious bug.

One solution to this problem would be to ask the user for conformation on any E-Mail that KOrganizer intends to send. Another one would be to send a the changes just to the original organizer as an suggestion or something. But even in this case some mail window should pop up so that the user can enter some sentences why he suggests this changes.
Comment 1 Denis Kurz 2016-09-24 18:46:12 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:01:32 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.