Re: [kde] exporting from kmail (Was: Kmail2/Akonadi issue on FreeBSD.)

2011-11-29 Thread gene heskett
On Wednesday, November 30, 2011 12:52:24 AM Duncan did opine:

> gene heskett posted on Tue, 29 Nov 2011 23:01:23 -0500 as excerpted:
> > I may have hit what is almost a show-stopper with claws.  There
> > appears, from the .pdf of the docs I found, no way to have another
> > script send it a check mail command.  And while I did find an
> > auto-check option in the preferences menu, it doesn't read as doing
> > what I need it to do, or the docs maybe are a bit old?  kmail from
> > 4.6.5, even from the 3.5.0+, has had a dbus socket that works very
> > well indeed using this line from my ~/bin/mailwatcher script:
> > Cmd define (word wrapped):
> > Cmd="/usr/lib/qt4/bin/qdbus org.kde.kmail /KMail
> > org.kde.kmail.kmail.checkMail"
> > 
> > Invocation later in the script after having verified that kmail is
> > indeed running and there is new mail in /var/spool/mail/gene:
> > $cmd
> > 
> > Is this dbus port indeed on the missing list?
> 
> I'm not aware of a dbus command for it -- that doesn't mean it doesn't
> exist, I just never looked for it, but there's definitely a scripted
> solution possible, as claws, like many mh-format mail clients, is
> designed with exactly that sort of scripted extensibility in mind.
> 
> There's one way that I know for sure of, because I used it after I ran
> the import script as described in an earlier post.  But that's not ideal
> for this particular situation, which as I said I've never looked into,
> so I'd rather go looking and give you a better answer later, than to
> give you this suboptimal solution now.
> 
> But as I said, I know it's possible, both because claws was designed for
> precisely this sort of extensibility and because I happen to know an
> indirect way of doing it already, based on what I have done.

Thanks Duncan, now I have something to look forward to.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: 
Beauty?  What's that?
 -- Larry Wall in <199710221937.maa25...@wall.org>
___
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.


Re: [kde] exporting from kmail (Was: Kmail2/Akonadi issue on FreeBSD.)

2011-11-29 Thread Duncan
gene heskett posted on Tue, 29 Nov 2011 23:01:23 -0500 as excerpted:

> I may have hit what is almost a show-stopper with claws.  There appears,
> from the .pdf of the docs I found, no way to have another script send it
> a check mail command.  And while I did find an auto-check option in the
> preferences menu, it doesn't read as doing what I need it to do, or the
> docs maybe are a bit old?  kmail from 4.6.5, even from the 3.5.0+, has
> had a dbus socket that works very well indeed using this line from my
> ~/bin/mailwatcher script:
> Cmd define (word wrapped):
> Cmd="/usr/lib/qt4/bin/qdbus org.kde.kmail /KMail
> org.kde.kmail.kmail.checkMail"
> 
> Invocation later in the script after having verified that kmail is
> indeed running and there is new mail in /var/spool/mail/gene:
> $cmd
> 
> Is this dbus port indeed on the missing list?

I'm not aware of a dbus command for it -- that doesn't mean it doesn't 
exist, I just never looked for it, but there's definitely a scripted 
solution possible, as claws, like many mh-format mail clients, is 
designed with exactly that sort of scripted extensibility in mind.

There's one way that I know for sure of, because I used it after I ran 
the import script as described in an earlier post.  But that's not ideal 
for this particular situation, which as I said I've never looked into, so 
I'd rather go looking and give you a better answer later, than to give 
you this suboptimal solution now.

But as I said, I know it's possible, both because claws was designed for 
precisely this sort of extensibility and because I happen to know an 
indirect way of doing it already, based on what I have done.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

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


Re: [kde] exporting from kmail (Was: Kmail2/Akonadi issue on FreeBSD.)

2011-11-29 Thread Duncan
gene heskett posted on Tue, 29 Nov 2011 22:01:31 -0500 as excerpted:

> It appears the mutt script can do it, one dir at a time, but I should
> setup claws's mail filtering to match the kmail folder sorter, then pick
> a time and do them all.

That's pretty much what I did.  I have about 50 filters so it wasn't 
easy, but I did it.

If you have a lot of filters and would prefer typing it into a config 
file directly, rather than setting them up one by one in the GUI, I can 
give you the necessary filter file format hints.

Additionally, claws doesn't seem to have a built-in method for adding a 
header via filter, which is one of the things I did with my kde filter 
scripts, with each one adding a header indicating the filter name, so I 
had some hope of diagnosing problems when things went awry.  BUT...

That's where claws-mail extensibility comes to the rescue, there's a 
filter action that allows calling an external script with filter 
controlled parameters, and now I have a script that adds the header as 
assigned by the filter. =:^)

If such a script sounds useful, to you or anyone else, ask and I can post 
it, or a link to it, or something.  (I should probably think about 
contacting upstream, to have it added to their list of utility scripts, 
but I've not done that yet, and I didn't see a script for it in the 
existing list, thus my creation of my own solution.)


I see you expanded on your other comment in a second post, so I'll 
address it in a reply there.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

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


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Duncan
Chuck Burns posted on Tue, 29 Nov 2011 18:39:47 -0600 as excerpted:

> I have used claws in the past.. but I found it's UI to be.. lacking.

FWIW, I first tried it a /long/ time ago, IIRC early 2002 when it was 
still the testing version of sylpheed, before I settled on kmail for nine 
years.  I find it somewhat ironic that I rejected it then, but am back on 
it all these years later, and find myself wondering at what point it 
would have become better for me than kmail, had I known about it at the 
time.

As for the claws-mail gui, it might be slightly less fancy than current 
kmail, but it MORE than makes up for it in configurability.

The configurability of its hotkeys puts pretty much every kde app I've 
ever tried (but for the old kde kaffeine, perhaps, tho I'm now using the 
qt4 based smplayer with similar configurability) to shame, and that's 
saying something!  Literally /every/ /single/ /function/ it's possible to 
invoke via menu or other action, has a configurable hotkey, and for the 
extensions I've used, that extends to them as well.  Actually configuring 
some of them might require editing its gtk2 style entirely unordered 
keydump file, but I copied that off somewhere, ordered it into GUI menu 
order, and made my changes.  That's actually how I know how much 
functionality has available configurable hotkeys, because I reordered the 
keydump file and saw them all!  I actually discovered some functionality 
I had no idea was there that way, as well.

The color scheme, etc, fits in quite well with kde, if one has the 
appropriate option checked in kde's color config, to export it to non-kde 
apps.  That's a BIG thing for me too, as I *STRONGLY* prefer a so-called 
'reverse" color scheme, with light text on a dark background, to the 
extent that the default greyish color schemes of both kde and gtk make me 
mildly physically nauseous, both for the colors and because of all that 
light background.  So it was definitely a MUST that any mail client I was 
to use either had to have a decidedly non-traditional colorscheme that I 
could be comfortable with, or more likely was compatible with kde's 
colorscheme export to non-kde apps option, and claws, being gtk-based, 
definitely fit that requirement.

