[kmail2] [Bug 324229] Bug in the Emaileditor. The %CURSOR did not work in the template to send a new mail
https://bugs.kde.org/show_bug.cgi?id=324229 Tilman Klaeger k...@tilman-klaeger.de changed: What|Removed |Added CC||k...@tilman-klaeger.de --- Comment #8 from Tilman Klaeger k...@tilman-klaeger.de --- I have got a similiar bug in KDE 4.12.0. I can use %CURSOR in the template without any problems, but adding %SIGNATURE breaks everything and only the signature is shown, without the text I put above or below. Don´t know if this is a different bug or is caused by the same piece of code. With KDE 4.11 the templates with signature worked very well! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 309481] CalDAV only syncs on restart
https://bugs.kde.org/show_bug.cgi?id=309481 Tilman Klaeger k...@tilman-klaeger.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Tilman Klaeger k...@tilman-klaeger.de --- Seems to be working now with KDE 4.9.3, I can see the REPORT statements every now and then in the log files and not only on restarts. Before only PROFIND appeared in the logs, which seems not be enough. Thanks a lot for your efforts! -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 309481] CalDAV only syncs on restart
https://bugs.kde.org/show_bug.cgi?id=309481 --- Comment #2 from Tilman Klaeger k...@tilman-klaeger.de --- I´m using KDE 4.9.2 and Owncloud 4.5.1a, both latest stable. The server logs look like the following, I get the 401, but followed by a 207. Nevertheless my calendar loaded nicely, but as said only on restart of the GroupDAV Agent or Akonadi restart. - [04/Nov/2012:12:59:36 +0100] PROPFIND /remote.php/caldav/ HTTP/1.1 401 4187 - Mozilla/5.0 (X11; Linux 3.6.5-1-ARCH) AppleWebKit/534.34 (KHTML, like Gecko) akonadi_davgroupware_resource_7/4.9.2 Safari/534.34 tilman [04/Nov/2012:12:59:37 +0100] PROPFIND /remote.php/caldav/ HTTP/1.1 207 4587 - Mozilla/5.0 (X11; Linux 3.6.5-1-ARCH) AppleWebKit/534.34 (KHTML, like Gecko) akonadi_davgroupware_resource_7/4.9.2 Safari/534.34 - [04/Nov/2012:12:59:38 +0100] PROPFIND /remote.php/caldav/principals/tilman/ HTTP/1.1 401 4187 - Mozilla/5.0 (X11; Linux 3.6.5-1-ARCH) AppleWebKit/534.34 (KHTML, like Gecko) akonadi_davgroupware_resource_7/4.9.2 Safari/534.34 tilman [04/Nov/2012:12:59:39 +0100] PROPFIND /remote.php/caldav/principals/tilman/ HTTP/1.1 207 4459 - Mozilla/5.0 (X11; Linux 3.6.5-1-ARCH) AppleWebKit/534.34 (KHTML, like Gecko) akonadi_davgroupware_resource_7/4.9.2 Safari/534.34 - [04/Nov/2012:12:59:39 +0100] PROPFIND /remote.php/caldav/calendars/tilman/ HTTP/1.1 401 4187 - Mozilla/5.0 (X11; Linux 3.6.5-1-ARCH) AppleWebKit/534.34 (KHTML, like Gecko) akonadi_davgroupware_resource_7/4.9.2 Safari/534.34 tilman [04/Nov/2012:12:59:40 +0100] PROPFIND /remote.php/caldav/calendars/tilman/ HTTP/1.1 207 8507 - Mozilla/5.0 (X11; Linux 3.6.5-1-ARCH) AppleWebKit/534.34 (KHTML, like Gecko) akonadi_davgroupware_resource_7/4.9.2 Safari/534.34 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 309481] New: CalDAV only syncs on restart
https://bugs.kde.org/show_bug.cgi?id=309481 Bug ID: 309481 Severity: normal Version: 4.9 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: CalDAV only syncs on restart Classification: Unclassified OS: Linux Reporter: k...@tilman-klaeger.de Hardware: Archlinux Packages Status: UNCONFIRMED Component: DAV Resource Product: Akonadi I use a GroupDAV Resource to sync Kontact / Akonadi with my ownCloud. After adding an event in ownCloud it does not show up in Kontact when refreshing the calendar. I see that a connect in the webserver access logs, but the new event is not transfered and so not also not shown in Kontact. Restarting Akonadi or (in Akonadi Console) restarting the GroupDAV Resource helps and the event is shown. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 218654] Kontact crashes when switching to Knode
https://bugs.kde.org/show_bug.cgi?id=218654 Tilman Klaeger k...@tilman-klaeger.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 218654] New: Kontact crashes when switching to Knode
https://bugs.kde.org/show_bug.cgi?id=218654 Summary: Kontact crashes when switching to Knode Product: kontact Version: 4.3 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@tilman-klaeger.de Version:(using Devel) Compiler: gcc-Version 4.4.2 20091208 OS:Linux Installed from:Compiled sources I enabled the Knode module in Kontact. And now everytime I click on the Knode button, Kontact crashes. All other modules in Kontact work, and starting Knode standalone also does not give me any trouble. Also tried this with a completly fresh useraccount, same thing. Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb60cc80a in strcmp () from /lib/libc.so.6 #7 0xb6e6c6dd in ?? () from /usr/lib/libQtCore.so.4 #8 0xb6e75e2b in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib/libQtCore.so.4 #9 0xb6033c4b in KParts::Part::setWidget (this=0x9f907b8, widget=0xa02cd58) at /home/tilman/temp/build/build-i686/kdelibs/src/kdelibs/kparts/part.cpp:287 #10 0xad76b0da in KNodePart (this=0x9f907b8, parentWidget=0x89e45c0, parent=0x89e45c0, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /home/tilman/temp/build/build-i686/kdepim/src/kdepim/knode/knode_part.cpp:71 #11 0xad76b6dd in KPluginFactory::createPartInstanceKNodePart (parentWidget=0x89e45c0, parent=0x89e45c0, args=...) at /usr/include/kpluginfactory.h:467 #12 0xb7172989 in KPluginFactory::create (this=0x8a09b98, iface=0xb60514e0 KParts::ReadOnlyPart, parentWidget=0x89e45c0, parent=0x89e45c0, args=..., keyword=...) at /home/tilman/temp/build/build-i686/kdelibs/src/kdelibs/kdecore/util/kpluginfactory.cpp:191 #13 0xb770d3a9 in KPluginFactory::createKParts::ReadOnlyPart (this=0x89e45c0, libname=0x89f91c8 knodepart) at /usr/include/kpluginfactory.h:491 #14 KontactInterface::Core::createPart (this=0x89e45c0, libname=0x89f91c8 knodepart) at /home/tilman/temp/build/build-i686/kdepimlibs/src/kdepimlibs/kontactinterface/core.cpp:87 #15 0xb770e53c in KontactInterface::Plugin::loadPart (this=0x8affe88) at /home/tilman/temp/build/build-i686/kdepimlibs/src/kdepimlibs/kontactinterface/plugin.cpp:152 #16 0xb07852ba in KNodePlugin::createPart (this=0x8affe88) at /home/tilman/temp/build/build-i686/kdepim/src/kdepim/kontact/plugins/knode/knode_plugin.cpp:100 #17 0xb770f809 in KontactInterface::Plugin::part (this=0x8affe88) at /home/tilman/temp/build/build-i686/kdepimlibs/src/kdepimlibs/kontactinterface/plugin.cpp:191 #18 0xb78963b4 in Kontact::MainWindow::selectPlugin (this=0x89e45c0, plugin=0x8affe88) at /home/tilman/temp/build/build-i686/kdepim/src/kdepim/kontact/src/mainwindow.cpp:778 #19 0xb789aa17 in Kontact::MainWindow::qt_metacall (this=0x89e45c0, _c=QMetaObject::InvokeMetaMethod, _id=53, _a=0xbfe7b218) at /home/tilman/temp/build/build-i686/kdepim/src/build/kontact/src/mainwindow.moc:113 #20 0xb6e681da in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #21 0xb6e76cf7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #22 0xb789c0c6 in Kontact::SidePaneBase::pluginSelected (this=0x89c3490, _t1=0x8affe88) at /home/tilman/temp/build/build-i686/kdepim/src/build/kontact/src/sidepanebase.moc:90 #23 0xb789c129 in Kontact::SidePaneBase::qt_metacall (this=0x89c3490, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0xbfe7b388) at /home/tilman/temp/build/build-i686/kdepim/src/build/kontact/src/sidepanebase.moc:77 #24 0xb789c377 in Kontact::IconSidePane::qt_metacall (this=0x89c3490, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0xbfe7b388) at /home/tilman/temp/build/build-i686/kdepim/src/build/kontact/src/iconsidepane.moc:145 #25 0xb6e681da in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #26 0xb6e76cf7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #27 0xb789c434 in Kontact::Navigator::pluginActivated (this=0x88b1020, _t1=0x8affe88) at /home/tilman/temp/build/build-i686/kdepim/src/build/kontact/src/iconsidepane.moc:96 #28 0xb789c4b1 in Kontact::Navigator::slotCurrentChanged (this=0x88b1020, current=...) at /home/tilman/temp/build/build-i686/kdepim/src/kdepim/kontact/src/iconsidepane.cpp:475 #29 0xb789ccd5 in Kontact::Navigator::qt_metacall (this=0x88b1020, _c=QMetaObject::InvokeMetaMethod, _id=71, _a=0xbfe7b4f4) at /home/tilman/temp/build/build-i686/kdepim/src/build/kontact/src/iconsidepane.moc:82 #30 0xb6e681da in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #31 0xb6e76cf7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from
[Bug 204712] New: Mark DKIM signed messages
https://bugs.kde.org/show_bug.cgi?id=204712 Summary: Mark DKIM signed messages Product: kmail Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: k...@tilman-klaeger.de Version:(using KDE 4.3.0) OS:Linux Installed from:Unlisted Binary Package With DKIM the sending mailserver adds a signature to the email headers, similiar to a GPG signature. The receiving mailserver then validates the signature with a public key published in the DNS record of the sending domain, on success, a header is added to the email. It would be cool, if KMail could mark messages, that passed DKIM similiar to the way GPG-Messages are marked! dkim-milter produces following header: Authentication-Results: mx.rcpt.domain; dkim=pass (1024-bit key) header...@sender.domain; dkim-asp=none Google uses the following header (first SPF, then DKIM): Authentication-Results: mx.google.com; spf=pass (google.com: domain of sen...@sending.domain designates xxx.xxx.xxx.xxx as permitted sender) smtp.mail=sen...@sending.domain; dkim=pass header...@sending.domain KMail could also do the signing and verification on its own, but imho this is the job of the mta, not the mua. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
