[Akonadi] [Bug 427800] Handler exception when handling command FetchItems on connection Archive Mail Kernel ETM

[quazgar]

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

quazgar  changed:

   What|Removed |Added

 OS|FreeBSD |All

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 427800] Handler exception when handling command FetchItems on connection Archive Mail Kernel ETM

[quazgar]

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

quazgar  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||quaz...@posteo.de
 Ever confirmed|0   |1

--- Comment #2 from quazgar  ---
I can confirm this behavior.

Depending on the operation, Akonadi may also say instead:

```
org.kde.pim.akonadiserver: Error while handling command ModifyItems on
connection kontact-48271 (0x55ac6b7cfe80)
```

Versions:
  Linux: Debian Bullseye
  Kontact Version: 5.15.3 (20.08.3)
  KDE Frameworks: 5.78.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 449329] New: ENH: Filter should support full Boolean logic

[quazgar]

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

Bug ID: 449329
   Summary: ENH: Filter should support full Boolean logic
   Product: kmail2
   Version: 5.15.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

SUMMARY

Currently the mail filters only support full conjunction (AND) or disjunction
(OR) over all criteria.  The filters could become much more expressive if
nested criteria could be defined, such as `a AND (b OR c)` or even `(NOT "From
= foo") AND ("Subject = Interesting")`.

For me this would resolve use cases where for example I receive mails to
different addresses on the same mailbox, and I want to apply different filters
on some of them.

UI/UX IDEAS

Unfortunately I do not have a completely intuitive UI in mind which would be
ideal for casual and power filter users alike.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Currently 5.15.3 (20.08.3) on Debian Bullseye

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 316153] can't move or delete messages in imap inbox

[quazgar]

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

--- Comment #48 from quazgar  ---
I experience the problem in Debian Buster as well (5.9.3), setting ACLs in
akonadiconsole also worked as a workaround for me. The IMAP account in question
was one from uberspace.de.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 316153] can't move or delete messages in imap inbox

[quazgar]

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

quazgar  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---
 CC||quaz...@posteo.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 403159] Blank page on print and print preview

[quazgar]

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

quazgar  changed:

   What|Removed |Added

 CC||quaz...@posteo.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 404700] Unable to select GPG key not matching identity email

[quazgar]

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

quazgar  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||quaz...@posteo.de

--- Comment #2 from quazgar  ---
More likely, this was implemented as a feature in
https://phabricator.kde.org/T3125

Suggestion for an enhancement:

Also allow all keys matching email aliases set in the first identity tab.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

[quazgar]

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

quazgar  changed:

   What|Removed |Added

 CC||quaz...@posteo.de

--- Comment #25 from quazgar  ---
As of 5.7.3, the current state seems to be that Akonadi simply saves the tags
in the `pimitemtagrelation` table.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

[quazgar]

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

quazgar  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=405456

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 405456] Search for custom header fails with inconclusive error message

[quazgar]

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

quazgar  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=283020

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 405456] New: Search for custom header fails with inconclusive error message

[quazgar]

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

Bug ID: 405456
   Summary: Search for custom header fails with inconclusive error
message
   Product: kmail2
   Version: 5.7.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: search
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

Created attachment 118787
  --> https://bugs.kde.org/attachment.cgi?id=118787=edit
Screenshot of the error message

# SUMMARY

Trying to search (with "s") for a custom header field fails with an error
message. 

# STEPS TO REPRODUCE
1. Open search dialog (see screenshot).
2. In the "Choose or type..." field, enter your desired header, e.g.
"X-MyHeaderField".
3. In the value field, enter your desired value.
4. Press "Search" button

# OBSERVED RESULT
An error message appears: "Search failed some errors were found: 
You forgot to add conditions."

# EXPECTED RESULT
Search for messages with the expected condition.

# SOFTWARE/OS VERSIONS
Distro: Ubuntu 18.04.2 LTS
Qt: 5.9.5
KDE: 5.44.0

# ADDITIONAL INFORMATION
This would be a workaround for me until bug #283020 is implemented.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 348382] Action item flag is lost in IMAP folders

[quazgar]

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