And just as with the mh text-based mail client it inherited its mailstore 
format from, claws is /extremely/ extensible with external commands and 
scripts, since an individual message is simply a file in what amounts to 
raw rfc standard message format.  Maildir actually inherited that quality 
from mh format, its predecessor, and for both of them it's billed as a 
major feature advantage compared to monolithic file-per-folder formats 
such as mbox.  For whatever reason, however, mh and the family of mail 
clients based on that format (including both sylpheed and claws) seem to 
put far more emphasis on external script extensibility than do the maildir 
clients I've come across, and it's not unusual at all for longtime users 
of mh-format clients to have developed a number of their own scripts that 
they use for customized further processing.  See here for LWN's Jon 
Corbet's article on the subject:

http://lwn.net/Articles/89403/

Choice quote:

"
It should be possible to do anything with email - even things that the 
developer of the mail client might not have thought of. It must be 
possible to make connections between the mail client and the LWN site 
code. It should be possible to manipulate messages and folders with shell 
scripts and programs without great pain. The client should be a powerful 
tool for working with electronic mail, but it should be just the 
beginning point, rather than the final destination. 
"

So while the UI might be a bit... lacking... as you put it, that's "just 
the beginning point", as Jon Corbet put it.  Many mh-format mail clients 
and their users do all sorts of scripting, etc, with the mail data, and 
claws-mail is designed with just that sort of extensible scripting in 
mind, with a number of configurable ways to invoke external commands via 
the GUI, either setting them up to be run routinely, say when entering a 
particular folder or on any mail it receives, or invoked interactively.  
Again, if it's a function configurable or invokable from the claws GUI, 
it's got an assignable hotkey, and invoking an external command is as 
simple as invoking that hotkey. =:^)

Wow, I guess I'm quite the claws evangelist, aren't I?  But the bottom 
line is, the more I work with claws-mail and the more I understand its 
incredible configurability and extensibility, the more I like it!

I originally chose KDE over Gnome when I was first coming over from MS, 
because, ultimately, I couldn't understand how a FLOSS desktop could only 
allow theme changes, not have a colors selection control panel for 
changing individual colors, as even the proprietary MS had!  Well, that 
was the ultimate symptom that made my choice, anyway, but it reflected 
the fact that even back with g

Re: [kde] exporting from kmail (Was: Kmail2/Akonadi issue on FreeBSD.)

2011-11-29 Thread gene heskett
On Tuesday, November 29, 2011 10:47:42 PM Duncan did opine:

> gene heskett posted on Tue, 29 Nov 2011 13:58:11 -0500 as excerpted:
 
> > Interesting that you say claws, but this post came from the pan
> > newsreader according to its headers.
> 
> There were clues to that explanation in the previous mail, but they were
> indirect enough that someone who wasn't familiar with the service might
> have missed them.
> 
> I handle all my lists thru gmane.org, a publicly available list2news
> (and list2web, with a convenient-for-link-references header in each
> news article pointing at the web version) service, and use pan as my
> news client, so pan's what I read and reply to list messages with.  My
> email client thus only deals with normal, personal mail, not
> mailinglists.
> 
> You can read more about it at http://gmane.org .  The list2news server
> is at nntp://news.gmane.org .  You can read as news any list it
> carries, but before replying to anything using it, do read up on it at
> the website, as the mechanism it uses for posting is sort of like
> posting to a moderated newsgroup, but with an "are you sure" address
> verification on the first post to a particular list, and then a forward
> to the listserv -- it only actually posts the message to the group
> after getting it as a list message, just like any other list message.
> 
> I don't actually do much real news these days, but when I do, I use a
> separate pan instance, complete with its own settings, for handling
> news, as compared to the one I use for lists thru gmane.  Thus, as I
> said in the previous post, separate apps or at least separate instances
> of apps for each of mail, lists, news and feeds.  As it happens, I use
> separate instances of pan for lists (thru gmane) and news, and separate
> instances of claws for mail and feeds, but I did go to the trouble to
> setup separate instances, it's not one instance handling both, so they
> act more like four separate apps with similar keyboard accelerator
> settings (I have the keyboard accelerators setup similarly in each),
> than two apps each handling two tasks.
> 
> > What I would like to do is start a conversation with someone who has
> > bailed on kmail & went to claws, and see just how hard it would be to
> > convert my box to that, including the importation of the whole,
> > several Gigabyte, some of it now approaching 10 years old, kmail
> > email corpus into claws.  All the while continuing with my present
> > fetchmail based system to deliver the filtered email into
> > /var/spool/mail/gene.
> > 
> > I have a lot of claws installed already, so the first thing is to
> > import the kmail email corpus into claws.  And on that point, I have
> > no clue,
> 
> I see two other suggestions already, (1) setting up a temporary IMAP
> server to grab them and then pulling from that into claws, and (2) using
> mutt to do the conversion.  However, I used a third solution, (3)
> running the script for that purpose as available on the claws-mail
> site.  It should be easy to find as it's listed as a kmail maildir
> importer script.
> 
> I used a (different) script, also from the claws-mail site, to import
> kmails/kaddressbook's addressbook/contacts into claws-mail.  But it's
> labeled as an evolution vcf-format addressbook importer.
> 
> Unfortunately, both of these were somewhat old and needed a bit of
> massaging to work with current kmail data.  I should note that I don't
> actually know either python or perl (the languages the scripts were
> written in), but know bash and have a sysadmin's "maybe I can hack it to
> work" level familiarity with everything from C/C++ to
> perl/python/tcl/tk/ javascript to html.  That sysadmin's "can I hack it
> to work" approach was all I needed.
> 
> I think it was the maildir importer that was written in python, but it
> was python 2.2 or some such, and didn't initially work with the python
> 2.7 I'm running here.  IIRC I first had to change the shebang line (#!/
> bin/python...) to point at 2.7 instead of 2.2 but that was no big deal.
> That got it to try to run, but it spit out some errors.  Looking at
> them, I had to change a keyword or two and possibly rearrange the
> passed variables in a couple of calls.  That's certainly hacking at a
> level that's beyond some, but it should be doable with a bit of
> patience and persistence by anyone with as I said, a sysadmin's "can I
> hack it to work" level of understanding and approach to their boxes.
> 
> Based on what you have said before about your setups and the hacks you
> use to get them to work, I'm guessing it's within your capabilities.  If
> you understand shebang, that part's easy enough, and once past that, if
> need be, you can post the errors and I or someone can probably figure
> out what's going on and post a fixit mod.
> 
> Or, since I think a couple of your boxes are running older
> installations, it's quite possible you won't have to make any changes
> except possibly to the shebang, if you're ru

Re: [kde] exporting from kmail (Was: Kmail2/Akonadi issue on FreeBSD.)

2011-11-29 Thread gene heskett
On Tuesday, November 29, 2011 09:55:21 PM Duncan did opine:

