[Bug 291746] sometimes imap accounts are not updated any more
https://bugs.kde.org/show_bug.cgi?id=291746 Christian joulupukin.ton...@yandex.ru changed: What|Removed |Added CC||joulupukin.ton...@yandex.ru --- Comment #3 from Christian joulupukin.ton...@yandex.ru --- I have the same problem or a similar problem. Sometimes, after a while of absence (it is possible that the network connection was lost in the meantime, but it is now available again, KMail was running all the time), the IMAP folder contents and new message counts are out of sync with the IMAP server. (Checked eg on the webmail in a browser window.) Then, also, KMail cannot display IMAP messages that have to be fetched from the server. The status bar says it is ready, the progress bar says 0%, and when I click on the arrow, it shows me that it is busy synchronising another IMAP account (0%). Clicking on Update account or Update folder seems to have no effect. Closing Kontact (i.e. completely closing Kontact so that the icons disappear) and restarting it helps sometimes, but not 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 246195] Cannot create Google Contacts akonadi resource [strlen, strdup,extract_and_check_multi, ..., gcal_get_contacts]
https://bugs.kde.org/show_bug.cgi?id=246195 Gary Cobb cobb...@gmail.com changed: What|Removed |Added CC||cobb...@gmail.com -- 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
[Bug 246195] Cannot create Google Contacts akonadi resource [strlen, strdup,extract_and_check_multi, ..., gcal_get_contacts]
https://bugs.kde.org/show_bug.cgi?id=246195 --- Comment #49 from Gary Cobb cobb...@gmail.com --- Created attachment 73047 -- https://bugs.kde.org/attachment.cgi?id=73047action=edit New crash information added by DrKonqi akonadi_googledata_resource (4.7) on KDE Platform 4.7.2 (4.7.2) release 5 using Qt 4.7.4 - What I was doing when the application crashed: Adding my Google account information, then akonadi crashed. -- Backtrace (Reduced): #8 0x7f529b68d5b8 in extract_and_check_multi (doc=optimized out, xpath_expression=optimized out, getContent=0, attr1=0x7f529b69abc5 address, attr2=0x7f529b69abc1 rel, attr3=0x7f529b69ac07 protocol, attr4=0x7f529b69abe3 primary, values=0xa30630, types=0xa30640, protocols=0xa30638, pref=0xa3064c) at /usr/src/debug/libgcal-0.9.6/src/atom_parser.c:295 #9 0x7f529b68eb0d in atom_extract_contact (entry=optimized out, ptr_entry=0xa30580) at /usr/src/debug/libgcal-0.9.6/src/atom_parser.c:753 #10 0x7f529b694228 in extract_all_contacts (doc=optimized out, data_extract=optimized out, length=optimized out) at /usr/src/debug/libgcal-0.9.6/src/gcal_parser.c:434 #11 0x7f529b6980a5 in gcal_get_all_contacts (gcalobj=0x832ba0, length=0x79d828) at /usr/src/debug/libgcal-0.9.6/src/gcont.c:111 #12 0x7f529b69568b in gcal_get_contacts (gcalobj=0x832ba0, contact_array=0x79d820) at /usr/src/debug/libgcal-0.9.6/src/gcontact.c:155 -- 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
[Bug 295484] filtering removes email's content
https://bugs.kde.org/show_bug.cgi?id=295484 pipapo pi...@arcor.de changed: What|Removed |Added CC||pi...@arcor.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
[Bug 280761] crash after entering sieve password during fetch mail
https://bugs.kde.org/show_bug.cgi?id=280761 --- Comment #7 from Dennis Schridde devuran...@gmx.net --- Created attachment 73049 -- https://bugs.kde.org/attachment.cgi?id=73049action=edit New crash information added by DrKonqi kontact (4.9) on KDE Platform 4.9.00 using Qt 4.8.2 - What I was doing when the application crashed: Same as before: KWallet password dialogue appears to have timed out, Sieve password dialogue is being displayed, I wait even longer before entering my password and Kontact crashes. This time I am using KDE 4.9.0, still with Qt 4.8.2. -- Backtrace (Reduced): #6 0x003a5f52aa61 in QUrl::setUserName(QString const) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f456ee16884 in KManageSieve::Session::saslInteract (this=this@entry=0x17aebf0, in=0x18275c0) at /var/tmp/portage/kde-base/kmail-4.9.0-r1/work/kmail-4.9.0/libksieve/kmanagesieve/session.cpp:448 #8 0x7f456ee175d4 in KManageSieve::Session::startAuthentication (this=this@entry=0x17aebf0) at /var/tmp/portage/kde-base/kmail-4.9.0-r1/work/kmail-4.9.0/libksieve/kmanagesieve/session.cpp:375 #9 0x7f456ee18329 in KManageSieve::Session::processResponse (this=this@entry=0x17aebf0, response=..., data=...) at /var/tmp/portage/kde-base/kmail-4.9.0-r1/work/kmail-4.9.0/libksieve/kmanagesieve/session.cpp:190 #10 0x7f456ee1921d in KManageSieve::Session::dataReceived (this=0x17aebf0) at /var/tmp/portage/kde-base/kmail-4.9.0-r1/work/kmail-4.9.0/libksieve/kmanagesieve/session.cpp:134 -- 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 304741] The messages i received have blank body
https://bugs.kde.org/show_bug.cgi?id=304741 Christian joulupukin.ton...@yandex.ru changed: What|Removed |Added CC||joulupukin.ton...@yandex.ru --- Comment #5 from Christian joulupukin.ton...@yandex.ru --- Does this have to do with the Filter scanning for viruses, by any chance? I had set up such a filter (using clamd and the Filter autoconfiguration wizard) and that filter made all incoming emails blank. (It didn't save the originals, though.) Luckily I switched the filter off after a few hours! -- 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 304817] New: Mail Dispatcher Agent crashed when KMail closed
https://bugs.kde.org/show_bug.cgi?id=304817 Bug ID: 304817 Severity: crash Version: 4.7 Priority: NOR CC: vkra...@kde.org Assignee: kdepim-bugs@kde.org Summary: Mail Dispatcher Agent crashed when KMail closed Classification: Unclassified OS: Linux Reporter: giecr...@stegny.2a.pl Hardware: openSUSE RPMs Status: UNCONFIRMED Component: Mail Dispatcher Agent Product: Akonadi Application: akonadi_maildispatcher_agent (4.7) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.1.10-1.16-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: I closed KMail and discovered a Mail Dispatcher Agend password prompt underneath so I entered the password in it and submitted the entry. -- Backtrace: Application: Mail Dispatcher Agent (akonadi_maildispatcher_agent), signal: Segmentation fault [KCrash Handler] #6 KCoreConfigSkeleton::findItem (this=0x1636, name=...) at /usr/src/debug/kdelibs-4.8.4/kdecore/config/kcoreconfigskeleton.cpp:1318 #7 0x7fce197c4e69 in KCoreConfigSkeleton::isImmutable (this=optimized out, name=optimized out) at /usr/src/debug/kdelibs-4.8.4/kdecore/config/kcoreconfigskeleton.cpp:1307 #8 0x7fce192651a8 in setUserName (v=..., this=0x1636) at /usr/src/debug/kdepimlibs-4.7.2/build/mailtransport/transportbase.h:165 #9 MailTransport::SmtpJob::startSmtpJob (this=0x964a70) at /usr/src/debug/kdepimlibs-4.7.2/mailtransport/smtpjob.cpp:190 #10 0x7fce1926653a in MailTransport::SmtpJob::doStart (this=0x964a70) at /usr/src/debug/kdepimlibs-4.7.2/mailtransport/smtpjob.cpp:129 #11 0x7fce1924dd34 in MailTransport::TransportJob::start (this=0x964a70) at /usr/src/debug/kdepimlibs-4.7.2/mailtransport/transportjob.cpp:129 #12 0x0041602f in SendJob::Private::doTraditionalTransport (this=0x8441d0) at /usr/src/debug/kdepim-runtime-4.7.2/agents/maildispatcher/sendjob.cpp:197 #13 0x0041697e in SendJob::Private::doTransport (this=0x8441d0) at /usr/src/debug/kdepim-runtime-4.7.2/agents/maildispatcher/sendjob.cpp:130 #14 0x0041729e in SendJob::qt_metacall (this=0x8550d0, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0x85ad20) at /usr/src/debug/kdepim-runtime-4.7.2/build/agents/maildispatcher/sendjob.moc:85 #15 0x7fce19ffee06 in QObject::event (this=0x8550d0, e=optimized out) at kernel/qobject.cpp:1204 #16 0x7fce17c83fe4 in notify_helper (e=0x9fa3e0, receiver=0x8550d0, this=0x653170) at kernel/qapplication.cpp:4551 #17 QApplicationPrivate::notify_helper (this=0x653170, receiver=0x8550d0, e=0x9fa3e0) at kernel/qapplication.cpp:4523 #18 0x7fce17c88db3 in QApplication::notify (this=0x7fff606dc240, receiver=0x8550d0, e=0x9fa3e0) at kernel/qapplication.cpp:4412 #19 0x7fce189ca746 in KApplication::notify (this=0x7fff606dc240, receiver=0x8550d0, event=0x9fa3e0) at /usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311 #20 0x7fce19fe5d0c in QCoreApplication::notifyInternal (this=0x7fff606dc240, receiver=0x8550d0, event=0x9fa3e0) at kernel/qcoreapplication.cpp:915 #21 0x7fce19fe95ba in sendEvent (event=0x9fa3e0, receiver=0x8550d0) at kernel/qcoreapplication.h:231 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x62a110) at kernel/qcoreapplication.cpp:1539 #23 0x7fce1a0149a3 in sendPostedEvents () at kernel/qcoreapplication.h:236 #24 postEventSourceDispatch (s=0x650350) at kernel/qeventdispatcher_glib.cpp:279 #25 0x7fce155845dd in g_main_dispatch (context=0x650260) at gmain.c:2425 #26 g_main_context_dispatch (context=0x650260) at gmain.c:2995 #27 0x7fce15584dd8 in g_main_context_iterate (context=0x650260, block=optimized out, dispatch=1, self=optimized out) at gmain.c:3073 #28 0x7fce15584fa9 in g_main_context_iteration (context=0x650260, may_block=1) at gmain.c:3136 #29 0x7fce1a014dcf in QEventDispatcherGlib::processEvents (this=0x6299d0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #30 0x7fce17d2769e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x7fce19fe4842 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #32 0x7fce19fe4a97 in QEventLoop::exec (this=0x7fff606d7a80, flags=...) at kernel/qeventloop.cpp:204 #33 0x7fce1814fc76 in QDialog::exec (this=0x7fff606d7af0) at dialogs/qdialog.cpp:554 #34 0x7fce19265109 in MailTransport::SmtpJob::startSmtpJob (this=0x952ab0) at /usr/src/debug/kdepimlibs-4.7.2/mailtransport/smtpjob.cpp:183 #35 0x7fce1926653a in MailTransport::SmtpJob::doStart (this=0x952ab0) at /usr/src/debug/kdepimlibs-4.7.2/mailtransport/smtpjob.cpp:129 #36 0x7fce1924dd34 in MailTransport::TransportJob::start (this=0x952ab0) at
[Bug 304821] New: Signing/Encrypting a mail doesn't respect the settings in my addressbook of the contact
https://bugs.kde.org/show_bug.cgi?id=304821 Bug ID: 304821 Severity: normal Version: 4.9.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Signing/Encrypting a mail doesn't respect the settings in my addressbook of the contact Classification: Unclassified OS: Linux Reporter: regi.h...@gmx.net Hardware: openSUSE RPMs Status: UNCONFIRMED Component: crypto Product: kmail2 I have a PGP and a S/MIME certificate/key. I have set in my identity settings the preferred format for encryption and signing to all. When I write an email to al...@example.com, who is configured in my addressbook only to allow S/MIME in the protocol settings, kmail2 silently ignores this and sends the message signed with my PGP-Key. Additionally the settings for signing and encryption are set to always, kmail2 never signs nor encrypts the message nor warn me to do so. It silently sends the message. If you activate the setting always show encryption key... in settings-security-create message you'll see that the settings from the addressbook are ignored, except the public key. Reproducible: Always Steps to Reproduce: 1. set up an account with a PGP-Key/Cert and a S/MIME Key/Cert 2. let the prefered format for signing and encryption at the default (All) 3. create a contact with a S/MIME public key 4. set the allowed protocol to S/MIME only 5. set the sending options to always sign and always encrypt 6. send an email to this contact 7. send a signed email to the contact Actual Results: point 6. sends the email not signed and not encrypted point 7. sends the email signed with my PGP key Expected Results: point 6. kmail2 should warn me about the missing signature / encryption, like it warns me if I forgot to enter a subject in the message. And give me the option to send the email unsigned/unencrypted point 7. kmail2 should the email sign with my S/MIME key. In the case that I don't have a Cert/Key fitting the options in the contact, it should bring up a dialog where I can choose to abort or send the email unsigned In both cases an additional link to the respective contact would be the cream on top, which would be especially helpful when sending emails to more then one person -- 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 304821] Signing/Encrypting a mail doesn't respect the settings in my addressbook of the contact
https://bugs.kde.org/show_bug.cgi?id=304821 --- Comment #1 from regi.h...@gmx.net --- To clarify point 4 and 5 of the Steps to Reproduce 4. set the allowed protocol to S/MIME only FOR THE CREATED CONTACT 5. set the sending options to always sign and always encrypt FOR THE CREATED CONTACT -- 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 304823] New: Removing local folders impossible
https://bugs.kde.org/show_bug.cgi?id=304823 Bug ID: 304823 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Removing local folders impossible Classification: Unclassified OS: Linux Reporter: bugs.kde@falkensweb.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.5) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-26-generic-pae i686 Distribution: Ubuntu 12.04 LTS -- Information about the crash: Every time I go to the list of accounts and remove the pointless 'local folders' one, it reappears. If I then remove that one Kontact crashes. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb20f9980 (LWP 3332))] Thread 4 (Thread 0xafb14b40 (LWP )): #0 0xb76e0424 in __kernel_vsyscall () #1 0xb390296b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb600c3dc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb578a263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb578a37f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb38fed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0xb5ffeace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xaf1f3b40 (LWP 3334)): #0 0xb3650dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0xb6265315 in do_gettime (frac=0xaf1f3000, sec=0xaf1f2ff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb634f226 in QTimerInfoList::updateCurrentTime (this=0xae802074) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb634f57a in QTimerInfoList::timerWait (this=0xae802074, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb634de23 in timerSourcePrepareHelper (src=optimized out, timeout=0xaf1f30ec) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb382b872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb382bfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb382c201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb634e8e7 in QEventDispatcherGlib::processEvents (this=0xae800468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0xb631a50d in QEventLoop::processEvents (this=0xaf1f3270, flags=...) at kernel/qeventloop.cpp:149 #11 0xb631a7a9 in QEventLoop::exec (this=0xaf1f3270, flags=...) at kernel/qeventloop.cpp:204 #12 0xb620394c in QThread::exec (this=0x8e20890) at thread/qthread.cpp:501 #13 0xb6203a3b in QThread::run (this=0x8e20890) at thread/qthread.cpp:568 #14 0xb6206de0 in QThreadPrivate::start (arg=0x8e20890) at thread/qthread_unix.cpp:298 #15 0xb38fed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0xb5ffeace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xaa8fdb40 (LWP 3383)): #0 0xb3650dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0xb6265315 in do_gettime (frac=0xaa8fcfb0, sec=0xaa8fcfa8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb634f226 in QTimerInfoList::updateCurrentTime (this=0xa9f020a4) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb634f57a in QTimerInfoList::timerWait (this=0xa9f020a4, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0xb634de23 in timerSourcePrepareHelper (src=optimized out, timeout=0xaa8fd0bc) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb634debd in timerSourcePrepare (source=0xa9f02070, timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb382b872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb382bfaf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb382c201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0xb634e8e7 in QEventDispatcherGlib::processEvents (this=0xa9f02460, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0xb631a50d in QEventLoop::processEvents (this=0xaa8fd240, flags=...) at kernel/qeventloop.cpp:149 #12 0xb631a7a9 in QEventLoop::exec (this=0xaa8fd240, flags=...) at kernel/qeventloop.cpp:204 #13 0xb620394c in QThread::exec (this=0x8f58cb0) at thread/qthread.cpp:501 #14 0xb62f7b5d in QInotifyFileSystemWatcherEngine::run (this=0x8f58cb0) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb6206de0 in QThreadPrivate::start (arg=0x8f58cb0) at thread/qthread_unix.cpp:298 #16 0xb38fed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0xb5ffeace in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb20f9980 (LWP 3332)): [KCrash Handler] #7 ref (this=0x0) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120 #8 QPen::QPen (this=0xa7a6d30)
[Bug 303415] Create new account only after finishing dialog
https://bugs.kde.org/show_bug.cgi?id=303415 Jeff Strunk jstr...@math.utexas.edu changed: What|Removed |Added CC||jstr...@math.utexas.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
[Bug 304829] New: Make the password dialog for the private key more readable
https://bugs.kde.org/show_bug.cgi?id=304829 Bug ID: 304829 Severity: wishlist Version: 4.9.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Make the password dialog for the private key more readable Classification: Unclassified OS: Linux Reporter: regi.h...@gmx.net Hardware: openSUSE RPMs Status: UNCONFIRMED Component: crypto Product: kmail2 The password dialog (titled pinentry-qt) for the private key (PGP and S/MIME) displays the information of the chosen certificate in a more or less raw format. This format would be OK for users who are familiar with certificates. But having more than one certificate it is difficult to directly notice the relevant information. And for people who are not familiar with certificates the displayed information are very uncomfortable. Reproducible: Always Steps to Reproduce: 1. send an encrypted or signed email with a password protected private key 2. have a look at the password dialog Actual Results: the raw subject and some additional information like validity are displayed in a floating text format Expected Results: show a dialog with the most important information on separate lines, like: - Common Name (CN) - Email-Address (EMAIL) - Optionally additional Email-Addresses (SubjectAltName) - Valid until (in localized format?) or an icon showing the validity status - A link to the raw certificate information would be also nice Alternatively there could be also a dialog showing the expected result information of the certificate, before the password dialog opens up. This could be also useful to choose a certificate, if there are two or more possible certificates for the requested action. -- 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 302145] I cannot see a message without switch to html mode
https://bugs.kde.org/show_bug.cgi?id=302145 Martin Koller kol...@aon.at changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||kol...@aon.at Resolution|--- |INVALID --- Comment #7 from Martin Koller kol...@aon.at --- The mail has a header Content-Type: multipart/alternative; boundary=_=_swift-DELETED.14779692_=_ which tells the mail client to either show the one (text) or the other (html) format, and the boundary tells it where that part starts. The text only part (Content-Type: text/plain;) contains what kmail shows by default (as you seem to not have told it to show html per default). So kmail is correct in what it shows when you do not tell it explicitly that you want to see html instead. What you mention as kmail shows a html warning box ... this is only done when the mail comes in HTML _only_ (which is not the case here) -- 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 303292] Filtering crashed when kmail started up
https://bugs.kde.org/show_bug.cgi?id=303292 Jekyll Wu adap...@gmail.com changed: What|Removed |Added CC||jos...@joshuakugler.com --- Comment #3 from Jekyll Wu adap...@gmail.com --- *** Bug 304824 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
[Bug 304824] akonadi_mailfilter_agent crashes when filtering
https://bugs.kde.org/show_bug.cgi?id=304824 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jekyll Wu adap...@gmail.com --- *** This bug has been marked as a duplicate of bug 303292 *** -- 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 304741] The messages i received have blank body
https://bugs.kde.org/show_bug.cgi?id=304741 --- Comment #6 from Dimitrios Glentadakis dgl...@gmail.com --- Excellent Christian! After disabled the spam filter i don't have any more duplicate blank messages. Thanks a million! -- 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 304741] The messages i received have blank body when the spam filter is enabled
https://bugs.kde.org/show_bug.cgi?id=304741 Dimitrios Glentadakis dgl...@gmail.com changed: What|Removed |Added Summary|The messages i received |The messages i received |have blank body |have blank body when the ||spam filter is enabled -- 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