--- Comment #4 from quazgar  ---
(In reply to Erik Quaeghebeur from comment #2)
> (In reply to quazgar from comment #0)
> > If relevant: The server is an MS Exchange mail server.
> Exchange does not support arbitrary IMAP flags, so this does not seem
> surprising. Check from another IMAP client (Trojita, Thunderbird,…) whether
> the Action flag ($TODO) is actually propagated at all (I doubt it).

I can confirm that for e.g. posteo.de it seems to work flawlessly.

> However, with Exchange, the best thing is to try out the akonadi-ews
> resource under development: https://github.com/KrissN/akonadi-ews (it may
> also be in your distribution's packages).

I tried to use that resource, but am still stuck with bug #390799 / bug
#390798, so cannot test it for the moment.  Maybe this one should depend on
#390798?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 390799] EWS resource didn't appear in list of directory

[quazgar]

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

quazgar  changed:

   What|Removed |Added

 CC||quaz...@posteo.de

--- Comment #2 from quazgar  ---
Not a duplicate IMHO, I managed to work around the referenced bug using the
manual settings from https://github.com/KrissN/akonadi-ews/issues/48, but it
still does not show up in the folder list in KMail.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 397451] New: DavGroupwareResource: Failed to parse item data for XML with error message.

[quazgar]

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

Bug ID: 397451
   Summary: DavGroupwareResource: Failed to parse item data for
XML with error message.
   Product: Akonadi
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

The CalDAV parser seems to fail when the DAV object contains just an error
message, the output by akonadi is:

parse error from icalcomponent_new_from_string. string= "\nhttp://sabredav.org/ns\;>\n 
Sabre\\DAV\\Exception\\NotFound\n 
Calendar object not found\n\n"
org.kde.pim.davresource: DavGroupwareResource::onItemFetched: Failed to parse
item data. 
"https://nextcloud.goltzsche.net/remote.php/caldav/calendars/daniel/caosdb_shared_by_henrik/1534254381.R191.ics

This just happened for me for data from a NextCloud installation:


http://sabredav.org/ns;>
  Sabre\DAV\Exception\NotFound
  Calendar object not found


Instead of failing and displaying an error in the Akonadi output, it should
maybe either ignore the exception, raise just a warning or display the included
message to the user.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395085] Signature of email with attachment is shown as invalid in Evolution

[quazgar]

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

--- Comment #2 from quazgar  ---
Could it be that the problem is on KMail's side?

- KMail does not strip trailing space.
- As per
https://gitlab.gnome.org/GNOME/evolution-data-server/issues/4#note_234216,
Evolution by default strips trailing whitespaces.

If I read https://tools.ietf.org/html/rfc3156, page 5, bullet point (4)
correctly, "any trailing whitespace MUST then be removed from the signed
material" before calculating the signature.

I am not accustomed enough with MIME messages and transfer encodings though to
tell if there is no exception to the rule here ;-)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395085] Signature of email with attachment is shown as invalid in Evolution

[quazgar]

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

--- Comment #1 from quazgar  ---
Evolution bug: https://gitlab.gnome.org/GNOME/evolution/issues/11

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395085] New: Signature of email with attachment is shown as invalid in Evolution

[quazgar]

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

Bug ID: 395085
   Summary: Signature of email with attachment is shown as invalid
in Evolution
   Product: kmail2
   Version: 5.7.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

Created attachment 113114
  --> https://bugs.kde.org/attachment.cgi?id=113114=edit
Sample mail, seems to work for KMail, fails for Evolution.

When sending an email with an attachment, its signature is shown as invalid by
Evolution.

See the attached example mbox file.  It can be opened in KMail and KMail shows
a valid signature, but when opened with evolution, the signature is said to be
wrong.  This behavior will also be filed as a bug for Evolution, but I want to
make sure that there are no open MIME-related issues with the message
composition.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 390166] Folder list should show number of unread mails for top-level folder and children separately

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 390166] Folder list should show number of unread mails for top-level folder and children separately

[quazgar]

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

--- Comment #2 from quazgar <quaz...@posteo.de> ---
Created attachment 110711
  --> https://bugs.kde.org/attachment.cgi?id=110711=edit
Unread mails

(In reply to Laurent Montel from comment #1)
> It was not changed.
> Please add a screenshot 

Hi,

it seems this was a misunderstanding by me when setting up KMail on a new
machine.  The old behavior is actually still there, so NOTABUG, I simply did
not find it at first because I had the extra "Unread" column enabled.  It might
help to add a similar feature there as well, though that might then be a
different bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 390166] New: Folder list should show number of unread mails for top-level folder and children separately

[quazgar]

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

Bug ID: 390166
   Summary: Folder list should show number of unread mails for
top-level folder and children separately
   Product: kmail2
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

Currently, the folder list shows the total number of unread messages for a
folder and its sub-folders:

-Debian  100

So all of the two following cases could be the case:

-Debian 100
 |--Debian KDE0
 |--Debain Users  0

or

-Debian  20
 |--Debian KDE   30
 |--Debain Users 50

or

-Debian   0
 |--Debian KDE   80
 |--Debain Users 20

