[kmail2] [Bug 321684] kmail2 embedded mail can't be opened - kmail2 reports contains not a mail

[Jonathan Marten]

https://bugs.kde.org/show_bug.cgi?id=321684

Jonathan Marten  changed:

   What|Removed |Added

 CC||j...@keelhaul.me.uk

--- Comment #5 from Jonathan Marten  ---
Reported some time ago as bug 281530, claimed to be fixed (although it didn't
work for me).

-- 
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 321684] kmail2 embedded mail can't be opened - kmail2 reports contains not a mail

[Marc Schmitzer]

https://bugs.kde.org/show_bug.cgi?id=321684

--- Comment #4 from Marc Schmitzer  ---
Created attachment 89561
  --> https://bugs.kde.org/attachment.cgi?id=89561&action=edit
Affected mail

-- 
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 321684] kmail2 embedded mail can't be opened - kmail2 reports contains not a mail

[Marc Schmitzer]

https://bugs.kde.org/show_bug.cgi?id=321684

Marc Schmitzer  changed:

   What|Removed |Added

 CC||marc-schmit...@gmx.de

--- Comment #3 from Marc Schmitzer  ---
I think I'm hitting the same problem.

A little more detailed explanation: Spamassassin has a feature where it
generates a report email for each detected spam mail, and attaches the original
mail to the report mail.
Kmail displays the report mail just fine and indicates the attachment. Opening
the attachment with "KMail View" gives a "The file does not contain a message"
error. Saving the attachement results in a zero-byte file.
Looking at the source of the report message, the attached message is there.
I'll attach an example.

-- 
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 331267] Kontact crashed upon print

[ali.sherif10]

https://bugs.kde.org/show_bug.cgi?id=331267

ali.sheri...@yahoo.com changed:

   What|Removed |Added

 CC||ali.sheri...@yahoo.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

[kontact] [Bug 331267] Kontact crashed upon print

[ali.sherif10]

https://bugs.kde.org/show_bug.cgi?id=331267

--- Comment #2 from ali.sheri...@yahoo.com ---
Created attachment 89560
  --> https://bugs.kde.org/attachment.cgi?id=89560&action=edit
New crash information added by DrKonqi

kontact (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:
Kontact crashed, after I had clicked the print button.

-- Backtrace (Reduced):
#6  KMail::MessageActions::printMessage (this=0x1d42ef0, preview=) at /usr/src/debug/kdepim-4.14.2/kmail/messageactions.cpp:508
[...]
#8  0x7fc3b0c7f622 in QAction::triggered (this=this@entry=0x1b4d790,
_t1=false) at .moc/release-shared/moc_qaction.cpp:276
#9  0x7fc3b0c80fd3 in QAction::activate (this=0x1b4d790, event=) at kernel/qaction.cpp:1257
#10 0x7fc3b1033112 in QAbstractButtonPrivate::click
(this=this@entry=0x1e8a330) at widgets/qabstractbutton.cpp:530
#11 0x7fc3b103323c in QAbstractButton::mouseReleaseEvent (this=0x1d5fea0,
e=0x7fff3ed7c700) at widgets/qabstractbutton.cpp:1123

-- 
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 340664] Syncs the whole inbox,not just the changes

[abensonca]

https://bugs.kde.org/show_bug.cgi?id=340664

abenso...@gmail.com changed:

   What|Removed |Added

 CC||abenso...@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 339093] under kmail 4.14.0, mail filtering randomly stops working

[abensonca]

https://bugs.kde.org/show_bug.cgi?id=339093

abenso...@gmail.com changed:

   What|Removed |Added

 CC||abenso...@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 340019] Filters stop working randomly.

[abensonca]

https://bugs.kde.org/show_bug.cgi?id=340019

abenso...@gmail.com changed:

   What|Removed |Added

 CC||abenso...@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

[kontact] [Bug 329645] Kontact crashed

[Martin]

https://bugs.kde.org/show_bug.cgi?id=329645

Martin  changed:

   What|Removed |Added

 CC||martin.ruess...@mailbox.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

