[Akonadi] [Bug 386010] KMail2 fails to archive folder

2020-01-27 Thread Thorsten Otto
https://bugs.kde.org/show_bug.cgi?id=386010

--- Comment #5 from Thorsten Otto  ---
And why did nobody ask for missing information 2 years ago?

And you still don't get the point. Its not about why some mail cannot be
retrieved. Its about that the archiving process is completely aborted. That
makes it impossible to get at least some kind of backup.

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

[Akonadi] [Bug 386010] KMail2 fails to archive folder

2020-01-26 Thread Thorsten Otto
https://bugs.kde.org/show_bug.cgi?id=386010

--- Comment #3 from Thorsten Otto  ---
As already noted, in the GUI i don't get any hint about which message was
involved. IIRC it had something to do with duplicate mails, and one of them
being rejected. All i can see in the journal log is:

ItemRetrievalJob for request 0x7f20c007f210 finished with error: "Unable to
retrieve item from resource: [LRCONFLICT] Resource akonadi_maildir_resource_0
tries to modify item 13106 () (in collection 17) with dirty payload, aborting
STORE.

But that is not the main problem. I could live with the fact that single mails
would be skipped during archiving, especially if they are really duplicates.
But i cannot live with the fact that the whole archiving process is aborted,
leaving a truncated & damaged archive behind.

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

[kmail2] [Bug 416754] Annoying complaints about external references

2020-01-25 Thread Thorsten Otto
https://bugs.kde.org/show_bug.cgi?id=416754

--- Comment #1 from Thorsten Otto  ---
Created attachment 125402
  --> https://bugs.kde.org/attachment.cgi?id=125402=edit
Original mail contents

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

[kmail2] [Bug 416754] New: Annoying complaints about external references

2020-01-25 Thread Thorsten Otto
https://bugs.kde.org/show_bug.cgi?id=416754

Bug ID: 416754
   Summary: Annoying complaints about external references
   Product: kmail2
   Version: 5.13.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: ad...@tho-otto.de
  Target Milestone: ---

Created attachment 125401
  --> https://bugs.kde.org/attachment.cgi?id=125401=edit
Screenshot of displayed mail

Since quite some time, KMail complains about external references in HTMl mails,
even if allowed to open them, and even if there aren't any (see attached
screenshot)

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

[Akonadi] [Bug 386010] KMail2 fails to archive folder

2020-01-25 Thread Thorsten Otto
https://bugs.kde.org/show_bug.cgi?id=386010

--- Comment #1 from Thorsten Otto  ---
Reported more than 2 years ago, the bug still persists, and no comment at all?

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

[Akonadi] [Bug 386010] New: KMail2 fails to archive folder

2017-10-21 Thread Thorsten Otto
https://bugs.kde.org/show_bug.cgi?id=386010

Bug ID: 386010
   Summary: KMail2 fails to archive folder
   Product: Akonadi
   Version: 5.6.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Archive Mail Agent
  Assignee: kdepim-bugs@kde.org
  Reporter: ad...@tho-otto.de
  Target Milestone: ---

While trying to archive a folder within KMail2, i get an error message:

Failed to archive the folder 'xxx'. Downloading a message in folder 'xxx'
failed.

i'm not complaining about why that happens, but i'm complaining about the
behaviour of KMail2 here. Firstly, aborting the whole operation only because a
single message could not be accessed is absolutely catastrophic for a feature
that  is primarly used to backup mails, or to transfer them to a different
location. Aborting that renders the whole folder unusable. Secondly, it does
not give *any* hint about which message could not be accessed. Maybe the
problem could be solved by just deleting that single message, but i get no clue
which one.

It would be nice it that error behaviour could be improved.

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