korganizer: can't send invitation mails
Hi, with the latest Tumbleweed snapshot and korganizer-22.08.1-1.1.x86_64 it is no longer possible to send invitation mails when using a CalDAV server like SabreDAV (Nextcloud, baikal). When creating an invitation and adding an email address, it is converted to something like CN=<name>;RSVP=TRUE;PARTSTAT=ACCEPTED;ROLE=REQ- PARTICIPANT;CUTYPE=INDIVIDUAL;X-UID=94351025505088:mailto:<mail address> which obviously isn't a valid email address. Therefore no email is sent. On clicking "OK" to save the invitation, Korganizer even shows a dialog box, that it isn't a valid email address and asks to remove this recipient. This makes korganizer nearly unusable for me. Everything works on Android (DavX) and Windows clients (Outlook plugin), so it doesn't seem to be a server problem. I already opened a bug for this (https://bugzilla.suse.com/show_bug.cgi? id=1204362), but perhaps someone here can help with a workaround. TIA. Bye. Michael.
On Dienstag, 18. Oktober 2022 13:19:49 CEST mh@mike.franken.de wrote:
Hi,
with the latest Tumbleweed snapshot and korganizer-22.08.1-1.1.x86_64 it is no longer possible to send invitation mails when using a CalDAV server like SabreDAV (Nextcloud, baikal). When creating an invitation and adding an email address, it is converted to something like CN=<name>;RSVP=TRUE;PARTSTAT=ACCEPTED;ROLE=REQ- PARTICIPANT;CUTYPE=INDIVIDUAL;X-UID=94351025505088:mailto:<mail address> which obviously isn't a valid email address. Therefore no email is sent. On clicking "OK" to save the invitation, Korganizer even shows a dialog box, that it isn't a valid email address and asks to remove this recipient.
This makes korganizer nearly unusable for me. Everything works on Android (DavX) and Windows clients (Outlook plugin), so it doesn't seem to be a server problem.
I already opened a bug for this (https://bugzilla.suse.com/show_bug.cgi? id=1204362), but perhaps someone here can help with a workaround.
it is a bug in libical3: https://bugs.kde.org/show_bug.cgi?id=460592 libical3-3.0.16-99.1.x86_64 solves the problem.
TIA.
Bye. Michael.
participants (1)
-
mh@mike.franken.de