[kmailtransport] [Bug 400195] Some emails stays in outgoing folder
https://bugs.kde.org/show_bug.cgi?id=400195 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #5 from Wolfgang Bauer --- (In reply to Samuel Gilbert from comment #4) > Authentication: XOAUTH2 See bug#421664. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 423248] New: Missing menu on mail tab
https://bugs.kde.org/show_bug.cgi?id=423248 Bug ID: 423248 Summary: Missing menu on mail tab Product: kontact Version: 5.13.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: nat...@deckinga.com Target Milestone: --- SUMMARY When I'm in Kontact and I switch from Summary to Mail to Contacts to ... I have the standard text menu bar at the top with the "Main Toolbar" shown immediately underneath that. Except for the Mail section. On that section, I do not see the "File, View, ..." menu nor do I have any toolbars shown. I think if I had the text one, I could add the toolbar that would then allow me to add a "new email" button and other shortcuts, but as of right now I have no way to create a new email from within the Kontact window, I have to go out to the separate KMail UI and that somewhat defeats the purpose of an integrated UI. When I open KMail as a stand alone application, everything works as expected. I have tried updating everything that's available as standard on Fedora 32 and rebooting the computer to make sure that it isn't a transient situation. Side note, the "New Message" in the main tool bar on the Summary tab works as expected. STEPS TO REPRODUCE 1. Open Kontact 2. Switch from "Summary" to "Mail" 3. Notice all menus are missing OBSERVED RESULT All menus are missing and there is no way to start a new email message EXPECTED RESULT At the very least, the "File, View, ..." text menu should exist and allow me to add a Toolbar with the shortcuts I want (including create new email). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 KDE spin (Kernel 5.6.19-300.fc32.x86_64) (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 423246] New: Obvious phishing URLs are not recognized
https://bugs.kde.org/show_bug.cgi?id=423246 Bug ID: 423246 Summary: Obvious phishing URLs are not recognized Product: kmail2 Version: 5.14.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: david.hu...@mailbox.org CC: david.hu...@mailbox.org Target Milestone: --- SUMMARY KMail reports me various links as being “scam”, because they contain some odd detail, like ending with &. But a link like https://kde.оrg is not reported, although it is obviously a phishing link. (It contains a cyrillic o and points to https://kde.xn--rg-emc/) STEPS TO REPRODUCE 1. Send https://kde.оrg as email to yourself OBSERVED RESULT Nothing special EXPECTED RESULT Shows me some warning about a non-ascii domain name SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I don’t know what scam means, the usual meaning is very vague on URLs. But based on the previous warnings, I expected KMail to recognize phishing links. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 --- Comment #3 from Arne Spiegelhauer --- I have done some debugging and found a couple of issues in smtpjob.cpp (kmailtransport) and accountmanager.cpp (libkgapi). 1. When SmtpJob::startPasswordRetrieval(true) is executed and calls KGAPI2::AccountManager::instance()->refreshTokens after a successful findAccount, the AccountPromise created for findAccount has not yet been destroyed and is reused by the createPromise function. Since mRunning is true, the only action of refreshTokens is to return the AccountPromise, and since its emitFinished() has already been executed, nothing more happens. 2. When the previous AccountPromise is removed from the mPendingPromises hash table before refreshTokens is called, refresh succeeds and the mail is successfully sent to the SMTP server, but the mail is not deleted/moved from the outbox. This is due to a missing removeSubjob for the TokenExpired case in the SmtpJob::slotResult function, leading to the !hasSubjobs() condition for sending a noError result is not fulfilled. 3. loginJob:result is connected to SmtpJob::slotResult both explicitly and as a result of addSubJob, leading to SmtpJob::slotResult receiving duplicated result signals from loginJob. 4. Not really a problem, but an unsuccessful login attempt on expired token can be avoided by adopting the algorithm used in gmailpasswordrequester.cpp from kdepim-runtime. When refresh is not forced, gmailpasswordrequester calls KGAPI2::AccountManager::instance()->getAccount, which does a token refresh if a comparison between current time and calculated expiry time indicates that it is needed. 5. Not really related, but the code at the end of SmtpJob::startSmtpJob looks like it could start a password retrieval and a sendjob at the same time. -- You are receiving this mail because: You are on the CC list for the bug.
[kmailtransport] [Bug 400195] Some emails stays in outgoing folder
https://bugs.kde.org/show_bug.cgi?id=400195 Samuel Gilbert changed: What|Removed |Added CC||samuel.gilbert@usherbrooke. ||ca --- Comment #4 from Samuel Gilbert --- I have the same issue with a Gmail account in Kmail 5.14.2(20.04.2) on Linux (x86_64) release 5.7.4-arch1-1 Outgoing mail server: smtp.gmail.com Encryption: STARTTLS Port: 587 Authentication: XOAUTH2 Some mails will be sent right away, but after a while, they just sit in the outbox. It take a long time, but I eventually get a notification informing me that sending has failed: "Failed to transport message. The remote host closed the connection." I believe this is a problem with Kmail or the mail transport agent since the mails get sent right away after a reboot. I tried to kill the akonadi_maildispatcher_agent process, but even if it re-spawns automatically, sending the queued messages doesn't work. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 423121] Adding complete task event in journal doesn't work if task completed via "completed" slider
https://bugs.kde.org/show_bug.cgi?id=423121 --- Comment #1 from der_fenix --- Also, journal entry is not created if the task was marked as completed from other app (calendar synced via caldav) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 423222] New: Akonadi crashes while importing mails into KMail
https://bugs.kde.org/show_bug.cgi?id=423222 Bug ID: 423222 Summary: Akonadi crashes while importing mails into KMail Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: claus_...@webspeed.dk Target Milestone: --- Application: akonadiserver (5.14.2 (20.04.2)) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 4.15.0-106-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: I had connected to a POP3-server and was fetching mails (several thousands mails needs to be imported). After having imported hundreds of mails Akonadi crashed. This happened three times in a row. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x7f8988f05801 in __GI_abort () at abort.c:79 #6 0x7f898955a957 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f8989560ae6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7f8989560b21 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f89898e4e2b in qTerminate () at global/qglobal.cpp: #10 0x7f8989909dc3 in QThreadPrivate::start (arg=0x55a279ac1c80) at thread/qthread_unix.cpp:354 #11 0x7f8987a5c6db in start_thread (arg=0x7f897aaad700) at pthread_create.c:463 #12 0x7f8988fe688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7f8985e5e2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8985e190b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8985e19570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8985e196dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f8989b587cb in QEventDispatcherGlib::processEvents (this=0x7f897c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f8989af7d2a in QEventLoop::exec (this=this@entry=0x7f8980bf8d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f8989908757 in QThread::exec (this=this@entry=0x7f898a49ada0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:536 #8 0x7f898a222555 in QDBusConnectionManager::run (this=0x7f898a49ada0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #9 0x7f8989909c2c in QThreadPrivate::start (arg=0x7f898a49ada0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:342 #10 0x7f8987a5c6db in start_thread (arg=0x7f8980bf9700) at pthread_create.c:463 #11 0x7f8988fe688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 #1 0x7f8985e195c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8985e196dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8989b587ac in QEventDispatcherGlib::processEvents (this=0x55a279a7e210, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f8989af7d2a in QEventLoop::exec (this=this@entry=0x7ffdfbf50370, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f8989b014a0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1383 #6 0x55a2787cf0ea in main (argc=, argv=) at ./src/server/main.cpp:79 Possible duplicates by query: bug 422775, bug 422433, bug 422374, bug 422017, bug 421576. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417862] Kmail doesn't allow to sign messages
https://bugs.kde.org/show_bug.cgi?id=417862 Iyán Méndez Veiga changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Iyán Méndez Veiga --- Trying to debug a different issue (https://bugs.kde.org/show_bug.cgi?id=422870) I had to install some VMs so I decided to try to use my certificate on them. In both KDE Neon and a fresh Archlinux installation it works! So this is clearly an issue of my computer and not a bug in kmail/kleopatra. Please close the issue and sorry for previous comment. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417863] Akonadi Server crash
https://bugs.kde.org/show_bug.cgi?id=417863 --- Comment #1 from forenk...@gmx.de --- Created attachment 129511 --> https://bugs.kde.org/attachment.cgi?id=129511=edit New crash information added by DrKonqi kontact (5.14.2 (20.04.2)) using Qt 5.15.0 - What I was doing when the application crashed: reading emails. More precisely, a Whatsapp message had also popped up (via firefox) - Custom settings of the application: -- Backtrace (Reduced): #6 0x7fddf36a886a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #7 0x7fddf36b4d8a in __cxxabiv1::__terminate (handler=) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #8 0x7fddf36b4df7 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #9 0x7fddf36b509e in __cxxabiv1::__cxa_throw (obj=, tinfo=0x7fdd779ce798 , dest=0x7fdd774bc430) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95 [...] #15 0x7fdd7746c475 in Xapian::Database::get_termfreq(std::__cxx11::basic_string, std::allocator > const&) const () from /usr/lib/libxapian.so.30 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 417863] Akonadi Server crash
https://bugs.kde.org/show_bug.cgi?id=417863 forenk...@gmx.de changed: What|Removed |Added CC||forenk...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
