[Users] Need help, moving from kmail-1.13.5 to claws-mail

[Gene Heskett]

On Monday 24 February 2014 15:27:06 Steve Litt did opine:

> On Mon, 24 Feb 2014 09:49:23 -0500
> 
> Gene Heskett <gheskett at wdtv.com> wrote:
> > On Monday 24 February 2014 09:34:03 Ricardo Mones did opine:
> > > On Mon, Feb 24, 2014 at 08:44:51AM -0500, Gene Heskett wrote:
> > > > On Monday 24 February 2014 08:42:10 Paul did opine:
> > > > > On Sat, 22 Feb 2014 22:05:35 -0500
> > > > > 
> > > > > Gene Heskett <gheskett at wdtv.com> wrote:
> > > > > > /var/spool/mail/$user
> > > > > 
> > > > > Create a 'Local' account in Claws and that will pick up mail
> > > > > from /var/spool/mail/$user
> > > > > 
> > > > > with regards
> > > > > 
> > > > > Paul
> > > > 
> > > > This is what I am doing in kmail now.  But in the long run, I'd
> > > > like to put dovecot in the chain so I can access it, using claws
> > > > in imap mode, from any machine on my local net.
> > > > 
> > >   If you have X servers on your local net machines you can simply
> > > 
> > > ssh -X your server and run Claws Mail there but viewing it locally.
> > > 
> > >   regards,
> > 
> > Ok, but if I leave this copy running 24/7 like I do kmail, can this
> > machine actually run another non-interacting copy when I ssh -Y
> > coyote from say, lathe.coyote.den and run the 2nd copy beside the one
> > that is already running?  Previously I have not had a lot of luck
> > trying to do that.  My background script that uses inotifywait for
> > that, will cause reboot to fix system problems if the dbus cache
> > pipeline fills up with unreplied msgs.
> 
> Leave dbus alone. Don't use it in your script, and Claws won't use it
> either. Kmail makes dbus go 99% of CPU, often so often that I had to
> use a cron job to look for and kill dbus instances remaining above 94%
> for more than 5 seconds.

I agree, its probably a solution looking for a problem, but I can count on 
one or 2 fingers the number of times the grab a core and hang on has 
happened in about 6 or 7 years of use.
 
> I'm a huge fan of encapsulation, and dbus, even though not made by the
> Klowns Destroying Everything (KDE), is a huge encapsulation violation.
> If I absolutely need two processes to talk to each other, I can usually
> find ways of doing that myself, especially if I'm the guy who coded one
> or both of them.

Yeah, I'd be much more in favor of a "unix socket" (domain.name:37295) for 
example, to feed, but I've no experience in coding such a beast.  But I 
think you can check for the presence of the socket before you send the 
command to it, preventing the trash build up.  Well written bash scripts 
can do that pretty easy and I've managed to hit a lick or two with those.  
I must have, when everything is up and running here, a good dozen bash 
scripts that think they are background daemons.  ~/bin/mailwatcher, which 
uses inotifywait, is just one of them.  ATM one java jar is not running, a 
feedback loop over heated and blew the bit banging serial port in my Color 
Computer 3 in the basement, so that and 2 or 3 other bash helpers aren't 
running.  My nightly amanda run for backups is managed by a bash script 
that fills the recovery data gap of one day, so I can recover to exactly 
what I had at 2AM this morning if something should be fat fingered.  To 
new, bare metal if need be.


> Thanks,
> 
> SteveT
> 
> Steve Litt                *  http://www.troubleshooters.com/
> Troubleshooting Training  *  Human Performance
> _______________________________________________
> Users mailing list
> Users at lists.claws-mail.org
> http://lists.claws-mail.org/cgi-bin/mailman/listinfo/users


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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

NOTICE: Will pay 100 USD for an HP-4815A defective but
complete probe assembly.