> gene heskett posted on Tue, 29 Nov 2011 13:58:11 -0500 as excerpted:
> > On Tuesday, November 29, 2011 01:38:04 PM Duncan did opine:
> >> Martin (KDE) posted on Tue, 29 Nov 2011 07:44:18 +0100 as excerpted:
> >> > I had similar problems about ten years ago and my solution to this
> >> > was setting up an imap mail server. With this I do all my filtering
> >> > on the server and I am free to use any client I want - kmail and
> >> > thunderbird on linux - thunderbird on windows - k9mail on android -
> >> > native mail program on ipod-touch - any other imap aware client you
> >> > can think of
> >> 
> >> Well, the OP in this thread is using IMAP and the new kmail is still
> >> causing him problems...
> >> 
> >> > All these clients gets the same filtered mails. Isn't this an
> >> > option for you?
> >> 
> >> Yes and no.  My mail providers don't offer it, and I could run my
> >> own, but there's little point, as I don't have but the one place I
> >> do mail anyway, and even if I did run my own IMAP server, I'd still
> >> have to find a mail client I was comfortable with to access that
> >> IMAP server from the one location, so why even bother, when a good
> >> mail client bypasses the need for me to run such a server entirely?
> >> 
> >> OK, so after nearly a decade of kmail working just fine as that mail
> >> client, until the devs decided they couldn't leave well enough alone,
> >> I found I needed another solution.  But again, if I'm ultimately
> >> going to need a client I'm comfortable with anyway, why complicate
> >> things by throwing in an IMAP server when the client I'm going to
> >> need to be comfortable with anyway can deal directly with my
> >> providers' POP3 servers?
> >> 
> >> Actually, throwing in extra functionality I don't need and that only
> >> complicates things sounds like a rather familiar idea!  I wonder
> >> where I might have heard that before?  Oh, yeah, that's why I was in
> >> the situation in the first place, because the devs couldn't leave an
> >> unbroken kmail unbroken!
> >> 
> >> Oh, well, I guess I should count myself lucky that I got that nine
> >> years out of it.  Not so much software works that well for that long,
> >> and if claws-mail serves me another nine years, I guess I'll be as
> >> happy with the lengthy usefulness of my choice as I am currently with
> >> its functional practicality. =:^)
> >> 
> >> > Btw: I once tried claws-mail as well, but this program did not fit
> >> > my needs. I currently use SOGo as groupware server besides my
> >> > cyrus imap server and afaik only thunderbird and kmail2 are able
> >> > to handle CalDAV/CardDAV correctly (on Linux). I no longer want to
> >> > handle addresses and appointments in different programs
> >> > separately.
> >> 
> >> My situation is /vastly/ different from yours.  Mobile phone and/or
> >> internet simply hasn't yet fit my cost/benefit profile, and the
> >> proprietary equipment choices don't help.  Android's close enough to
> >> be acceptable if the price was right, but as I said, I've not yet
> >> seen it right, and unfortunately, the mobile-providers are moving
> >> away from unlimited Internet again now, so the situation isn't
> >> likely to get better out to at least the medium term.
> >> 
> >> And while I do have a netbook (gentoo/kde, built in a 32-bit chroot
> >> on my workstation and ssh-rsynced), I really don't use the "net" bit
> >> of it. Very close to 100% of my internet activities are on my
> >> workstation, dual 1080p monitors, etc, so I really DO have little
> >> use for IMAP. Sure, I could run an IMAP server on localhost, but as
> >> I said, it's all single- point local anyway, so it might as well all
> >> be in the client, which I'm going to have to be comfortable with in
> >> any case.
> >> 
> >> And I don't need an
> >> organizer/scheduler/calendar/groupware/nntp-client/
> >> feed-reader/mail-client/im/irc-client/singing-baboons/dancing-monkey
> >> s-
> 
> al
> 
> >> l- in-one!  In fact, I don't need an organizer/scheduler at all, and
> >> I'm more comfortable with async-style email, mailinglists and
> >> newsgroups than sync-style im/irc, so I don't need those, either.  I
> >> do use email, mailinglists, newsgroups and feeds, but I prefer
> >> separate clients or at least separate instances of the same client,
> >> for each of mail, lists, groups and feeds.  As it happens, I now
> >> have separate instances of claws for mail and feeds, and separate
> >> instances of pan for news and lists, so I'm pretty well set.
> >> 
> >> Some folks /want/ it all combined, as in konact, and that's fine...
> >> for them.  But it's not for me!
> >> 
> >> It's just too bad that kde now lacks a reasonable mail-only client
> >> (and news-only client and feeds-only client, all three, but
> >> SEPARATE), even if independently developed, without the heavyweight
> >> cost in terms of resources, reliability and single-failure-point of
> >> akonadi.  I do 

Re: [kde] Disable notification in a given activity?

2011-11-29 Thread Duncan
Kishore posted on Wed, 30 Nov 2011 00:07:18 +0530 as excerpted:

> I was hoping to have a plasma activity setup for presentations in which
> notifications are disabled. However, I learn that one cannot have
> separate panels per activity and as a consequence, when i disable
> notifications, they are disabled across all activities.
> 
> So... as the subject asks, how do i disable notifications only in a
> given activity?

I'm not sure of a working current solution to your question, but I can 
point out that integrating panels into activities is definitely part of 
the plan.  I've you've played at all with activities over the twice-
yearly kde4 feature version bumps (4.x -> 4.x+), you'll note that in each 
feature version they've changed and evolved.

Last I played with them much was in 4.6, tho, as I decided they really 
weren't something I'd use that much, and I'm now running 4.7.80 (aka 4.8 
beta1, all new 4.8 features should be included but many will be only 
partially functional and most can be expected to be quite buggy, at this 
stage), so I'm not really up with current developments.  I should 
probably backup my config just in case, and play with activities again, 
to see what's new if nothing else.  Perhaps panels integrate with 
activities now, as I remember Aaron's blogging on the subject had it 
penciled in for 4.8 or so, and I'm now running 4.8-beta1.