It would be useful (and in earlier versions of KMail this was the case) if a
collapsed top-level folder indicated somehow the number of top-level unread
messages in addition to the overall number.  IIRC previously it was:

- "100" if there are only 100 unread top-level messages.
- "20 + 80" if there are 20 in the top-level folder and 80 messages in the
children.
- "0 + 100" if there are no top-level and 100 unread child folders messages.

This would increase the usability again since the user does not open the
top-level folder in vain but can simply extend the view in the folder tree view
to show th children first, before deciding which folder to open in the message
list.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 348103] Thousands of empty messages with duplicate headers created in accounts

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 CC||quaz...@posteo.de

--- Comment #5 from quazgar <quaz...@posteo.de> ---
I had a similar behavior just today, when accidentally enabling server-side
subscription for an Outlook IMAP server (at gwdg.de).  The only way to get rid
of the problem was to remove the IMAP account and recreate it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 374923] cannot used Ctrl-n in kontact to create new mail

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

Version|5.5.1   |5.6.3

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 374923] cannot used Ctrl-n in kontact to create new mail

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||quaz...@posteo.de
 Ever confirmed|0   |1

--- Comment #4 from quazgar <quaz...@posteo.de> ---
This bug is still valid in 5.6.3 on Debian testing (17.08.3 bundle).  Similar
to bug #235224 and probably a duplicate of bug #354941.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 354941] CTRL-N is seen as ambigous in mail and contacts plugin (not in calendar)

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 CC||quaz...@posteo.de
Version|5.5.2   |5.6.3
   Platform|Kubuntu Packages|Debian testing

--- Comment #5 from quazgar <quaz...@posteo.de> ---
This bug is still valid in 5.6.3 on Debian testing (17.08.3 bundle).  Similar
to bug #235224.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 235224] Kontact: Please remove Ctrl+N shortcut from File menu -> New message... (error about ambiguous shortcurts)

[quazgar]

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

--- Comment #3 from quazgar <quaz...@posteo.de> ---
(In reply to quazgar from comment #2)
> This bug is still valid in 5.6.3 on Debian testing (17.08.3 bundle).  Even
> though KNode is not even installed (which makes it impossible to remove the
> shortcut there).

Actually it happens in KMail here...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 235224] Kontact: Please remove Ctrl+N shortcut from File menu -> New message... (error about ambiguous shortcurts)

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 CC||quaz...@posteo.de
Version|4.4.2   |5.6.3
   Platform|Gentoo Packages |Debian testing

--- Comment #2 from quazgar <quaz...@posteo.de> ---
This bug is still valid in 5.6.3 on Debian testing (17.08.3 bundle).  Even
though KNode is not even installed (which makes it impossible to remove the
shortcut there).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 389638] When moving imported maildir folders, before they are completely written to disk, they arrive empty, losing all the mails.

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

  Component|composer|commands and actions
 Ever confirmed|0   |1
Summary|When moving several maildir |When moving imported
   |folders, some arrive empty, |maildir folders, before
   |losing all the mails.   |they are completely written
   ||to disk, they arrive empty,
   ||losing all the mails.
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from quazgar <quaz...@posteo.de> ---
OK, I think I can fully reproduce the problem now and have found its reason:

Steps to reproduce
--
1) Create a KMail archive, it should contain a folder ("somedir") and some
subfolders and sufficiently many emails (in my case, a total of 700 emails was
enough).
2) Create a target maildir directory, e.g. "target"
3) Import the archive into a folder, e.g. "imported"
4) Shortly after the import has finished, move the imported folders, e.g.
"imported/somedir" to "target".

Expected result
---
1) The moved folders should have an identical content compared to the archive's
source.

Actual result
-
1) Some, or all, of the emails are missing.

Workaround
--
1) Wait until the folder structure on the file system exists and has been
populated.  This can be checked e.g. by watching the output of:

find ~/.local/share/akonadi_maildir_resource_0/.imported.directory/ -type f |
wc -l

2) Only when the number looks reasonable and does not change any more, start
moving the folder.


Notes
-
Since in this case, the bug only happens after importing mails, maybe the
severity can be downgraded, because no data is lost as long as the archive is
still available and the problem has been noticed soon enough.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 389638] When moving several maildir folders, some arrive empty, losing all the mails.

[quazgar]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

  Component|commands and actions|composer

--- Comment #1 from quazgar <quaz...@posteo.de> ---
A small addition: I was able to reproduce this by moving a single folder (which
contains subfolders) to a different location in the same maildir structure:

-+-A
 |
 +-B
   +-C
 +-D

Here I was trying to move C into A so that the structure would look like this:

