Web lists-archives.com

Re: [kde] Kmail duplicates and Akonadi

On Sunday, February 15, 2015 01:57:11 AM Duncan wrote:
> Martin Koller posted on Sat, 14 Feb 2015 10:33:59 +0100 as excerpted:
> > On Wednesday 28 January 2015 16:53:11 Peter wrote:
> >> One of the KMail folders is showing 407 emails, yet on the disk
> >> there are only 199 files for that folder. Is this just Akonadi not
> >> being in sync with KMail. How do I force Akonadi to use what is on
> >> disk, not what it "thinks" is there please ?
> >> 
> >> I know there is a 'Remove Duplicate messages' option on the
> >> 'Folder', but I saw numerous posts that it doesn't work 100%.
> > 
> > I assume this is the same akonadi bug I still hunt ...
> > see also https://bugs.kde.org/show_bug.cgi?id=283682
> > 
> > A workaround might be
> > https://bugs.kde.org/show_bug.cgi?id=283682#c118
> FWIW...
> Back in the kde 4.7 era, when akonadized kmail was still new, I lost
> one too many emails.  Sure I could have reset akonadi and likely
> recovered the missing email, as I had before, but I suddenly found
> myself wondering:
> "Why is this even /necessary/.  Email is *NOT* rocket science, and has
> been around for quite some time at this point.  There are lots of
> reliable email clients that "just work", as indeed, kmail has for me,
> for the nearly a decade since I switched from MS in the kde2 era,
> before this stupid akonadization messed with something that WAS 'just
> working'.
> "Indeed, why am I tolerating this AT ALL, instead of demanding an email
> client that can actually FUNCTION as a reliable email client?"
> And simple as that, I decided I was NOT tolerating it, and began a
> hasty search for an appropriate replacement.
> I found claws-mail.  While there was a bit of pain doing the
> conversion, I haven't looked back.  Best of all, because a major
> usage-point feature of claws-mail is that it can be extended via user
> scripts, and the claws- devs would lose both most of their user base
> and arguably the primary reason for claws-mail's existence if they
> were to decide to go to some database and break all those user
> scripts, claws-mail is extremely unlikely to go the way of akonadified
> kmail.  And if it does, there's both original sylpheed from which
> claws forked, which uses the same mh-dir single-file-per-message
> format, and there's other clients that use it, including mutt, where
> that's an option, as well.
> Other former kmail users now run evolution or mozilla thunderbird.  Tho
> they both use databases (altho their database usage is considerably
> more mature than akonadi), and I wanted to stay away from that, so
> those weren't good options for me.  But claws-mail was! =:^)
> Ironically, back in 2001/2002 when I first switched from MS and ended
> up on kmail, #2 on my list was the then sylpheed-claws, which later
> became claws-mail.  Had I picked it way back then, I'd have not had to
> bother trying to convert from kmail when I did, as I'd have been on
> sylpheed- claws, now claws-mail, all along.

I too have not been impressed with akonadi and its use of mysql, for what 
I have not deduced but it does seem like needless complexity that could 
become an albatros all too easily.  Others are on record as having 
suffered, sometimes greatly but with much newer versions of kmail than the 
1.13.7 in use here ATM.

I asked how to import, from kmail into claws, what, a year ago?  And 
didn't get very encouraging discussion so I did not pursue it.

I am now on debian wheezy due to a drive failure, and while in the process 
of bringing kmail back to life, I found a way to do it.  Cumbersome, but 
it works and I converted nearly 8.5Gb of mailfiles to maildir, starting 
with the smallest and cuminating in a 5.1 Gb mailfile for one of my kmail 
folders into maildir format which now accesses in perhaps 1/2 the time 
that the mailfile used finding (or appending) a new message.

Now I find in the wheezy repos that claws is mostly 3.8.1-2.  Is this new 
enough to be usable, or should I pull a tarball and build it?  That would 
be discouraging when its claws that I want to learn how to use as opposed 
to trying to figure out all the options I'd need to feed ./configure just 
to get started on building it.  From the looks of the deb listings, 
something I would have to do 30+ times to get it all.

I intend to keep on using all my fetch recipes that deliver a somewhat 
cleaned up stream of mail to /var/mail/gene, so claws needs only to grab 
its incoming from /var/mail/gene in the final config, but while bringing 
it up on a live system, will likely be using some other name until such 
time as its working 100%, if I can convince procmail to write a copy to 
both names.

However, for that to work correctly, claws needs to respond, like kmail 
does, to a message on a dbus port.  But at the time I asked, dbus was not 

Can I assume that this version 3.8.1-2 of claws now has dbus support?

Or is there some other way I can send it a "go get the mail" command from 
a bash script?

Send transport here is simple smtp, direct access to my account on the 
mail server.

Is there anything I need to be aware of up front in such an email agent 

Thanks Duncan and all.
Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.