[kmail2] [Bug 420436] New: Modify header section
https://bugs.kde.org/show_bug.cgi?id=420436 Bug ID: 420436 Summary: Modify header section Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- SUMMARY Kmail already has many options to customize the interface and that's amazing! But there's almost nothing to customize the part where the basic headers of an email are displayed, like sender, recipient, subject, etc. Options to change which items should be displayed, list all headers, see the source of the email, would be very useful. Another necessary modification would be the possibility to move the reply buttons, forward, and other useful ones to that same place. In my opinion it makes more sense that these buttons stay in the header. Currently, they only stay on the top menu and you can move it to one of the sides or keep it "floating". Something like what I tried to do in this image: https://i.imgur.com/etvJlxE.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420434] New: Change only body font size
https://bugs.kde.org/show_bug.cgi?id=420434 Bug ID: 420434 Summary: Change only body font size Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- SUMMARY Changing the font size of the mail body also changes the header font. OBSERVED RESULT I changed the default font size of kmail because I think the default size is too small (at least on my monitor) but I would like this change to only apply to the message body and not the header. As some email addresses can be very large, or there can be a lot of recipients, this becomes a mess and takes up almost every piece of screen available See this screenshot: https://i.imgur.com/djDh9nt.png EXPECTED RESULT Ideally, it would be possible to edit the font size individually for each of the two separately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381579] add and handle Openpgp header
https://bugs.kde.org/show_bug.cgi?id=381579 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #1 from Parker --- Autocrypt does that. It hasn't been implemented in kmail yet. https://bugs.kde.org/show_bug.cgi?id=388036 Maybe this is a duplicate bug? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420433] Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 Parker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Parker --- I just realized that this option appears when creating a new identity. sorry -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416181] Allow selecting different locale for each identity / account
https://bugs.kde.org/show_bug.cgi?id=416181 Parker changed: What|Removed |Added CC||sotadic_restage@simplelogin ||.co --- Comment #1 from Parker --- up -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420433] Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 --- Comment #1 from Parker --- A screenshot of the current options https://i.imgur.com/ReTcDUc.png -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420433] New: Clone identity
https://bugs.kde.org/show_bug.cgi?id=420433 Bug ID: 420433 Summary: Clone identity Product: kmail2 Version: Git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sotadic_rest...@simplelogin.co Target Milestone: --- Kmail already offers some options like modify, delete and rename, but it's still not possible to clone an existing identity. That would be very helpful. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 5.6.6 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420423] HTML font size is affected by view zoom in composer
https://bugs.kde.org/show_bug.cgi?id=420423 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- Sdfsfdfdf sqdqs dqsdqsdqsdqsd q => 1.2em now. so it depends against zoom. it's fixed from long time ago. 5.9.3 is very old :) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 420423] New: HTML font size is affected by view zoom in composer
https://bugs.kde.org/show_bug.cgi?id=420423
Bug ID: 420423
Summary: HTML font size is affected by view zoom in composer
Product: kmail2
Version: 5.9.3
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-bugs@kde.org
Reporter: alejandro_a...@yahoo.es
Target Milestone: ---
First of all, i am not sure if this has already been fixed in more modern
versions of kmail (using Debian Stable here).
STEPS TO REPRODUCE
1. Compose an email in HTML mode with, let's say Noto Sans at 11 points of size
2. Make text bigger or smaller for viewing (Ctrl+Mouse scroll wheel, or
Ctrl+{,+})
3. Send message
4. Received message will have a font size proportional to the zoom you used
composing the message
It's also notable that when kmail receives emails composed like this (a CC for
yourself) the size of the text will appear normal so you won't notice but other
people with different emails clients will
In my mind, zoom of the text should be independent of the font size sent in the
HTML. But that's my two cents
OBSERVED RESULT
Example of the HTML code generated by the composer
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Stable 10.3
KDE Plasma Version: 5.14.5.1
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3+dfsg1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 420414] New: What I was doing when the application crashed
https://bugs.kde.org/show_bug.cgi?id=420414 Bug ID: 420414 Summary: What I was doing when the application crashed Product: Akonadi Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: christian.holzm...@t-online.de Target Milestone: --- Application: akonadiserver (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-46-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: reboot after successfull upgrade to "eoan ermine" per "do-release-upgrade" -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=16, buf=0x7ffdf3f1ba20, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26 [Current thread is 1 (Thread 0x7f1f5ce46d40 (LWP 2692))] Thread 30 (Thread 0x7f1ef77fe700 (LWP 2736)): #0 0x7f1f5f61cc3d in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1f5f5d0235 in g_main_context_query () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1f5f5d0a28 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1f60c31653 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x55c74fd1b69e in ?? () #7 0x7f1f60c12696 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f1f60c05de5 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f1f60bd9a07 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f1f60c30990 in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f1f60c3126c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1f5f5d08bd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f1f5f5d0b40 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f1f60c31635 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f1f60a11a45 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f1f60a12c92 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f1f5fdbb669 in start_thread (arg=) at pthread_create.c:479 #20 0x7f1f6067d323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f1ef7fff700 (LWP 2732)): #0 __GI___libc_read (nbytes=16, buf=0x7f1ef7ffe710, fd=110) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=110, buf=0x7f1ef7ffe710, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f1f5f61870f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1f5f5d05fe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1f5f5d0a52 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f1f60c31653 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x55c74fd1b69e in ?? () #9 0x7f1f60c12696 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f1f60c05de5 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f1f60bd9a07 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f1f60c30990 in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f1f60c3126c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f1f5f5d08bd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f1f5f5d0b40 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f1f5f5d0be3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f1f60c31635 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f1f60bd85cb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f1f60a11a45 in QThread::exec() () from /usr/lib/x86_64-lin
[kmail2] [Bug 358071] Kmail adds wrong contacts to e-mail when using contact groups
https://bugs.kde.org/show_bug.cgi?id=358071 --- Comment #4 from Robert Spillner --- I dug into this bug a little by myself and found out that in order to resolve contact group names into mail addresses kmail does a search via akonadi. When using *spaces* in the contact group names with similar words in both contact group names this search will have multiple results. So if you have two list, say foo bar foo crowbar, and you use "foo crowbar" as recipient the akonadi search query will return "foo bar" and "foo crowbar" since "foo" is in both of them. KMail apparently chooses the first result of the result list, which is "foo bar". As a workaround, if you rename your contact lists to foorbar foocrowbar this will not happen. Unfortunately, KMail does not allow "_" in the names. I guess that there should be a better input validation and masking of the search word in kmail when quering for a contact group. -- You are receiving this mail because: You are the assignee for the bug.