-+-A
 | +-C
 |   +-D
 |
 +-B

In the folder overview D looked as if it had still a large number of unread
mails, but when I entered the folder, the number of unread mails was reset to
zero and the folder was empty.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 389638] New: When moving several maildir folders, some arrive empty, losing all the mails.

[quazgar]

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

Bug ID: 389638
   Summary: When moving several maildir folders, some arrive
empty, losing all the mails.
   Product: kmail2
   Version: 5.6.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

I recently tried to migrate a large maildir structure from one machine to
another, by creating an archive first on one machine and then importing the
archive on the other.  The import, into a temporary "imported" folder, seemed
to have worked alright.

I then tried to move the imported folders to their new destination.  This
worked fine for the first two folders, so I got a bit carefree and
drag-n-dropped several folders to their new locations before the old moving
operation had finished.

A few hours later I checked back in and found that the process seemed to have
finished, but some of the subfolders (at their new locations) were completely
empty, the messages were gone, seemingly both from the database (not showing up
in KMail) and from the file system (the respective maildir folders were empty).

Not sure if this is related to bug #322697.

KMail: 5.6.3
Qt: 5.9.2
KDE Frameworks: 5.37.0
(all installed as 17.08.3 on Debian testing)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 380307] IMAP fails against Exchange 2016

[quazgar]

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

--- Comment #6 from quazgar <quaz...@posteo.de> ---
Some akonadi output during a lookup from the server.  There was one message
which I marked as spam before but which was now seemingly fetched again and
moved as a "ghost" message into my (local) spam folder, where it now sits
alongside the original message.  Maybe that was also the cause of the previous
filter problems, that moving messages to other folders worked locally but the
messages were not removed remotely, and then fetched from the server again and
again?

Anyways, here's the output:

log_imapresource: Detected inconsistency in local cache, we're missing some
messages. Server:  24  Local:
0
log_imapresource: Refetching complete mailbox.
log_imapresource: Detected inconsistency in local cache, we're missing some
messages. Server:  246  Local:  244
log_imapresource: Refetching complete mailbox.
Tokenizer Warning: attribute ends with "*", but value is a
quoted-string!Chopping away "*".
Tokenizer Warning: attribute ends with "*", but value is a
quoted-string!Chopping away "*".
Tokenizer Warning: attribute ends with "*", but value is a
quoted-string!Chopping away "*".
Tokenizer Warning: attribute ends with "*", but value is a
quoted-string!Chopping away "*".
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&,
bool) Akonadi::Server::NotificationManager(0x55e38d81cdc0)
"akonadi_imap_resource_0
_2924_GURJ2K" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&,
bool) Akonadi::Server::NotificationManager(0x55e38d81cdc0)
"akonadi_imap_resource_0
_2924_yc7Rnz" false
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/akonadi_imap_resource_0_2924_GURJ2K"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/akonadi_imap_resource_0_2924_yc7Rnz"
Tokenizer Warning: attribute ends with "*", but value is a
quoted-string!Chopping away "*".
Tokenizer Warning: attribute ends with "*", but value is a
quoted-string!Chopping away "*".
org.kde.akonadi.ETM: Subtree:  387 QSet(387)
org.kde.akonadi.ETM: Subtree:  393 QSet(407, 406, 405, 404, 411, 410, 409, 408,
413, 412, 395, 394, 393, 399, 398, 397, 396, 403, 402, 401, 400)
org.kde.akonadi.ETM: Subtree:  4 QSet(173, 172, 345, 344, 322, 372, 381, 380,
353, 147, 146, 145, 367, 144, 366, 151, 150, 149, 148, 155, 154, 153, 152, 159,
157,
156, 131, 135, 134, 287, 133, 286, 132, 7, 285, 139, 6, 137, 4, 136, 11, 143,
142, 9, 140, 179, 178, 13, 177, 12, 176, 163, 162, 161, 160, 313, 167, 166,
165, 164,
 171, 170, 290, 169, 289, 168, 288, 175, 174)
org.kde.akonadi.ETM: Fetch job took  8375 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 91
org.kde.akonadi.ETM: first fetched collection: "Local Folders"
org.kde.akonadi.ETM: Subtree:  387 QSet(387)
org.kde.akonadi.ETM: Subtree:  393 QSet(407, 406, 405, 404, 411, 410, 409, 408,
413, 412, 395, 394, 393, 399, 398, 397, 396, 403, 402, 401, 400)
org.kde.akonadi.ETM: Subtree:  4 QSet(173, 172, 345, 344, 322, 372, 381, 380,
353, 147, 146, 145, 367, 144, 366, 151, 150, 149, 148, 155, 154, 153, 152, 159,
157,
156, 131, 135, 134, 287, 133, 286, 132, 7, 285, 139, 6, 137, 4, 136, 11, 143,
142, 9, 140, 179, 178, 13, 177, 12, 176, 163, 162, 161, 160, 313, 167, 166,
165, 164,
 171, 170, 290, 169, 289, 168, 288, 175, 174)