[kontact] [Bug 329645] Kontact crashed

[Martin]

https://bugs.kde.org/show_bug.cgi?id=329645

--- Comment #2 from Martin  ---
Created attachment 89554
  --> https://bugs.kde.org/attachment.cgi?id=89554&action=edit
New crash information added by DrKonqi

kontact (4.14.2) on KDE Platform 4.14.2 using Qt 4.8.6

I had some unfinished mails on my desktop left open.

-- Backtrace (Reduced):
#7  0x004034df in qDeleteAll::const_iterator>
(end=..., begin=...) at /usr/include/QtCore/qalgorithms.h:322
#8  qDeleteAll > (c=...) at
/usr/include/QtCore/qalgorithms.h:330
#9  main (argc=, argv=0x7fff9580e358) at
/chakra/desktop-testing/kdepim/src/kdepim-4.14.2/kontact/src/main.cpp:220

-- 
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 339214] Starting KMail gives message "Could not create collection trash resourceId: 3

[Stephan Wienczny]

https://bugs.kde.org/show_bug.cgi?id=339214

Stephan Wienczny  changed:

   What|Removed |Added

 CC||step...@wienczny.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

[kmail2] [Bug 323058] kmail fails on startup with message :could not create collection inbox"

[Stephan Wienczny]

https://bugs.kde.org/show_bug.cgi?id=323058

Stephan Wienczny  changed:

   What|Removed |Added

 CC||step...@wienczny.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

[kontact] [Bug 333725] Kontact crashed out of the blue

[Piotr Keplicz]

https://bugs.kde.org/show_bug.cgi?id=333725

Piotr Keplicz  changed:

   What|Removed |Added

 CC||kepl...@cmc.pl

--- Comment #3 from Piotr Keplicz  ---
Application: kontact (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-24-generic x86_64
Distribution: Ubuntu 14.10

-- Information about the crash:
- What I was doing when the application crashed:

Kontact crashed suddenly, a couple of minutes after system startup. I wasn't
doing anything  in the Kontact at the moment.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2b1ce7b8c0 (LWP 4587))]

Thread 4 (Thread 0x7f2afc9b6700 (LWP 4651)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2b17b7581d in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f2b17b75859 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f2b1428f0a5 in start_thread (arg=0x7f2afc9b6700) at
pthread_create.c:309
#4  0x7f2b1a3a084d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f2abc0b3700 (LWP 4665)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2b178b620d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f2b17ba4fd6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f2b1428f0a5 in start_thread (arg=0x7f2abc0b3700) at
pthread_create.c:309
#4  0x7f2b1a3a084d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f2aa8b99700 (LWP 4715)):
[KCrash Handler]
#6  0x7f2b11a063ae in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x7f2b119fee02 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#8  0x7f2b119ff332 in dbus_message_unref () from
/lib/x86_64-linux-gnu/libdbus-1.so.3
#9  0x7f2b197187e9 in q_dbus_message_unref (message=) at
qdbus_symbols_p.h:296
#10 ~QDBusArgumentPrivate (this=, __in_chrg=) at
qdbusargument.cpp:66
#11 QDBusArgument::~QDBusArgument (this=0x16abc30, __in_chrg=)
at qdbusargument.cpp:348
#12 0x7f2b196f565e in qMetaTypeDeleteHelper (t=0x3462840) at
../../include/QtCore/../../src/corelib/kernel/qmetatype.h:134
#13 0x7f2b1ab19143 in clear (d=0x10bb5e0) at kernel/qvariant.cpp:290
#14 0x7f2b196e4b5c in node_destruct (this=, to=0x1ce0398,
from=0x1ce0398) at ../../include/QtCore/../../src/corelib/tools/qlist.h:431
#15 free (this=, data=0x1ce0380) at
../../include/QtCore/../../src/corelib/tools/qlist.h:757
#16 QList::~QList (this=, __in_chrg=)
at ../../include/QtCore/../../src/corelib/tools/qlist.h:732
#17 0x7f2b196f8daf in QDBusMessage::~QDBusMessage (this=0x16abc30,
__in_chrg=) at qdbusmessage.cpp:537
#18 0x7f2b196f5bb6 in ~QDBusCallDeliveryEvent (this=0x31f0390,
__in_chrg=) at qdbusintegrator_p.h:93
#19 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0x31f0390,
__in_chrg=) at qdbusintegrator_p.h:93
#20 0x7f2b1aaf8f4a in QCoreApplicationPrivate::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x16ac1d0) at
kernel/qcoreapplication.cpp:1593
#21 0x7f2b1aaf93d3 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1470
#22 0x7f2b1ab22ed3 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=0x7f2aa40012e0) at
kernel/qeventdispatcher_glib.cpp:287
#24 0x7f2b13da9c5d in g_main_dispatch (context=0x7f2aa40009a0) at
/build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111
#25 g_main_context_dispatch (context=context@entry=0x7f2aa40009a0) at
/build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710
#26 0x7f2b13da9f48 in g_main_context_iterate
(context=context@entry=0x7f2aa40009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781
#27 0x7f2b13da9ffc in g_main_context_iteration (context=0x7f2aa40009a0,
may_block=1) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3842
#28 0x7f2b1ab23031 in QEventDispatcherGlib::processEvents
(this=0x7f2aa40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#29 0x7f2b1aaf44f1 in QEventLoop::processEvents
(this=this@entry=0x7f2aa8b98d20, flags=...) at kernel/qeventloop.cpp:149
#30 0x7f2b1aaf4805 in QEventLoop::exec (this=this@entry=0x7f2aa8b98d20,
flags=...) at kernel/qeventloop.cpp:204
#31 0x7f2b1a9f2c39 in QThread::exec (this=) at
thread/qthread.cpp:538
#32 0x7f2b1a9f539f in QThreadPrivate::start (arg=0x9

