SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm doing a new current install. I've been a Thunderbird user. I'm wondering, though, if it's worth the trouble to try to get KMail working. Any specific advantages over Thunderbird?
Now, I have never actually managed to get KMail to work. Any version, on any distribution. Last time I tried, as soon as I clicked "Finish" on the automatic account setup, the machine began to beep rapidly as many, many, instances of that config routine kept opening.
Is there a trick? Or is KMail one of those things to be avoided forever?
I'm using IMAP on FastMail and won't be migrating any backups.
While in Arch(linux) I used kmail for a while - found the 'visual' part of setting it up rather confusing, but it generally worked ok - apart from some occasional hiccups. Also tried evolution which really was my favourite until I left Arch.
Now I'm an alltime thunderbird user - it 'just works' ... I certainly wouldn't leave it for kmail.
Some KDE apps like K3B, Dolphin or Gwenview are really fine. Others - like KMail or KTorrent - definitely have some Rube Goldberg touch to them. I'm mainly an Xfce guy, and I use Thunderbird for my mail. Most KDE users I know also use Thunderbird.
Kmail has evolved into a full blown bells and whistles database and calander scheduler combined into a humongous Email application that makes Rube Goldberg devices a tad simplistic. And it's been rumored it may even brew your morning coffee.
Joking aside, in it's earlier incarnations in KDE3 and up to KDE 4.5, Kmail was useful as a simple email POP3 client. Unfortunately, Kmail has become a political hot potato amidst KDE developers to justify the heavy use of multiple databases running all the time in a desktop.
From my own experience, since KDE 4.8, setting up kmail has been a hit or miss affair. One must ensure Akonadi, the various KDE calenders and Kwallet setups are set up and synced just right for the thing to work.
For low powered hardware and simpler desktop setups, that won't do. For simplified KDE desktop setups, where one minimizes or turns off Kwallet and the Akonadi Nepomuk and Strigi databases, Kmail won't function.
Since then, I've abandoned it for other email clients. Thunderbird, Seamonkey are one choice. My favorite is Claws email from the wonderful folks at Slackbuilds (Thank you Slackbuild volunteers!)
Configuring kmail can be potentially confusing. There is interaction between Accounts and Identities, particularly with SMTP and transports. When the transport layer is not configured correctly for each identity, kmail uses the default transport. That means users with multiple accounts will send emails from the same transport, which is not what most users want, and is potentially embarrassing. Not a bug, but just be meticulous with configuring kmail.
Whereas kmail1 allowed storing passwords in the rc file as encrypted text, in kmail2 all users are required to use kwallet. There is no option otherwise except to reenter passwords every time kmail is started.
All KDE PIM apps use the akonadi framework. While a benefit to certain users, that backend is not needed or wanted by many users who have only basic email requirements. The akonadi framework duplicates all emails for its cache, which is a waste of space since emails are clear text and easily searchable.
The akonadi framework will fetch emails when kmail is not running. There is an option in kmail to disable that option, but is not obvious to new users.
Although akonadi can be configured not to start when starting KDE, starting any akonadi-enabled PIM app starts the akonadi service. Akonadi-enabled apps will not run when akonadi is not installed.
Unlike nepomuk indexing, which is largely now tamed and easily disabled by users not wanting that service, akonadi is not negotiable.
Lastly, kmail2 remains mildly buggy and incomplete. Check the KDE bug tracker and KDE forum.
That said, I use kmail1 from the Trinity Desktop Environment. Mostly I use Trinity as my desktop, but when I use KDE4 I use wrapper scripts for Trinity PIM apps so I do not have to use akonadi and KDE PIM apps.
I used Kmail for a short while but wasn't very impressed with it. Thunderbird works quite well and setting up my email account took only a few seconds. It retrieved the proper POP3 settings from it's database and did all the work for me.
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
I use both here. Generally I find that Kmail just works without any specific hoops to jump through and had been my e-mail agent of choice since KDE2. But I do use Thunderbird simply for it's Exquilla plugin. As soon as Kmail offers the ability to attach to M$Outlook server used at work, then TBird will have to go.