(FWIW, I've not noticed much different with the beta, yet.  But I have 
all the semantic-desktop stuff hard-disabled at build-time (gentoo
USE=-semantic-desktop, plus a few other USE flags toggled off) and keep 
well clear of the now thoroughly akonadi-entangled kdepim, which isn't 
installed at all, so I'd not notice major changes there, and as I said, I 
don't do activities, with only one configured, so I wouldn't have noticed 
changes there.  But I've not noticed any other changes either, except 
possibly minor tweaks to the window rules configuration GUI, with the 
major changes happening there for 4.7.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

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


[kde] exporting from kmail (Was: Kmail2/Akonadi issue on FreeBSD.)

2011-11-29 Thread Duncan
gene heskett posted on Tue, 29 Nov 2011 13:58:11 -0500 as excerpted:

> On Tuesday, November 29, 2011 01:38:04 PM Duncan did opine:
> 
>> Martin (KDE) posted on Tue, 29 Nov 2011 07:44:18 +0100 as excerpted:
>> > I had similar problems about ten years ago and my solution to this
>> > was setting up an imap mail server. With this I do all my filtering
>> > on the server and I am free to use any client I want - kmail and
>> > thunderbird on linux - thunderbird on windows - k9mail on android -
>> > native mail program on ipod-touch - any other imap aware client you
>> > can think of
>> 
>> Well, the OP in this thread is using IMAP and the new kmail is still
>> causing him problems...
>> 
>> > All these clients gets the same filtered mails. Isn't this an option
>> > for you?
>> 
>> Yes and no.  My mail providers don't offer it, and I could run my own,
>> but there's little point, as I don't have but the one place I do mail
>> anyway, and even if I did run my own IMAP server, I'd still have to
>> find a mail client I was comfortable with to access that IMAP server
>> from the one location, so why even bother, when a good mail client
>> bypasses the need for me to run such a server entirely?
>> 
>> OK, so after nearly a decade of kmail working just fine as that mail
>> client, until the devs decided they couldn't leave well enough alone, I
>> found I needed another solution.  But again, if I'm ultimately going to
>> need a client I'm comfortable with anyway, why complicate things by
>> throwing in an IMAP server when the client I'm going to need to be
>> comfortable with anyway can deal directly with my providers' POP3
>> servers?
>> 
>> Actually, throwing in extra functionality I don't need and that only
>> complicates things sounds like a rather familiar idea!  I wonder where
>> I might have heard that before?  Oh, yeah, that's why I was in the
>> situation in the first place, because the devs couldn't leave an
>> unbroken kmail unbroken!
>> 
>> Oh, well, I guess I should count myself lucky that I got that nine
>> years out of it.  Not so much software works that well for that long,
>> and if claws-mail serves me another nine years, I guess I'll be as
>> happy with the lengthy usefulness of my choice as I am currently with
>> its functional practicality. =:^)
>> 
>> > Btw: I once tried claws-mail as well, but this program did not fit my
>> > needs. I currently use SOGo as groupware server besides my cyrus imap
>> > server and afaik only thunderbird and kmail2 are able to handle
>> > CalDAV/CardDAV correctly (on Linux). I no longer want to handle
>> > addresses and appointments in different programs separately.
>> 
>> My situation is /vastly/ different from yours.  Mobile phone and/or
>> internet simply hasn't yet fit my cost/benefit profile, and the
>> proprietary equipment choices don't help.  Android's close enough to be
>> acceptable if the price was right, but as I said, I've not yet seen it
>> right, and unfortunately, the mobile-providers are moving away from
>> unlimited Internet again now, so the situation isn't likely to get
>> better out to at least the medium term.
>> 
>> And while I do have a netbook (gentoo/kde, built in a 32-bit chroot on
>> my workstation and ssh-rsynced), I really don't use the "net" bit of
>> it. Very close to 100% of my internet activities are on my workstation,
>> dual 1080p monitors, etc, so I really DO have little use for IMAP.
>> Sure, I could run an IMAP server on localhost, but as I said, it's all
>> single- point local anyway, so it might as well all be in the client,
>> which I'm going to have to be comfortable with in any case.
>> 
>> And I don't need an organizer/scheduler/calendar/groupware/nntp-client/
>> feed-reader/mail-client/im/irc-client/singing-baboons/dancing-monkeys-
al
>> l- in-one!  In fact, I don't need an organizer/scheduler at all, and
>> I'm more comfortable with async-style email, mailinglists and
>> newsgroups than sync-style im/irc, so I don't need those, either.  I do
>> use email, mailinglists, newsgroups and feeds, but I prefer separate
>> clients or at least separate instances of the same client, for each of
>> mail, lists, groups and feeds.  As it happens, I now have separate
>> instances of claws for mail and feeds, and separate instances of pan
>> for news and lists, so I'm pretty well set.
>> 
>> Some folks /want/ it all combined, as in konact, and that's fine... for
>> them.  But it's not for me!
>> 
>> It's just too bad that kde now lacks a reasonable mail-only client (and
>> news-only client and feeds-only client, all three, but SEPARATE), even
>> if independently developed, without the heavyweight cost in terms of
>> resources, reliability and single-failure-point of akonadi.  I do
>> understand the idea of shared functionality and reduced code
>> duplication, and for folks who want it all combined in one interface
>> and can tolerate the single-point-of-failure and reliability issues,
>> whether that's because they use server-based tec

Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Chuck Burns
I have used claws in the past.. but I found it's UI to be.. lacking.
I actually like the kmail interface.. but I see that it may be time to
simply revert to the old kdepim4.4.x version.  I did, however,
discover another qt4 imap client, but it appears to not be quite ready
either: Trojita. http://trojita.flaska.net/ - I have gotten it to
compile, but it apparently doesn't quite like my FreeBSD system, but I
am trying to contact their support for it, as well.

Chuck

On Tue, Nov 29, 2011 at 4:51 PM, gene heskett  wrote:
> On Tuesday, November 29, 2011 05:50:07 PM Tami King did opine:
>
>> On 11/29/11 15:38, gene heskett wrote:
>> > So the CMC/ string is a dir currently cd'd to the parent of, and it
>> > generates the archive file in mbox format in this 'parent' aka $pwd
>> > directory?
>> >
>> > Neat, and 30 megs of mutt is being installed now.  Time to test. I
>> > don't fully understand how some of the quoted stuff works, but here
>> > goes, I am cd'd into the ~/Mail/alsa-user directory, giving it the
>> > argument "cur/" in place of the CMC/.
>>
>> cd to ~/Mail and run the mutt command on alsa-user/
>>
>> Tami
>
> Thanks Tami, worked, or at least I have the 'archive' file now.  More after
> dinner.
>
>
> Cheers, Gene
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> My web page: 
> Maybe you can't buy happiness, but these days you can certainly charge it.
> ___
> 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.
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread gene heskett
On Tuesday, November 29, 2011 05:50:07 PM Tami King did opine:

> On 11/29/11 15:38, gene heskett wrote:
> > So the CMC/ string is a dir currently cd'd to the parent of, and it
> > generates the archive file in mbox format in this 'parent' aka $pwd
> > directory?
> > 
> > Neat, and 30 megs of mutt is being installed now.  Time to test. I
> > don't fully understand how some of the quoted stuff works, but here
> > goes, I am cd'd into the ~/Mail/alsa-user directory, giving it the
> > argument "cur/" in place of the CMC/.
> 
> cd to ~/Mail and run the mutt command on alsa-user/
> 
> Tami

Thanks Tami, worked, or at least I have the 'archive' file now.  More after 
dinner.


Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: 
Maybe you can't buy happiness, but these days you can certainly charge it.
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Tami King
On 11/29/11 15:38, gene heskett wrote:

> So the CMC/ string is a dir currently cd'd to the parent of, and it 
> generates the archive file in mbox format in this 'parent' aka $pwd 
> directory?
> 
> Neat, and 30 megs of mutt is being installed now.  Time to test. I don't 
> fully understand how some of the quoted stuff works, but here goes, I am  
> cd'd into the ~/Mail/alsa-user directory, giving it the argument "cur/" in 
> place of the CMC/.

cd to ~/Mail and run the mutt command on alsa-user/

Tami
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread gene heskett
On Tuesday, November 29, 2011 04:18:22 PM Tami King did opine:

> On 11/29/11 14:11, J wrote:
> > gene heskett
> > 
> >> On Tuesday, November 29, 2011 02:43:56 PM J did opine:
> >> 
> >> Claws apparently does only mailfile operations, whereas I have 3/4ths
> >> of the kmail "cur" subdirs as maildirs.
> >> 
> >> I was thinking that I could maybe do a "cpa cur/* /var/mail/gene" and
> >> then have claws read it just as if it was incoming mail.
> >> 
> >> Would that, or a similar idea work?
> > 
> > To convert a Maildir you either need to convert the mail files into
> > mbox format (I don't recommend this, the scripts I tried were almost
> > as bad as kMail2) or put in a temporary install of an IMAP server and
> > rename Folder to .Folder within the Maildir to get the imap server to
> > see them.
> 
> You can convert Maildir to mbox using mutt.  I have been doing that as
> needed since moving from Kmail.
> 
> mutt -f CMC/ -e 'set mbox_type=mbox; set confirmcreate=no; set
> delete=no; push "T.*;sarchive"'
> 
> That reads messages in the Maildir directory CMC and saves them to an
> mbox file called archive.  You can then move archive to where ever it
> needs to be for your new email client.
> 
> Tami