org.kde.akonadi.ETM: Fetch job took  8394 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 91
org.kde.akonadi.ETM: first fetched collection: "Local Folders"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
log_kimap: We asked for UID but the server didn't give it back, resultingFlags
not stored.
Database "akonadi" opened using driver "QMYSQL"
false
Shutting down "/subscriber/akonadi_imap_resource_0_2924_GURJ2K" ...
Shutting down "/subscriber/akonadi_imap_resour

[Akonadi] [Bug 380307] IMAP fails against Exchange 2016

[quazgar]

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

--- Comment #5 from quazgar <quaz...@posteo.de> ---
Thank you for reminding me!

I actually had tried all the authentication methods before posting the bug
already.  Before the upgrade to Exchange 2016, the connection used to work with
SSL/TLS on port 993 and plain authentication.

One server-side change which was announced was that from this version on, the
username would no longer be the email address but of type "$domain\$user" (the
Microsoft specific user name convention), for example "gwdg\foobar".  Another
user here found out that this did not help at all, but what did help was to
replace the correct backslash by a normal slash (which is not supposed to
work).  So what worked for her was "gwdg/foobar".  Maybe that is an excessive
interpretation of the backslash as an escape character?

I also tried this variant but unfortunately ran into the problem that
KMail/Akonadi started running into an infinite loop with automatic filtering of
messages, see the attached screenshot.  I am not sure if this has to do with my
using of Thunderbird as an intermediate solution (not sure if it was connected
to the same IMAP account simultaneously or not) or if this is linked to the
original problem.  Anyways since Akonadi did not stop to duplicate these
messages, the only way for me to keep a working computer was to disable the
account in KMail and use Thunderbird for the time being.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 380307] IMAP fails against Exchange 2016

[quazgar]

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

--- Comment #4 from quazgar <quaz...@posteo.de> ---
Created attachment 106308
  --> https://bugs.kde.org/attachment.cgi?id=106308=edit
Screenshot of the duplicate messages.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 380307] New: IMAP fails against Exchange 2016

[quazgar]

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

Bug ID: 380307
   Summary: IMAP fails against Exchange 2016
   Product: Akonadi
   Version: 5.2.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: quaz...@posteo.de
CC: kdepim-bugs@kde.org, vkra...@kde.org
  Target Milestone: ---

Our mail provider (gwdg.de) just switched to MS Exchange 2016 and KMail stopped
working, it displays an authentication failure message:

  The server for account "MPI" refused the supplied username and password. Do
you want to go to the settings, have another attempt at logging in, or do
nothing?

  Login failed, server replied: A03 NO AUTHENTICATE failed.

During several retries, this is the akonadi output on the terminal:

Pass a valid window to KWallet::Wallet::openWallet().
Pass a valid window to KWallet::Wallet::openWallet().
QXcbConnection: XCB error: 3 (BadWindow), sequence: 8197, resource id:
37811015, major code: 40 (TranslateCoords), minor code: 0
Pass a valid window to KWallet::Wallet::openWallet().
log_kimap: We asked for UID but the server didn't give it back, resultingFlags
not stored.
log_kimap: We asked for UID but the server didn't give it back, resultingFlags
not stored.
akonadiagentbase_log: "Only resources can modify remote identifiers"
log_kimap: We asked for UID but the server didn't give it back, resultingFlags
not stored.
akonadiagentbase_log: "Only resources can modify remote identifiers"
akonadiagentbase_log: "Only resources can modify remote identifiers"
Pass a valid window to KWallet::Wallet::openWallet().

