[kmail2] [Bug 325596] gpg does not work
https://bugs.kde.org/show_bug.cgi?id=325596 --- Comment #4 from Daniel Moyne --- Sandro, have you found anything wrong? For the time being I am working without storing passphrases in KwalletManager. -- 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
[kaddressbook] [Bug 327255] Unable to add contact. Address book DOES exist.
https://bugs.kde.org/show_bug.cgi?id=327255 --- Comment #5 from andy_90...@yahoo.com --- I agree with Wolfgang. Experienced users can easily disable things they don't want. New users have no idea what's wrong and generally assume it's broken - someone like me with some Linux experience and/or programming experience may go so far as to report it as a bug. A transplant from the Windoze universe will assume it's broken and simply move on - either to an alternative application if available - or just return to Windoze left with a bad taste in their mouth and it's doubtful they'll return. Applications should do what the user expects - it should be ready for use right out of the box. If a user has to tweak it to use it the first time, chances are they're going to walk away from it - this goes for any and all applications. Tweaking should be left for someone that has had a chance to explore the application and get some use out of it. You don't get a second chance to make a first impression. Just my opinion. On Saturday, November 9, 2013 3:31 AM, Wolfgang Bauer wrote: https://bugs.kde.org/show_bug.cgi?id=327255 Wolfgang Bauer changed: What |Removed |Added CC| |wba...@tmo.at --- Comment #4 from Wolfgang Bauer --- (In reply to comment #3) > So in summary each new addressbook is disable by default that's it ? > and you want that we enable it ? I'm not the original reporter, but that's exactly what I think should be done. Please note that also the default addressbook (created by Akonadi FirstRun) has to be enabled before being able to store any contact, which can be _very_ confusing for a new user IMHO. And the same also applies to the calendars (in KOrganizer), it's not restricted to the addressbooks. -- 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
[kontact] [Bug 288141] Kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=288141 Jekyll Wu changed: What|Removed |Added CC||k...@kaishome.de --- Comment #25 from Jekyll Wu --- *** Bug 327428 has been marked as a duplicate of this bug. *** -- 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
[kontact] [Bug 327428] kontact crashed long after closing window
https://bugs.kde.org/show_bug.cgi?id=327428 Jekyll Wu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu --- *** This bug has been marked as a duplicate of bug 288141 *** -- 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
[kmail2] [Bug 327430] New: Speed up "multiple to address" insert
https://bugs.kde.org/show_bug.cgi?id=327430
Bug ID: 327430
Summary: Speed up "multiple to address" insert
Classification: Unclassified
Product: kmail2
Version: 4.11.3
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: composer
Assignee: kdepim-bugs@kde.org
Reporter: virgo...@gmail.com
Every time I enter an address in "to" field, the cursor switch to the next
field ("cc"). I think is better have the possibility to enter multiple to,
using the comma as separator, without losing focus in the "to" field
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
[kontact] [Bug 327428] New: kontact crashed long after closing window
https://bugs.kde.org/show_bug.cgi?id=327428 Bug ID: 327428 Summary: kontact crashed long after closing window Classification: Unclassified Product: kontact Version: 4.11.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@kaishome.de Application: kontact (4.11.3) KDE Platform Version: 4.11.3 Qt Version: 4.8.5 Operating System: Linux 3.11.7-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I closed Kontact serveral minutes before and later it crashed -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f434969a780 (LWP 13543))] Thread 3 (Thread 0x7f434535c700 (LWP 13544)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x00383df5521d in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x00383df55329 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x003b17208ec6 in start_thread (arg=0x7f434535c700) at pthread_create.c:305 #4 0x003b16aea6ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f4344a43700 (LWP 13545)): #0 0x003b16adcfad in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x003ece283c4f in read (__nbytes=16, __buf=0x7f4344a42c20, __fd=) at /usr/include/bits/unistd.h:45 #2 g_wakeup_acknowledge (wakeup=0x1bb41c0) at gwakeup.c:212 #3 0x003ece248be4 in g_main_context_check (context=context@entry=0x7f4349a0, max_priority=2147483647, fds=fds@entry=0x7f43400029c0, n_fds=n_fds@entry=1) at gmain.c:3129 #4 0x003ece248ff2 in g_main_context_iterate (context=context@entry=0x7f4349a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3287 #5 0x003ece249174 in g_main_context_iteration (context=0x7f4349a0, may_block=1) at gmain.c:3351 #6 0x0038381abbc6 in QEventDispatcherGlib::processEvents (this=0x7f4348c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #7 0x00383817c52f in QEventLoop::processEvents (this=this@entry=0x7f4344a42e00, flags=...) at kernel/qeventloop.cpp:149 #8 0x00383817c7b8 in QEventLoop::exec (this=0x7f4344a42e00, flags=...) at kernel/qeventloop.cpp:204 #9 0x00383807f2a0 in QThread::exec (this=) at thread/qthread.cpp:536 #10 0x003838081a1c in QThreadPrivate::start (arg=0x1df6a80) at thread/qthread_unix.cpp:338 #11 0x003b17208ec6 in start_thread (arg=0x7f4344a43700) at pthread_create.c:305 #12 0x003b16aea6ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f434969a780 (LWP 13543)): [KCrash Handler] #6 operator QItemSelectionModel* (this=) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:78 #7 QAbstractItemView::selectionModel (this=0x3e0001) at itemviews/qabstractitemview.cpp:766 #8 0x7f42fc3381a6 in MailCommon::FolderTreeWidget::selectedCollections (this=) at /var/tmp/portage/kde-base/kmail-4.11.3/work/kmail-4.11.3/mailcommon/folder/foldertreewidget.cpp:244 #9 0x7f42fc70ebc4 in KMMainWidget::updateFolderMenu (this=0x2611150) at /var/tmp/portage/kde-base/kmail-4.11.3/work/kmail-4.11.3/kmail/kmmainwidget.cpp:4137 #10 0x7f42fc71ba3a in KMMainWidget::slotUpdateActionsAfterMailChecking (this=) at /var/tmp/portage/kde-base/kmail-4.11.3/work/kmail-4.11.3/kmail/kmmainwidget.cpp:426 #11 0x7f42fc72040d in KMMainWidget::qt_static_metacall (_o=, _c=, _id=, _a=) at /var/tmp/portage/kde-base/kmail-4.11.3/work/kmail-4.11.3_build/kmail/kmmainwidget.moc:512 #12 0x003838192f74 in QMetaObject::activate (sender=0x26113a8, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3547 #13 0x003838196edc in QObject::event (this=0x26113a8, e=) at kernel/qobject.cpp:1156 #14 0x003838bde16c in QApplicationPrivate::notify_helper (this=this@entry=0x1bb2bf0, receiver=receiver@entry=0x26113a8, e=e@entry=0x7fff92359420) at kernel/qapplication.cpp:4562 #15 0x003838be0af2 in QApplication::notify (this=0x7fff9235a660, receiver=0x26113a8, e=0x7fff92359420) at kernel/qapplication.cpp:4423 #16 0x7f434dce27e6 in KApplication::notify (this=0x7fff9235a660, receiver=0x26113a8, event=0x7fff92359420) at /var/tmp/portage/kde-base/kdelibs-4.11.3/work/kdelibs-4.11.3/kdeui/kernel/kapplication.cpp:311 #17 0x00383817d87e in QCoreApplication::notifyInternal (this=0x7fff9235a660, receiver=0x26113a8, event=0x7fff92359420) at kernel/qcoreapplication.cpp:949 #18 0x0038381ae742 in sendEvent (event=0x7fff92359420, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #19 QTimerInfoList::ac
[kmail2] [Bug 325043] Kmail takes several minutes (and more) to open a message
https://bugs.kde.org/show_bug.cgi?id=325043 Eckhart Wörner changed: What|Removed |Added CC||ewoer...@kde.org -- 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
[kmail2] [Bug 327416] Subject isn't correctly shown in messageviewer cause to encoding
https://bugs.kde.org/show_bug.cgi?id=327416 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Will investigate it soon. -- 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
[kmail2] [Bug 314930] When Kmail finds encryption keys to use and I select, "Encrypt" it fails to encrypt the message with my key
https://bugs.kde.org/show_bug.cgi?id=314930 Nicolas VINOT changed: What|Removed |Added CC||ae...@imirhil.fr --- Comment #8 from Nicolas VINOT --- This bug is more serious than you think. After the warning because you have not select a key to encrypt for yourself, if you click on « Encrypt », the message is stored unencryted into KMail folder, but it is also send unencrypted ! Confirm with my recipient, the mail is not received encrypted. This is a serious security issue because you send clear email when you think you send cyphered email. The only way to really encrypt the email is to check « Encrypt Message » on the compose window. All other automatic ways send clear message even KMail seems saying the opposite to you. (Test on KDE PIM 4.11.2) -- 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
[Akonadi] [Bug 327421] New: akonaditray dont uses his plasma themes svg icon anymore
https://bugs.kde.org/show_bug.cgi?id=327421 Bug ID: 327421 Summary: akonaditray dont uses his plasma themes svg icon anymore Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: plusf...@gmail.com unter 4.11 akonaditray dont uses his plasma themes icon anymore. if the plasma theme supports the akonadiicon in the svg icon theme akonaditray should load it as it was in the last releases Reproducible: Always Steps to Reproduce: 1. install a plasma theme with akonadi icon 2. anyble the theme Actual Results: akonaditray still uses his normal blue icon Expected Results: akonaditray should use the themes icon again -- 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
[kaddressbook] [Bug 327315] KAddressbook should group contacts with same displayed name in list of contacts
https://bugs.kde.org/show_bug.cgi?id=327315 Arthur Țițeică changed: What|Removed |Added CC||arthur.tite...@gmail.com -- 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
[kmail2] [Bug 327416] Subject isn't correctly shown in messageviewer cause to encoding
https://bugs.kde.org/show_bug.cgi?id=327416 Arthur Țițeică changed: What|Removed |Added CC||arthur.tite...@gmail.com -- 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
[kmail2] [Bug 327416] New: Subject isn't corretly shown in messageviewer cause to encoding
https://bugs.kde.org/show_bug.cgi?id=327416 Bug ID: 327416 Summary: Subject isn't corretly shown in messageviewer cause to encoding Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@sandroknauss.de Created attachment 83477 --> https://bugs.kde.org/attachment.cgi?id=83477&action=edit Mail with a sebuject, that isn't displayed correctly everytime. I got a mail with a subject: =?iso-8859-1?q?Erinnerung=3A_=3D=3Fiso-8859-1=3F?= =?iso-8859-1?q?Q=3F=3D22Syrien=5Fzwischen=5FAufstand=3D2C=5FB=3DFCrgerkri?= =?iso-8859-1?q?eg=5Fund=5FV=3DF6lkerm=3F=3Dord=3D=3Fiso-8859-1=3FQ=3F=3D2?= =?iso-8859-1?q?2=5F-=5FDonnerstag=5F=7C=5F14=2ENovember=5F2013=5F=7C=5F19?= =?iso-8859-1?q?=2E30=5F=7C=5FBuchladen=5F=3F=3D=22Rote_Stra=DFe=22?= In messageview is is wrong decoded: Erinnerung: =?iso-8859-1?Q?=22Syrien_zwischen_Aufstand=2C_B=FCrgerkrieg_und_V=F6lkerm?=ord=?iso-8859-1?Q?=22_-_Donnerstag_|_14.November_2013_|_19.30_|_Buchladen_?="Rote Straße" In message list the Subject is correctly shown as: Erinnerung: "Syrien zwischen Aufstand, Bürgerkrieg und Völkermord" - Donnerstag | 14.November 2013 | 19.30 | Buchladen "Rote Straße" replying: the subject is correct decoded. forward: the subject is NOT correctly decoded. -- 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
[kmail2] [Bug 327416] Subject isn't correctly shown in messageviewer cause to encoding
https://bugs.kde.org/show_bug.cgi?id=327416 Sandro Knauß changed: What|Removed |Added Summary|Subject isn't corretly |Subject isn't correctly |shown in messageviewer |shown in messageviewer |cause to encoding |cause to encoding -- 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
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- 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
[Akonadi] [Bug 327411] New: Akonadi hangs on boot
https://bugs.kde.org/show_bug.cgi?id=327411 Bug ID: 327411 Summary: Akonadi hangs on boot Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: andy...@mail.ru Created attachment 83474 --> https://bugs.kde.org/attachment.cgi?id=83474&action=edit Akonadi server self-test report and backtraces Sometimes, when the system boots, Akonadi services don't start. I only see akonadiserver, akonadi_control and mysqld processes at startup, no other Akonadi processes. I have two IMAP mail accounts set up, and Akonadi resources for them don't start. Kmail shows that Akonadi service is not started. Akonadi resources configuration in System settings says the same and offers to start Akonadi, but it does nothing. The only way to revive Akonadi is to forcefully kill all Akonadi and MySQL processes and attempt to start the service again from system settings. I'm on Kubuntu 13.10, x86_64. I have Nepomuk disabled. I attached Akonadi Server self-test report (from the system settings page) and backtraces from the hanging Akonadi processes. -- 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
[Akonadi] [Bug 326480] Akonadi fails to start
https://bugs.kde.org/show_bug.cgi?id=326480 --- Comment #18 from Graeme Hewson --- I directed libakonadi debug output to disk while I logged in to KDE (file attached). The messages make reference to /tmp/akonadi-ghewson.ws0sFY/akonadiserver.socket, but there is no such file. This is after a reboot (on Kubuntu, where /tmp is cleared between reboots). However, the file /did/ exist in the previous session, and in the current session ~/.local/share/akonadi/socket-$(hostname) is a link to /tmp/akonadi-ghewson.ws0sFY/akonadiserver.socket. The messages also say "Akonadi server is already starting up", but before logging in to KDE I started a terminal session and verified that Akonadi wasn't running. (It's very hard to see how it could have been!) To reiterate: sometimes Akonadi does start properly. In fact, while I was debugging, it usually did (presumably due to a change in the timing), and I had to try several times before it failed to start properly. -- 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
[Akonadi] [Bug 326480] Akonadi fails to start
https://bugs.kde.org/show_bug.cgi?id=326480 --- Comment #17 from Graeme Hewson --- Created attachment 83470 --> https://bugs.kde.org/attachment.cgi?id=83470&action=edit libakonadi debug output -- 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
[Akonadi] [Bug 322200] limit restarts of crashing resources
https://bugs.kde.org/show_bug.cgi?id=322200 ancow changed: What|Removed |Added CC||b...@ancow.no-ip.org --- Comment #13 from ancow --- I'd like to mention that I've had akonadi mail resources crash and restart several times per second in KDE 4.10 (either .4 or .5, I don't remember exactly). The crash counter was definitely not working, as the crashes caused popup notifications and were therefore easy to observe. I haven't had the crashes in several months, so I don't exactly know whether the problem persists. -- 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
[Akonadi] [Bug 322200] limit restarts of crashing resources
https://bugs.kde.org/show_bug.cgi?id=322200 Rainer Dorsch changed: What|Removed |Added CC||m...@bokomoko.de -- 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
[Akonadi] [Bug 322199] akonadi_imap spams perdition log when two clients are active and gets restarted all the time
https://bugs.kde.org/show_bug.cgi?id=322199 --- Comment #4 from Rainer Dorsch --- I confirm that I see this problem from time to time, unfortunately I have no procedure to trigger it, deterministically. I own also the dovecot imap server, i.e. I can provide debug messages from both sides. When I run into the problem again, is there any specific information I should collect, which may help you to better understand the issue? Many thanks, Rainer -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 322199] akonadi_imap spams perdition log when two clients are active and gets restarted all the time
https://bugs.kde.org/show_bug.cgi?id=322199 Rainer Dorsch changed: What|Removed |Added CC||m...@bokomoko.de -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 327372] Akregator crash on Muylinux.com
https://bugs.kde.org/show_bug.cgi?id=327372 Jekyll Wu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu --- *** This bug has been marked as a duplicate of bug 264526 *** -- 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
[akregator] [Bug 327371] When I open Akregator this crash
https://bugs.kde.org/show_bug.cgi?id=327371 Jekyll Wu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu --- *** This bug has been marked as a duplicate of bug 264526 *** -- 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
[kmail2] [Bug 319204] Mailbodies are deleted by Kmails spam-bogofilter on the remote IMAP Server!
https://bugs.kde.org/show_bug.cgi?id=319204 --- Comment #7 from Martin Steigerwald --- One indication of a relationship of the two bugs would be one byte sized files on the IMAP server. Can you check there with find -size 1c ? -- 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
[kmail2] [Bug 319204] Mailbodies are deleted by Kmails spam-bogofilter on the remote IMAP Server!
https://bugs.kde.org/show_bug.cgi?id=319204 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #6 from Martin Steigerwald --- Maybe there is a relation ship with Bug 319226 - produces 1-byte-sized on processing crm114 spam filter rules https://bugs.kde.org/319226 It is with POP3 tough, but at least in both cases Akonadi pipes a mail through an external program. Would be pretty good to get confirmation and even better to actually find on why this is happening. I am still not using those CRM114 spam filter rules due to this bug. -- 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
[Akonadi] [Bug 322199] akonadi_imap spams perdition log when two clients are active and gets restarted all the time
https://bugs.kde.org/show_bug.cgi?id=322199 Martin Steigerwald changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||mar...@lichtvoll.de Ever confirmed|0 |1 --- Comment #3 from Martin Steigerwald --- For the record, I never answered this for this one (only for bug #322200: I do believe this bug is more important than normal, so I think my raising of the importance was justified. I have read on debian-kde mailinglist from two user having hit maximum amount of connection from an IP for an IMAP server. I asked them to comment here: http://lists.debian.org/debian-kde/2013/11/msg00012.html Downgrading severity of bugs doesn´t make them any less dangerous. This almost ate our mail proxy server. No amount of denial will help here. This bug is for real. Whether the resource crashes or it just reconnects endlessly, doesn´t matter regarding the effect it makes on the server. Or well if it just reconnects the effect may even be worse, cause it is likely able to make more reconnects within a given amount of time without restarting the akonadi imap resource each time. I am setting this to confirmed due to above reference. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[knode] [Bug 327394] New: Wrong error message when posting failed
https://bugs.kde.org/show_bug.cgi?id=327394 Bug ID: 327394 Summary: Wrong error message when posting failed Classification: Unclassified Product: knode Version: 4.10.5 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: martin7...@gmail.com When I post to a newsgroup, I get an error "The posting of this article to the server failer. Please check that you are not trying to post to a read-only group" The server actually gives me a much better error message: - Posting in UTF-8 impossible - Posting in HTML impossible This message should be given to the end-user instead of the generic confusing message. 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
