[kontact] [Bug 409293] FEATURE REQUEST: Easily backup/export Kontact data (kmail, calendar, contacts, etc.) for import/restoration on another PC (or a restored PC).

Jesse DuBord bugzilla_noreply at kde.org
Thu Jul 4 07:17:46 BST 2019


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

--- Comment #14 from Jesse DuBord <jesse.dubord at gmail.com> ---
(In reply to Laurent Montel from comment #13)
> (In reply to Jesse DuBord from comment #11)
> > (In reply to Laurent Montel from comment #10)
> > > (In reply to Jesse DuBord from comment #9)
> > > > > Indeed but akonadi doesn't allow it.
> > > > > We can't duplicate it directly we must to recreate it.
> > > > > I fixed a lot of bug for reducing to ask this info but it's not possible to
> > > > > reduce all.
> > > > 
> > > > So what is the expected behavior from the developer's end. When importing a
> > > > compressed file, and when it says "please choose a folder" for specified
> > > > email folder, but no folder exists, what are you expecting us to do?
> > > 
> > > By default you have a folder, if you don't have default inbox/outbox etc
> > > it's a bug :)
> > 
> > 1. So you're expecting users to assign their Gmail (IMAP) folders to the
> > local folder, when the default behavior when Kontact adds a new account is
> > to create a new IMAP folder scheme?
> 
> Why ???? it's an imap account => when we will sync resource it will create
> folders...
> 
> > 
> > 2. What if I have multiple email addresses I manage with Kmail, not just
> > one? I have my personal one, and my business one. How am I expected to
> > import both?
> 
> What is the problem ? When you export them you export all emails/accounts.
> 
> 
> > 
> > 3. If Akonadi has the ability to create folders upon a new account creation,
> > why can't the same processes be used when importing accounts?
> 
> I don't understand your problem here ? 
> 
> 
> > 
> > I feel there are solutions to this that aren't implemented
> 
> Really ?:) good :)
> 
> , so I'm
> > re-opening this bug. I greatly appreciate Kontact/Kmail as a product and all
> > of the hard work you're doing. There is a solution that can easily satisfy
> > the end-user experience, I feel we just need to find the right one to get
> > there. As of right now the implementation simply doesn't work with the pim
> > setting exporter, specifically during import of the data. Needing to specify
> > folders instead of a more straight-forward import approach (e.g. "Oh, this
> > is how it was set up on your source version of Kontact? Okay, we'll set it
> > up just like it was using the export file you provided". Simple by default,
> > powerful when needed, right? IMO, simplicity should be the goal of the
> > importing process.
> > 
> > It's less time for me to simply add the accounts manually than to use a tool
> > that seems to offer a quicker and simpler set-up experience.

So I want to help be a part of the solution. What will help resolve this
matter, effectively?

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


More information about the Kdepim-bugs mailing list