This is via STARTTLS on port 143.  When trying to connect directly with SSL/TLS
on port 993, the akonadi output is (this also looks like a Qt socket problem,
possibly related to
https://stackoverflow.com/questions/15213139/simple-qssl-client-server-cannot-start-handshake-on-non-plain-connection):

qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
log_kimap: Connection to server lost  0
log_imapresource: Session login cancelled
Pass a valid window to KWallet::Wallet::openWallet().

The Akonadi error popup window shows a slightly different message from the
server:

  The server for account "MPI" refused the supplied username and password. Do
you want to go to the settings, have another attempt at logging in, or do
nothing?

  Login failed, server replied: A02 NO AUTHENTICATE failed.

Any idea if this is a problem on Akonadi's side or on the server side?

I am working on a Debian Testing system:

$ akonadictl -v
Akonadi 5.2.2
$ kontact -v
kontact 5.2.3
$ kmail -v
kmail2 5.2.3

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[kontact] [Bug 380305] New: Kontact crash after unsuccerssful IMAP connection attempt

[quazgar]

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

Bug ID: 380305
   Summary: Kontact crash after unsuccerssful IMAP connection
attempt
   Product: kontact
   Version: 5.2.3
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-3-amd64 x86_64
Distribution: Debian GNU/Linux 9.0 (stretch)

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

- Unusual behavior I noticed:
I was unable to connect to the usual IMAP server, had many failed attempts to
connect to it.

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

Thread 19 (Thread 0x7f5e82a45700 (LWP 31179)):
#0  0x7f5ff16c055d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5fe2908073 in  () at
/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.375.39
#2  0x7f5fc9d41181 in pa_read () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
#3  0x7f5fca1c70be in pa_mainloop_prepare () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f5fca1c7b30 in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f5fca1c7bf0 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f5fca1d5bd9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f5fc9d702c8 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
#8  0x7f5feb626494 in start_thread (arg=0x7f5e82a45700) at
pthread_create.c:333
#9  0x7f5ff16cd93f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 18 (Thread 0x7f5f357fa700 (LWP 15500)):
#0  0x7f5fe97d6104 in g_mutex_unlock (mutex=0x7f5f18002e00) at
././glib/gthread-posix.c:1348
#1  0x7f5fe978fed0 in g_main_context_prepare
(context=context@entry=0x7f5f18002e00, priority=priority@entry=0x7f5f357f9b40)
at ././glib/gmain.c:3499
#2  0x7f5fe979091b in g_main_context_iterate
(context=context@entry=0x7f5f18002e00, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#3  0x7f5fe9790b0c in g_main_context_iteration (context=0x7f5f18002e00,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f5ff21ef06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5ff21989ca in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5ff1fc60f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5ff1fcada8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5feb626494 in start_thread (arg=0x7f5f357fa700) at
pthread_create.c:333
#9  0x7f5ff16cd93f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 17 (Thread 0x7f5f35ffb700 (LWP 15497)):
#0  0x7f5ff16c055d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5fe2908073 in  () at
/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.375.39
#2  0x7f5fe97d4d40 in read (__nbytes=16, __buf=0x7f5f35ffaa60,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#3  0x7f5fe97d4d40 in g_wakeup_acknowledge (wakeup=0x7f5f20002370) at
././glib/gwakeup.c:210
#4  0x7f5fe97904be in g_main_context_check
(context=context@entry=0x7f5f20002a00, max_priority=2147483647,
fds=fds@entry=0x7f5f20002ba0, n_fds=n_fds@entry=1) at ././glib/gmain.c:3707
#5  0x7f5fe9790994 in g_main_context_iterate
(context=context@entry=0x7f5f20002a00, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3926
#6  0x7f5fe9790b0c in g_main_context_iteration (context=0x7f5f20002a00,
may_block=1) at ././glib/gmain.c:3990
#7  0x7f5ff21ef06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5ff21989ca in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f5ff1fc60f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f5ff1fcada8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f5feb626494 in start_thread (arg=0x7f5f35ffb700) at
pthread_create.c:333
#12 0x7f5ff16cd93f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 16 (Thread 0x7f5f367fc700 (LWP 15496)):
#0  0x7f5ff42f073e in _dl_update_slotinfo (req_modid=1) at dl-tls.c:619
#1  0x7f5ff42f097c in update_get_addr (ti=0x7f5ff23e5788) at dl-tls.c:802
#2  0x7f5ff1fc9c36 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f5ff21ee931 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5fe97903f9 in 

[kontact] [Bug 373129] New: Kontact crashed when closing after tryong to accept an ics invitation

[quazgar]

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

Bug ID: 373129
   Summary: Kontact crashed when closing after tryong to accept an
ics invitation
   Product: kontact
   Version: 5.2.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
I received an ics invitation via KMail and clicked on the "Accept" button in
the mail window. Nothing seemd to happen, so I switched to the calendar tab,
but the event had not appeared there. After that I switched back to the KMail
tab, then closed Kontact to restart Akonadi (this sometimes helped with other
problems before). Upon closing Kontact, I received the KDE crash report.

When trying again (after restarting Akonadi), accepting the ics event worked on
the second attempt.

-- 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 0x7f3fcaffd940 (LWP 20989))]

