On Friday 04 December 2015 02:50:02 Dr. Nikolaus Klepp wrote:

> Am Donnerstag, 3. Dezember 2015 schrieb Gene Heskett:
> > On Thursday 03 December 2015 06:56:53 deloptes wrote:
> > > > How hard would it be to setup an imap server on this machine,
> > > > that uses the existing email corpus database, /home/gene/Mail,
> > > > and serves it to any other kmail agents running on my local
> > > > network?
> > >
> > > I am using devecot imap on the server at home and access the
> > > mailbox on that server from multiple clients. There is nothing
> > > special for that.
> > >
> > > You have to tell dovecot where your mail is and in which format.
> > > usually I would configure the server side mailbox aside from the
> > > home directory.
> > > You could use imap to copy your local mailbox data to the server
> > > dir after you set it up once.
> > > This is in /etc/dovecot/conf.d/10-mail.conf
> > >
> > > you can use anything like fetchmail to get mails to the mailbox
> > > and serve it to all clients. If you have any other pop3 accounts.
> > > This is what I would do. Thus you collect your mails in one
> > > mailbox and access them via imap by any client.
> > >
> > > I also had my mailbox set in the user home years ago and this was
> > > I guess by default set by Kmail, but turned to be misleading.
> > >
> > > However the flexibility of all this is so big that there is surely
> > > a way to get what you want or get it really wrong.
> > >
> > > I hope this helps
> >
> > Knowing where it keeps its log would help.  Its running, hasn't
> > reported any errordbut no logfile can be found. I also asked kmail
> > on one of the machines to access kit, and then had to leave for
> > about 5 hours. at the end of which that " client" kmail was still
> > trying to read the server.
> >
> > dovecot -n reports:
> >
> > # 2.1.7: /etc/dovecot/dovecot.conf
> > # OS: Linux 3.4-9-amd64 x86_64 Debian 7.9
> > mail_location = maildir:~/Mail/*/cur
> > mail_plugins = IMAP
> > namespace inbox {
> >   inbox = yes
> >   location =
> >   mailbox Drafts {
> >     special_use = \Drafts
> >   }
> >   mailbox Junk {
> >     special_use = \Junk
> >   }
> >   mailbox Sent {
> >     special_use = \Sent
> >   }
> >   mailbox "Sent Messages" {
> >     special_use = \Sent
> >   }
> >   mailbox Trash {
> >     special_use
> >
> > Hints?
> >
> > Thank you.
> >
> > Cheers, Gene Heskett
>
> Hi Gene!
>
> I might miss the point, but what would happen if you just run kmail on
> the remote comuter - that where your mails are and where you have
> kmail working - like this:
>
> $ ssh -X gene@remote /opt/trinity/bin/kmail
>
> Nik

Tried that from an ssh -Y login to GO704 just now.

That claims that kmail is already running, which of course it is, 
on /this/ machine, and while a root htop session on /sshnet/GO704 shows 
akanadi etc running there, no kmail is showing.  Since it is this 
machines kmail that handles the fetching and sorting to the proper 
folders, this one should remain in operation to handle incoming mail. 
Cannot each session of kmail on the remote machines maintain its own 
read mail database, obviating any need for the remote session of kmail 
to have write perms, with that potential for a clash between kmails 
wrecking the whole party?

That means that I would have to do a session of mark all read to keep 
those databases in sync if I am at one of the other 3 machines, as a way 
to keep from having to read the whole, large fraction of a million 
messages each time I ran kmail on the remote machine from its own 
console.

Thanks Nic.

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>