[kmail2] [Bug 283020] Store Kmail Tags in IMAP flags, like Thunderbird

[Erik Quaeghebeur]

https://bugs.kde.org/show_bug.cgi?id=283020

--- Comment #9 from Erik Quaeghebeur  ---
(In reply to David Alston from comment #6)
> I recognize that it may take quite a bit of coding to implement something 
> like this.

I just looked at a mail from an IMAP mailbox in the Akonadiconsole: all the
flags are there!! (In the tab ‘Internals’) The tab just to the left of it
‘Nepomuk’ (I’m on 4.12.5 still) contains the Akonadi tags. Also, the so-called
IMAP system flags (\Seen, \Answered,...), which are also in this tab, are
already exposed in such a way that KMail can get to them and modify them.

So, actually, this shouldn’t be a big coding task: in the same way the system
flags are synced, the non-system flags could be synced to Akonadi tags. (I
actually tried to solve the same issue for OfflineIMAP; see
 and the
amount of code changes needed was adding ~12 lines and modifying ~28 lines.)

I can’t seem to modify data in the ‘Internals’ tab (read-only mode?) to add a
custom flag to see if it is synced to the server; the other way around works:
flags set in Trojita get synced to Akonadi (via the IMAP server).

My question to the developers is: am I corrent in thinking this is, code-wise,
not a big issue? If so, what is holding this back most: lack of time, design
decisions (not sure if you want to map IMAP flags to Akonadi tags), something
else? What could we do to speed up implementation? (Start a small crowdfuning
campaign?) Would implementing a small Akonadi agent that does this syncing (and
which we can test) be more feasible than immediate integration into the main
IMAP agent?

-- 
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 282891] searching is severely broken (contains multiple reports)

[Erik Quaeghebeur]

https://bugs.kde.org/show_bug.cgi?id=282891

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||kdebugs@equaeghe.nospammail
   ||.net

-- 
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 340818] Tries to attach directories

[LtWorf]

https://bugs.kde.org/show_bug.cgi?id=340818

--- Comment #2 from Salvo "LtWorf" Tomaselli  ---
I type a directory name to just go in there (like I do in any other dialog) and
select the file or subdirectory from there (because I don't remember the full
path). But the moment I hit enter to open it, it will try to attach it.

-- 
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