Thread 17 (Thread 0x7f3efe876700 (LWP 21691)):
#0  0x7fff9aff6c33 in clock_gettime ()
#1  0x7f3fe174b886 in __GI___clock_gettime (clock_id=clock_id@entry=1,
tp=tp@entry=0x7f3efe8759e0) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f3fe20e0001 in qt_gettime() (ts=0x7f3efe8759e0, clock=) at tools/qelapsedtimer_unix.cpp:109
#3  0x7f3fe20e0001 in qt_gettime() (frac=,
sec=) at tools/qelapsedtimer_unix.cpp:164
#4  0x7f3fe20e0001 in qt_gettime() () at tools/qelapsedtimer_unix.cpp:173
#5  0x7f3fe2268379 in QTimerInfoList::updateCurrentTime()
(this=this@entry=0x7f3ef4002cd0) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f3fe2268925 in QTimerInfoList::timerWait(timespec&)
(this=0x7f3ef4002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f3fe2269cce in timerSourcePrepare(GSource*, gint*)
(timeout=0x7f3efe875ab4, src=) at
kernel/qeventdispatcher_glib.cpp:132
#8  0x7f3fe2269cce in timerSourcePrepare(GSource*, gint*)
(source=, timeout=timeout@entry=0x7f3efe875ab4) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x7f3fd9a27edd in g_main_context_prepare
(context=context@entry=0x7f3ef40009b0, priority=priority@entry=0x7f3efe875b40)
at ././glib/gmain.c:3501
#10 0x7f3fd9a2891b in g_main_context_iterate
(context=context@entry=0x7f3ef40009b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#11 0x7f3fd9a28b0c in g_main_context_iteration (context=0x7f3ef40009b0,
may_block=may_block@entry=1) at ././glib/gmain.c:3990
#12 0x7f3fe226a6fb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3ef40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7f3fe221407a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f3efe875c80, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#14 0x7f3fe20360d3 in QThread::exec() (this=) at
thread/qthread.cpp:507
#15 0x7f3fe203ad88 in QThreadPrivate::start(void*) (arg=0x55a499096370) at
thread/qthread_unix.cpp:368
#16 0x7f3fdb697464 in start_thread (arg=0x7f3efe876700) at
pthread_create.c:333
#17 0x7f3fe173e9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f3eff077700 (LWP 21689)):
#0  0x7f3fdb69ff9c in __lll_lock_wait () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7f3fdb699c36 in __GI___pthread_mutex_lock (mutex=0x7f3fdaeec2b0) at
../nptl/pthread_mutex_lock.c:115
#2  0x7f3fdac6881c in  () at /usr/lib/x86_64-linux-gnu/libGL.so.1
#3  0x7f3fdac6d741 in  () at /usr/lib/x86_64-linux-gnu/libGL.so.1
#4  0x7f3fdac6dc58 in  () at /usr/lib/x86_64-linux-gnu/libGL.so.1
#5  0x7f3fd2ba9102 in  () at
/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.367.57
#6  0x7f3fd9a6cc40 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f3eff076a60, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#7  0x7f3fd9a6cc40 in g_wakeup_acknowledge (wakeup=0x7f3ef8002730) at
././glib/gwakeup.c:210
#8  0x7f3fd9a284be in g_main_context_check
(context=context@entry=0x7f3ef9b0, max_priority=2147483647,
fds=fds@entry=0x7f3ef00013c0, n_fds=n_fds@entry=1) at ././glib/gmain.c:3707
#9  0x7f3fd9a28994 in g_main_context_iterate
(context=context@entry=0x7f3ef9b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3926
#10 0x7f3fd9a28b0c in g_main_context_iteration (context=0x7f3ef9b0,
may_block=may_block@entry=1) at ././glib/gmain.c:3990
#11 0x7f3fe226a6fb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f3ef8e0, flags=...) at 

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[quazgar]

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

--- Comment #117 from quazgar <quaz...@posteo.de> ---
(In reply to quazgar from comment #116)
> Debian testing here, Kontact, KMail and Akonadi are all at version 16.04.3-2.

Sorry, that was the Debian version, of course.  Kontact says it's 5.2.3,
Akonadi is at 5.2.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[quazgar]

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

--- Comment #116 from quazgar <quaz...@posteo.de> ---
Very similar here, after rebooting the computer, filtering consistently does
nothing.  Restarting the Akonadi server always makes filtering work again.

Debian testing here, Kontact, KMail and Akonadi are all at version 16.04.3-2.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[quazgar via KDE Bugzilla]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 CC||quaz...@posteo.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 336069] Mails with "From " in attachment are not signed properly

[quazgar via KDE Bugzilla]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 CC||skna...@kde.org

--- Comment #4 from quazgar <quaz...@posteo.de> ---
I cannot reproduce it ad-hoc anymore, wasn't it fixed together with bug
#303305?  Maybe Sandro knows more?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 325224] CalDav doesn't read server items

[quazgar via KDE Bugzilla]

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

--- Comment #60 from quazgar <quaz...@posteo.de> ---
OK, there seems to be a fix in OwnCloud now:

https://github.com/owncloud/calendar/issues/706
https://github.com/owncloud/calendar/pull/707

Still, would it be possible to make the ics file parser "more clever"?  Like
saying "OK, there is a property 

PRODID:-//ownCloud calendar v1.2.2

or similar, so let's just assume the VERSION property is missing but would be
something reasonable such as 2.0 or whatever."

This would be an ugly workaround but it would help people affected by buggy
CalDAV servers.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 325224] CalDav doesn't read server items