So the CMC/ string is a dir currently cd'd to the parent of, and it 
generates the archive file in mbox format in this 'parent' aka $pwd 
directory?

Neat, and 30 megs of mutt is being installed now.  Time to test. I don't 
fully understand how some of the quoted stuff works, but here goes, I am  
cd'd into the ~/Mail/alsa-user directory, giving it the argument "cur/" in 
place of the CMC/.

2 errors as follows:
gene@coyote alsa-user]$ mutt -f cur/ -e 'set mbox_type=mbox; set 
confirmcreate=no;set delete=no;push "T.*;sarchive"'
cur/ is not a mailbox.

So I cd into cur, where an ls shows several hundred files, and get a "cur/" 
no such directory error.  Also for ./cur/, and ./cur/* actually opens mutt 
to compose a message.  Not exactly what I wanted. :)

Call me confused, or an oldtimer (which I am at 77), but did I do it wrong?  
Running as the user me obviously.

Obviously Tami I don't have the complete idea grokked.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: 
In war, truth is the first casualty.
-- U Thant
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Tami King
On 11/29/11 14:11, J wrote:
> 
> gene heskett
>> On Tuesday, November 29, 2011 02:43:56 PM J did opine:

>> Claws apparently does only mailfile operations, whereas I have 3/4ths of
>> the kmail "cur" subdirs as maildirs.
>>
>> I was thinking that I could maybe do a "cpa cur/* /var/mail/gene" and then
>> have claws read it just as if it was incoming mail.
>>
>> Would that, or a similar idea work?

> 
> To convert a Maildir you either need to convert the mail files into mbox
> format (I don't recommend this, the scripts I tried were almost as bad as
> kMail2) or put in a temporary install of an IMAP server and rename Folder
> to .Folder within the Maildir to get the imap server to see them.

You can convert Maildir to mbox using mutt.  I have been doing that as
needed since moving from Kmail.

mutt -f CMC/ -e 'set mbox_type=mbox; set confirmcreate=no; set
delete=no; push "T.*;sarchive"'

That reads messages in the Maildir directory CMC and saves them to an
mbox file called archive.  You can then move archive to where ever it
needs to be for your new email client.

Tami
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread gene heskett
On Tuesday, November 29, 2011 03:27:14 PM J did opine:

> gene heskett
> 
> > On Tuesday, November 29, 2011 02:43:56 PM J did opine:
> >> gene heskett
> >> 
> >> > On Tuesday, November 29, 2011 01:38:04 PM Duncan did opine:
> >> >> Maybe someday an independent kde dev will come along and start a
> >> >> "just does X" client for each of those three Xs.  Maybe not.  If
> >> >> I'm lucky, tho, they'll be started right away, and be reasonably
> >> >> mature and ready for use when claws jumps the shark like kmail
> >> >> did, tho hopefully that won't be for a decade or longer, if ever.
> >> > 
> >> > Interesting that you say claws, but this post came from the pan
> >> > newsreader according to its headers.  It pointed out also that I
> >> > need to apparently increase the number of copies of spamd I have
> >> > running as it failed on the first call getting an
> >> > X-Nasty-aren't-we inserted by procmail.  Local stuffs.
> >> > 
> >> > What I would like to do is start a conversation with someone who
> >> > has bailed
> >> > on kmail & went to claws, and see just how hard it would be to
> >> > convert my box to that, including the importation of the whole,
> >> > several Gigabyte, some
> >> > of it now approaching 10 years old, kmail email corpus into claws.
> >> > All the
> >> > while continuing with my present fetchmail based system to deliver
> >> > the filtered email into /var/spool/mail/gene.
> >> 
> >> I just did that.  I tried to upgrade to kmail2 and it spectacularly
> >> failed.  I switched to claws, based on Duncan's recommendation.  I'm
> >> surprised I haven't been using it for some time.
> >> 
> >> > Like others, the ^#$%& churn in kmail's "accessory" tie-ins,
> >> > without ever fixing its most glaring fault, the lack of
> >> > multi-threading vis-a-vis mail fetching, is beginning to get under
> >> > my skin.
> >> 
> >> Claws doesn't multi-thread well either.
> >> 
> >> > This of course is off topic from the OP's subject line, sorry. 
> >> > Humm, no I'm not, come to think of it, kde needs to better
> >> > understand the users viewpoint on stuff like this, and this is
> >> > after all the kde (the whole maryann) mailing list.
> >> > 
> >> > I have a lot of claws installed already, so the first thing is to
> >> > import the kmail email corpus into claws.  And on that point, I
> >> > have no clue, but would assume the right search terms might find a
> >> > tut on the web.  My feeble  efforts haven't found it yet though.
> >> 
> >> I cheated.  I set up an imap server on localhost, pointed it to my
> >> kMail Maildir and then just did a drag and drop into the Claws MH
> >> mailstore. Then I uninstalled the imap server.
> > 
> > Claws apparently does only mailfile operations, whereas I have 3/4ths
> > of the kmail "cur" subdirs as maildirs.
> > 
> > I was thinking that I could maybe do a "cpa cur/* /var/mail/gene" and
> > then have claws read it just as if it was incoming mail.
> > 
> > Would that, or a similar idea work?
> > 
> > Thanks.
> 
> To convert a Maildir you either need to convert the mail files into mbox
> format (I don't recommend this, the scripts I tried were almost as bad
> as kMail2) or put in a temporary install of an IMAP server and rename
> Folder to .Folder within the Maildir to get the imap server to see
> them.

The difference between the maildir/file, and the individual email in a 
mailfile, seems to be that the apparent break between the files that I have 
noted the possible separator marker is a 2 empty lines followed by a From 
with no terminating semicolon, it really shouldn't be that hard to convert 
back to mailfile.  However, the mailfile messages are already contaminated 
with spamassassin headers, and the 5 or 6 I looked at are also bereft of 
the bare 'From so and so @ site' line, so possibly it will be more complex 
than a simple cpa operation after all.

> 
> It took me about 20 minutes to install, configure, convert, and
> uninstall. I had about 7 years of old email to move over.  Hardest part
> was configuring cyrus-IMAP to see the Maildir (one config item under
> OpenSusE).

I'll have to check cyrus-IMAP out after all.  Installed, but an lsof |grep 
cyrus doesn't return a hint of where its working directory is.  I'll search 
/etc & its man page for clues.

Thanks.


Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: 
One man's folly is another man's wife.
-- Helen Rowland
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread J

gene heskett
> On Tuesday, November 29, 2011 02:43:56 PM J did opine:
>
>> gene heskett
>>
>> > On Tuesday, November 29, 2011 01:38:04 PM Duncan did opine:
>> >> Maybe someday an independent kde dev will come along and start a
>> >> "just does X" client for each of those three Xs.  Maybe not.  If I'm
>> >> lucky, tho, they'll be started right away, and be reasonably mature
>> >> and ready for use when claws jumps the shark like kmail did, tho
>> >> hopefully that won't be for a decade or longer, if ever.
>> >
>> > Interesting that you say claws, but this post came from the pan
>> > newsreader according to its headers.  It pointed out also that I need
>> > to apparently increase the number of copies of spamd I have running
>> > as it failed on the first call getting an X-Nasty-aren't-we inserted
>> > by procmail.  Local stuffs.
>> >
>> > What I would like to do is start a conversation with someone who has
>> > bailed
>> > on kmail & went to claws, and see just how hard it would be to convert
>> > my box to that, including the importation of the whole, several
>> > Gigabyte, some
>> > of it now approaching 10 years old, kmail email corpus into claws.
>> > All the
>> > while continuing with my present fetchmail based system to deliver the
>> > filtered email into /var/spool/mail/gene.
>>
>> I just did that.  I tried to upgrade to kmail2 and it spectacularly
>> failed.  I switched to claws, based on Duncan's recommendation.  I'm
>> surprised I haven't been using it for some time.
>>
>> > Like others, the ^#$%& churn in kmail's "accessory" tie-ins, without
>> > ever fixing its most glaring fault, the lack of multi-threading
>> > vis-a-vis mail fetching, is beginning to get under my skin.
>>
>> Claws doesn't multi-thread well either.
>>
>> > This of course is off topic from the OP's subject line, sorry.  Humm,
>> > no I'm not, come to think of it, kde needs to better understand the
>> > users viewpoint on stuff like this, and this is after all the kde
>> > (the whole maryann) mailing list.
>> >
>> > I have a lot of claws installed already, so the first thing is to
>> > import the kmail email corpus into claws.  And on that point, I have
>> > no clue, but would assume the right search terms might find a tut on
>> > the web.  My feeble  efforts haven't found it yet though.
>>
>> I cheated.  I set up an imap server on localhost, pointed it to my kMail
>> Maildir and then just did a drag and drop into the Claws MH mailstore.
>> Then I uninstalled the imap server.
>
> Claws apparently does only mailfile operations, whereas I have 3/4ths of
> the kmail "cur" subdirs as maildirs.
>
> I was thinking that I could maybe do a "cpa cur/* /var/mail/gene" and then
> have claws read it just as if it was incoming mail.
>
> Would that, or a similar idea work?
>
> Thanks.
>

To convert a Maildir you either need to convert the mail files into mbox
format (I don't recommend this, the scripts I tried were almost as bad as
kMail2) or put in a temporary install of an IMAP server and rename Folder
to .Folder within the Maildir to get the imap server to see them.

It took me about 20 minutes to install, configure, convert, and uninstall.
 I had about 7 years of old email to move over.  Hardest part was
configuring cyrus-IMAP to see the Maildir (one config item under
OpenSusE).




-- 
Janus


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


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread gene heskett
On Tuesday, November 29, 2011 02:43:56 PM J did opine:

> gene heskett
> 
> > On Tuesday, November 29, 2011 01:38:04 PM Duncan did opine:
> >> Maybe someday an independent kde dev will come along and start a
> >> "just does X" client for each of those three Xs.  Maybe not.  If I'm
> >> lucky, tho, they'll be started right away, and be reasonably mature
> >> and ready for use when claws jumps the shark like kmail did, tho
> >> hopefully that won't be for a decade or longer, if ever.
> > 
> > Interesting that you say claws, but this post came from the pan
> > newsreader according to its headers.  It pointed out also that I need
> > to apparently increase the number of copies of spamd I have running
> > as it failed on the first call getting an X-Nasty-aren't-we inserted
> > by procmail.  Local stuffs.
> > 
> > What I would like to do is start a conversation with someone who has
> > bailed
> > on kmail & went to claws, and see just how hard it would be to convert
> > my box to that, including the importation of the whole, several
> > Gigabyte, some
> > of it now approaching 10 years old, kmail email corpus into claws. 
> > All the
> > while continuing with my present fetchmail based system to deliver the
> > filtered email into /var/spool/mail/gene.
> 
> I just did that.  I tried to upgrade to kmail2 and it spectacularly
> failed.  I switched to claws, based on Duncan's recommendation.  I'm
> surprised I haven't been using it for some time.
> 
> > Like others, the ^#$%& churn in kmail's "accessory" tie-ins, without
> > ever fixing its most glaring fault, the lack of multi-threading
> > vis-a-vis mail fetching, is beginning to get under my skin.
> 
> Claws doesn't multi-thread well either.
> 
> > This of course is off topic from the OP's subject line, sorry.  Humm,
> > no I'm not, come to think of it, kde needs to better understand the
> > users viewpoint on stuff like this, and this is after all the kde
> > (the whole maryann) mailing list.
> > 
> > I have a lot of claws installed already, so the first thing is to
> > import the kmail email corpus into claws.  And on that point, I have
> > no clue, but would assume the right search terms might find a tut on
> > the web.  My feeble  efforts haven't found it yet though.
> 
> I cheated.  I set up an imap server on localhost, pointed it to my kMail
> Maildir and then just did a drag and drop into the Claws MH mailstore.
> Then I uninstalled the imap server.

Claws apparently does only mailfile operations, whereas I have 3/4ths of 
the kmail "cur" subdirs as maildirs.

I was thinking that I could maybe do a "cpa cur/* /var/mail/gene" and then 
have claws read it just as if it was incoming mail.

Would that, or a similar idea work?

Thanks.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: 
Television is now so desperately hungry for material that it is scraping
the top of the barrel.
-- Gore Vidal
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread J

gene heskett
> On Tuesday, November 29, 2011 01:38:04 PM Duncan did opine:
>
>>
>> Maybe someday an independent kde dev will come along and start a "just
>> does X" client for each of those three Xs.  Maybe not.  If I'm lucky,
>> tho, they'll be started right away, and be reasonably mature and ready
>> for use when claws jumps the shark like kmail did, tho hopefully that
>> won't be for a decade or longer, if ever.
>
> Interesting that you say claws, but this post came from the pan newsreader
> according to its headers.  It pointed out also that I need to apparently
> increase the number of copies of spamd I have running as it failed on the
> first call getting an X-Nasty-aren't-we inserted by procmail.  Local
> stuffs.
>
> What I would like to do is start a conversation with someone who has
> bailed
> on kmail & went to claws, and see just how hard it would be to convert my
> box to that, including the importation of the whole, several Gigabyte,
> some
> of it now approaching 10 years old, kmail email corpus into claws.  All
> the
> while continuing with my present fetchmail based system to deliver the
> filtered email into /var/spool/mail/gene.

I just did that.  I tried to upgrade to kmail2 and it spectacularly
failed.  I switched to claws, based on Duncan's recommendation.  I'm
surprised I haven't been using it for some time.


> Like others, the ^#$%& churn in kmail's "accessory" tie-ins, without ever
> fixing its most glaring fault, the lack of multi-threading vis-a-vis mail
> fetching, is beginning to get under my skin.

Claws doesn't multi-thread well either.


> This of course is off topic from the OP's subject line, sorry.  Humm, no
> I'm not, come to think of it, kde needs to better understand the users
> viewpoint on stuff like this, and this is after all the kde (the whole
> maryann) mailing list.
>
> I have a lot of claws installed already, so the first thing is to import
> the kmail email corpus into claws.  And on that point, I have no clue, but
> would assume the right search terms might find a tut on the web.  My
> feeble  efforts haven't found it yet though.

I cheated.  I set up an imap server on localhost, pointed it to my kMail
Maildir and then just did a drag and drop into the Claws MH mailstore. 
Then I uninstalled the imap server.

-- 
Janus


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


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread gene heskett
On Tuesday, November 29, 2011 01:38:04 PM Duncan did opine:

> Martin (KDE) posted on Tue, 29 Nov 2011 07:44:18 +0100 as excerpted:
> > I had similar problems about ten years ago and my solution to this was
> > setting up an imap mail server. With this I do all my filtering on the
> > server and I am free to use any client I want
> > - kmail and thunderbird on linux
> > - thunderbird on windows
> > - k9mail on android
> > - native mail program on ipod-touch
> > - any other imap aware client you can think of
> 
> Well, the OP in this thread is using IMAP and the new kmail is still
> causing him problems...
> 
> > All these clients gets the same filtered mails. Isn't this an option
> > for you?
> 
> Yes and no.  My mail providers don't offer it, and I could run my own,
> but there's little point, as I don't have but the one place I do mail
> anyway, and even if I did run my own IMAP server, I'd still have to find
> a mail client I was comfortable with to access that IMAP server from the
> one location, so why even bother, when a good mail client bypasses the
> need for me to run such a server entirely?
> 
> OK, so after nearly a decade of kmail working just fine as that mail
> client, until the devs decided they couldn't leave well enough alone, I
> found I needed another solution.  But again, if I'm ultimately going to
> need a client I'm comfortable with anyway, why complicate things by
> throwing in an IMAP server when the client I'm going to need to be
> comfortable with anyway can deal directly with my providers' POP3
> servers?
> 
> Actually, throwing in extra functionality I don't need and that only
> complicates things sounds like a rather familiar idea!  I wonder where I
> might have heard that before?  Oh, yeah, that's why I was in the
> situation in the first place, because the devs couldn't leave an
> unbroken kmail unbroken!
> 
> Oh, well, I guess I should count myself lucky that I got that nine years
> out of it.  Not so much software works that well for that long, and if
> claws-mail serves me another nine years, I guess I'll be as happy with
> the lengthy usefulness of my choice as I am currently with its
> functional practicality. =:^)
> 
> > Btw: I once tried claws-mail as well, but this program did not fit my
> > needs. I currently use SOGo as groupware server besides my cyrus imap
> > server and afaik only thunderbird and kmail2 are able to handle
> > CalDAV/CardDAV correctly (on Linux). I no longer want to handle
> > addresses and appointments in different programs separately.
> 
> My situation is /vastly/ different from yours.  Mobile phone and/or
> internet simply hasn't yet fit my cost/benefit profile, and the
> proprietary equipment choices don't help.  Android's close enough to be
> acceptable if the price was right, but as I said, I've not yet seen it
> right, and unfortunately, the mobile-providers are moving away from
> unlimited Internet again now, so the situation isn't likely to get
> better out to at least the medium term.
> 
> And while I do have a netbook (gentoo/kde, built in a 32-bit chroot on
> my workstation and ssh-rsynced), I really don't use the "net" bit of
> it. Very close to 100% of my internet activities are on my workstation,
> dual 1080p monitors, etc, so I really DO have little use for IMAP. 
> Sure, I could run an IMAP server on localhost, but as I said, it's all
> single- point local anyway, so it might as well all be in the client,
> which I'm going to have to be comfortable with in any case.
> 
> And I don't need an organizer/scheduler/calendar/groupware/nntp-client/
> feed-reader/mail-client/im/irc-client/singing-baboons/dancing-monkeys-al
> l- in-one!  In fact, I don't need an organizer/scheduler at all, and I'm
> more comfortable with async-style email, mailinglists and newsgroups
> than sync-style im/irc, so I don't need those, either.  I do use email,
> mailinglists, newsgroups and feeds, but I prefer separate clients or at
> least separate instances of the same client, for each of mail, lists,
> groups and feeds.  As it happens, I now have separate instances of
> claws for mail and feeds, and separate instances of pan for news and
> lists, so I'm pretty well set.
> 
> Some folks /want/ it all combined, as in konact, and that's fine... for
> them.  But it's not for me!
> 
> It's just too bad that kde now lacks a reasonable mail-only client (and
> news-only client and feeds-only client, all three, but SEPARATE), even
> if independently developed, without the heavyweight cost in terms of
> resources, reliability and single-failure-point of akonadi.  I do
> understand the idea of shared functionality and reduced code
> duplication, and for folks who want it all combined in one interface
> and can tolerate the single-point-of-failure and reliability issues,
> whether that's because they use server-based technologies or whatever,
> akonadi and kontact may be WONDERFUL.  But here, I just want my simple
> to use and reliable separate apps back!
> 
> Maybe so

[kde] Disable notification in a given activity?

2011-11-29 Thread Kishore
I was hoping to have a plasma activity setup for presentations in which 
notifications are disabled. However, I learn that one cannot have separate 
panels per activity and as a consequence, when i disable notifications, they 
are disabled across all activities.

So... as the subject asks, how do i disable notifications only in a given 
activity?
-- 
Cheers!
Kishore
___
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.


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Martin (KDE)
Am 29.11.2011 00:40, schrieb Chuck Burns:
> DataStore (Database Error): DataStore::beginTransaction Driver said:
> QMYSQL: Unable to begin transaction Database said:MySQL server has
> gone awayAgentBase(akonadi_imap_resource_0): Unknown error. (There is
> no transaction in progress.)

Hm, this sounds like a database problem. As MySQL changes there are some
problems with akonadi and mysql. There is a web site with tips if there
are problems with kmail (one line):
http://userbase.kde.org/KMail/FAQs_Hints_and_Tips#Clean_start_after_a_failed_migration

Maybe this helps.

Regards
Martin

> 
> More info
> 
> Chuck Burns
> On Mon, Nov 28, 2011 at 11:38 AM, Chuck Burns  wrote:
>> I compiled the kdepim4.7.3 version under FreeBSD 9.0-STABLE, and while
>> everything -seemed- to work just fine, I am finding that is not quite
>> the case.
>>
>> After I added my 2 IMAP accounts, they failed to show up at all in
>> KMail2, but existed in Akonadi Console's list, so I restarted the
>> akonadi mysql server, restarted KMail2, and voila, They show up there
>> now..
>>
>> Not so fast, however... It only downloaded a few messages from one
>> account, nothing on my other IMAP account shows up at all.
>>
>> However, by checking thru the "Server-side Subscription" Akonadi is
>> able to see my email folders, just is refusing get any more messages.
>>
>> But wait! There's more! (lol)
>>
>> I cannot -read- the message that it -does- show in the list.  I select
>> the messages, and they do not show up in my message window.
>>
>> I am getting this from the "Enable Debugger" check box:
>> AkonadiConsole Browser Widget (0x805ca4550) 4 FETCH 1:* FULLPAYLOAD
>> ANCESTORS INF EXTERNALPAYLOAD (UID REMOTEID REMOTEREVISION
>> COLLECTIONID FLAGS SIZE DATETIME)
>> AkonadiConsole Browser Widget (0x805ca4550) 4 NO Unable to fetch item
>> from backend
> ___
> 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.

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


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Martin (KDE)
Am 29.11.2011 14:05, schrieb Jerry:
> On Tue, 29 Nov 2011 07:44:18 +0100
> Martin (KDE) articulated:
> 
>> Btw: I once tried claws-mail as well, but this program did not fit my
>> needs. I currently use SOGo as groupware server besides my cyrus imap
>> server and afaik only thunderbird and kmail2 are able to handle
>> CalDAV/CardDAV correctly (on Linux). I no longer want to handle
>> addresses and appointments in different programs separately.
> 
> Interesting. I use Claws-Mail myself and am quite happy with it
> although, like I guess about any other program you can name, there is
> definitely room for improvement.
> 
> Out of morbid curiosity, did you ever try to contact the CM developers
> directly and voice your concerns? I have done so in the past with some
> limited success. I don't expect them to jump just because I ask them
> to; however, they did address a few concerns that I had.
> 
> Perhaps contacting them yourself or posting a suggestion or feature
> desired request on their bugzilla or mail forum might prove useful.

I thought about that, yes. But as I use thunderbird (on different
windows systems and linux) and kmail (up to last weekend version 1,
since last weekend version 2 on linux only) I did not want to use
another one.

About two (or may be even three) years ago I had some issues with kmail.
That was the reason for me testing claws. As the kmail problems were
solved a month later there was no need for claws any more.

Since about tree days I use kmail2 and had no problems until then. But I
did not went the migration way. I completely removed all kmail
configurations and started from the beginning. As I don't use filters in
kmail nor any other special settings reconfiguration took about one hour
(configuring imap server, creating four identities, setting some
exirations and mailing list config to mail folders ...). I removed the
nepomuk database as well.

Searching in mails is currently limited, but as I rarely use global
search this is not a big problem.

Reagrds
Martin

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


Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Jerry
On Tue, 29 Nov 2011 07:44:18 +0100
Martin (KDE) articulated:

> Btw: I once tried claws-mail as well, but this program did not fit my
> needs. I currently use SOGo as groupware server besides my cyrus imap
> server and afaik only thunderbird and kmail2 are able to handle
> CalDAV/CardDAV correctly (on Linux). I no longer want to handle
> addresses and appointments in different programs separately.

Interesting. I use Claws-Mail myself and am quite happy with it
although, like I guess about any other program you can name, there is
definitely room for improvement.

Out of morbid curiosity, did you ever try to contact the CM developers
directly and voice your concerns? I have done so in the past with some
limited success. I don't expect them to jump just because I ask them
to; however, they did address a few concerns that I had.

Perhaps contacting them yourself or posting a suggestion or feature
desired request on their bugzilla or mail forum might prove useful.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
The value of a program is proportional to the weight of its output.
___
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.

Re: [kde] Kmail2/Akonadi issue on FreeBSD.

2011-11-29 Thread Duncan
Martin (KDE) posted on Tue, 29 Nov 2011 07:44:18 +0100 as excerpted:

> I had similar problems about ten years ago and my solution to this was
> setting up an imap mail server. With this I do all my filtering on the
> server and I am free to use any client I want 
> - kmail and thunderbird on linux
> - thunderbird on windows
> - k9mail on android
> - native mail program on ipod-touch
> - any other imap aware client you can think of

Well, the OP in this thread is using IMAP and the new kmail is still 
causing him problems...

> All these clients gets the same filtered mails. Isn't this an option for
> you?

Yes and no.  My mail providers don't offer it, and I could run my own, 
but there's little point, as I don't have but the one place I do mail 
anyway, and even if I did run my own IMAP server, I'd still have to find 
a mail client I was comfortable with to access that IMAP server from the 
one location, so why even bother, when a good mail client bypasses the 
need for me to run such a server entirely?

OK, so after nearly a decade of kmail working just fine as that mail 
client, until the devs decided they couldn't leave well enough alone, I 
found I needed another solution.  But again, if I'm ultimately going to 
need a client I'm comfortable with anyway, why complicate things by 
throwing in an IMAP server when the client I'm going to need to be 
comfortable with anyway can deal directly with my providers' POP3 servers?

Actually, throwing in extra functionality I don't need and that only 
complicates things sounds like a rather familiar idea!  I wonder where I 
might have heard that before?  Oh, yeah, that's why I was in the 
situation in the first place, because the devs couldn't leave an unbroken 
kmail unbroken!

Oh, well, I guess I should count myself lucky that I got that nine years 
out of it.  Not so much software works that well for that long, and if 
claws-mail serves me another nine years, I guess I'll be as happy with 
the lengthy usefulness of my choice as I am currently with its functional 
practicality. =:^)

> Btw: I once tried claws-mail as well, but this program did not fit my
> needs. I currently use SOGo as groupware server besides my cyrus imap
> server and afaik only thunderbird and kmail2 are able to handle
> CalDAV/CardDAV correctly (on Linux). I no longer want to handle
> addresses and appointments in different programs separately.

My situation is /vastly/ different from yours.  Mobile phone and/or 
internet simply hasn't yet fit my cost/benefit profile, and the 
proprietary equipment choices don't help.  Android's close enough to be 
acceptable if the price was right, but as I said, I've not yet seen it 
right, and unfortunately, the mobile-providers are moving away from 
unlimited Internet again now, so the situation isn't likely to get better 
out to at least the medium term.

And while I do have a netbook (gentoo/kde, built in a 32-bit chroot on my 
workstation and ssh-rsynced), I really don't use the "net" bit of it.  
Very close to 100% of my internet activities are on my workstation, dual 
1080p monitors, etc, so I really DO have little use for IMAP.  Sure, I 
could run an IMAP server on localhost, but as I said, it's all single-
point local anyway, so it might as well all be in the client, which I'm 
going to have to be comfortable with in any case.

And I don't need an organizer/scheduler/calendar/groupware/nntp-client/
feed-reader/mail-client/im/irc-client/singing-baboons/dancing-monkeys-all-
in-one!  In fact, I don't need an organizer/scheduler at all, and I'm 
more comfortable with async-style email, mailinglists and newsgroups than 
sync-style im/irc, so I don't need those, either.  I do use email, 
mailinglists, newsgroups and feeds, but I prefer separate clients or at 
least separate instances of the same client, for each of mail, lists, 
groups and feeds.  As it happens, I now have separate instances of claws 
for mail and feeds, and separate instances of pan for news and lists, so 
I'm pretty well set.

Some folks /want/ it all combined, as in konact, and that's fine... for 
them.  But it's not for me!

It's just too bad that kde now lacks a reasonable mail-only client (and 
news-only client and feeds-only client, all three, but SEPARATE), even if 
independently developed, without the heavyweight cost in terms of 
resources, reliability and single-failure-point of akonadi.  I do 
understand the idea of shared functionality and reduced code duplication, 
and for folks who want it all combined in one interface and can tolerate 
the single-point-of-failure and reliability issues, whether that's 
because they use server-based technologies or whatever, akonadi and 
kontact may be WONDERFUL.  But here, I just want my simple to use and 
reliable separate apps back!

Maybe someday an independent kde dev will come along and start a "just 
does X" client for each of those three Xs.  Maybe not.  If I'm lucky, 
tho, they'll be started right away, and be reasonably matur