Bug 118164 - group invitations sent to mailing lists are not detected
Summary: group invitations sent to mailing lists are not detected
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-12 09:36 UTC by Janne Karhunen
Modified: 2017-01-07 21:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Janne Karhunen 2005-12-12 09:36:05 UTC 
Version:           kdepim3-3.5.0-7 (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs
Compiler:          gcc-4.0.2_20050901-3 SUSE 10
OS:                Linux

Just received a meeting invitation sent to whole unit via mailing list. While pressing 'accept' korganizer asks that my
identity does not match any receiver of this message, and lets me to pick up identity from 2 mailing list addresses this
invitation was sent to. Upon selecting one, it sends out message with mailing list as a From: header! Please make an option
NOT TO send acknowledgement in such case. I just need this entry to my calendar..
Comment 1 Reinhold Kainhofer 2006-11-02 19:15:43 UTC 
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 2 Janne Karhunen 2007-01-17 11:16:53 UTC 
Still present in KDE 3.5.5 (SUSE 10.2).
Comment 3 Denis Kurz 2016-09-24 18:44:02 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 4 Denis Kurz 2017-01-07 21:45:19 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.