[quazgar via KDE Bugzilla]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 CC||quaz...@posteo.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 360910] KMail shows PGP/MIME encrypted content as attachment, does not offer to decrypt.

[quazgar via KDE Bugzilla]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

 CC||skna...@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 360910] New: KMail shows PGP/MIME encrypted content as attachment, does not offer to decrypt.

[quazgar via KDE Bugzilla]

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

Bug ID: 360910
   Summary: KMail shows PGP/MIME encrypted content as attachment,
does not offer to decrypt.
   Product: kmail2
   Version: 4.14.10
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: quaz...@posteo.de

I am not certain if this is a regression to bug 286481 again, the symptom looks
very similar to me.

When receiving PGP/MIME encrypted mails from Apple Mail with GPGMail (in most
cases, this means mails with attachments), KMail shows the MIME parts as
attachments instead of asking to decrypt them.

The relevant message parts looks like this:

...
Content-Type: multipart/mixed;
boundary="_003_55514CDCA78D430384C5F0810DF10C7Adsmpgde_"
MIME-Version: 1.0
X-Bogosity: Ham, tests=bogofilter, spamicity=0.00, version=1.2.4


--_003_55514CDCA78D430384C5F0810DF10C7Adsmpgde_
Content-Type: text/plain; charset="us-ascii"


--_003_55514CDCA78D430384C5F0810DF10C7Adsmpgde_
Content-Type: application/pgp-encrypted;
name="PGPMIME Versions Identification"
Content-Description: PGP/MIME Versions Identification
Content-Disposition: attachment; filename="PGPMIME Versions Identification";
size=77; creation-date="Tue, 22 Mar 2016 16:09:18 GMT";
modification-date="Tue, 22 Mar 2016 16:09:18 GMT"
Content-ID: 
Content-Transfer-Encoding: base64

VmVyc2lvbjogMQ0NCg==

--_003_55514CDCA78D430384C5F0810DF10C7Adsmpgde_
Content-Type: application/octet-stream; name="encrypted.asc"
Content-Description: OpenPGP encrypted message.asc
Content-Disposition: attachment; filename="encrypted.asc"; size=3183;
creation-date="Tue, 22 Mar 2016 16:09:18 GMT";
modification-date="Tue, 22 Mar 2016 16:09:18 GMT"
Content-ID: <58a712e65ab1824ab726904a64491...@um.gwdg.de>
Content-Transfer-Encoding: base64

LS0tLS1CRUdJTiBQR1AgTUVTU0FHRS0tLS0tDQpDb21tZW50OiBHUEdUb29scyAtIGh0dHBzOi8v
Z3BndG9vbHMub3JnDQoNCmhRSU1BK1Yrc2NWMjZLanRBUS8vVFUvamtkMG0zVzRDRDJmdjd4NGJu
...
RjdnPT0NCj0yRUlaDQotLS0tLUVORCBQR1AgTUVTU0FHRS0tLS0tDQo=

--_003_55514CDCA78D430384C5F0810DF10C7Adsmpgde_--

The full message is available as well, if necessary.

Reproducible: Always

Steps to Reproduce:
Get PGP/MIME encrypted message from Apple Mail.

Actual Results:  
Does not decrypt message.

Expected Results:  
Should decrypt message.

If the file "encrypted.asc" is saved to disc and decrypted manually, it can be
opened by KMail as a separate message.

-- 
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 357179] Moving an email to a collection without remote ID keeps copy in old collection

[quazgar via KDE Bugzilla]

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

quazgar <quaz...@posteo.de> changed:

   What|Removed |Added

Summary|Email remains in inbox  |Moving an email to a
   |after moving it to a folder |collection without remote
   ||ID keeps copy in old
   ||collection

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