2 Dec
2015
2 Dec
'15
6:08 p.m.
Greetings all;
There are times when I would find it expedient to be able to run kmail on
one of the other machines I have trinity installed on, which isn't all
of them.
How hard would it be to setup a server on this machine, which has R14.0.2
on it, all working as a pop client from 2 external mail accounts I have,
referencing the nominally 12Gb of an email corpus here, so I could
access it from a kmail session on another machine, still on my local
network?
Thanks.
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>
3 Dec
3 Dec
11:06 a.m.
New subject: [trinity-users] imaping an existing kmail maild atabase
On Wednesday 02 December 2015 13:08:05 Gene Heskett wrote:
Greetings all;
Let me reword this to clarify what I'd like to do.
There are times when I would find it expedient to be
able to run kmail
on one of the other machines I have trinity installed on, which isn't
all of them.
Running kmail on the other machines as an imap client, talking to this
machine.
How hard would it be to setup a server on this
machine, which has
R14.0.2 on it, all working as a pop client from 2 external mail
accounts I have, referencing the nominally 12Gb of an email corpus
here, so I could access it from a kmail session on another machine,
still on my local network?
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?
The server, courier or dovecot, whatever might be recommended should
adapt itself to the kmail storage tree, not by fiddling with it. Sending
a reply could even be by std smtp, with the reply copy kept on the
individual machine as opposed to writing that back to kmails sent-mail
folder, although that would centralize that. In either event, amanda
will back it up every night.
Is this possible?
Thanks.
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>
11:56 a.m.
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
2:50 p.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Thursday 03 December 2015 06:56:53 deloptes wrote:
Thats quite a few gigabytes, and a duplication operation.
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.
Here, fetchmail hands off to procmail which delivers that which survives
the spamassassin an clam inspections, and delivers it delivers to 1 of
3 /var/spool/mail/mailfiles.
Me, a niece, and virii. inotifywait sees the file closing, and if its me
or the niece, sends kmail over the message buss flavor of the week, a
get the mail message. kmail goes and gets it, sorting it to the correct
folder, so the incoming mail lands in foldername/cur. And there are
about 40 some foldernames.
One copy of the email corpus should be sufficient. Can dovecot be trained
to go look in ~/Mail/*/cur?
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.
Its the really wrong that bothers me.
I hope this helps
Perhaps. I'll install it and the docs and do some reading.
Does dovecot do a broadcast so that clients can find it, or is a complex
kmail setup required at the client side?
Thanks.
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>
3:35 p.m.
Gene Heskett wrote:
all good so far - only regarding /var/spool/mail - this looks like local
mailbox in flat file format where you move the message using Kmail into
another mailbox and sub dir in maildir format
Well - this means make a backup and turn off your fetchers - play arround
and see what you'll get
The setup is really simple on Kmail client side - same/similar as pop3
account.
The challenge for me was to read all the exim/dovecot docs and bound all to
fit together. Since then it is a pleasure.
I hope this helps
regards
On Thursday 03 December 2015 06:56:53 deloptes wrote:
Thats quite a few gigabytes, and a duplication operation.
I would allocate a partition for mail in that case, but you'll save the same
amount of space in the user home.
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.
Here, fetchmail hands off to procmail which delivers that which survives
the spamassassin an clam inspections, and delivers it delivers to 1 of
3 /var/spool/mail/mailfiles.
Me, a niece, and virii. inotifywait sees the file closing, and if its me
or the niece, sends kmail over the message buss flavor of the week, a
get the mail message. kmail goes and gets it, sorting it to the correct
folder, so the incoming mail lands in foldername/cur. And there are
about 40 some foldernames.
One copy of the email corpus should be sufficient. Can dovecot be trained
to go look in ~/Mail/*/cur?
(if it has Mail/*/cur - it is a maildir format - which is faster and good)
What I don't understand why would you do this. You would probably better
rework all of this and end up with a single maildir
/var/spool/dovecot/<USERNAME>/Mail/
So in theory you could move your Mail dir to /var/spool/dovecot/<USERNAME>/
or point dovecot to your maildir.
I setup the template in exim to point to the users dovecot maildir, where it
gets served
MAILDIR_HOME_MAILDIR_LOCATION = /var/spool/dovecot/$local_part/Mail
and this is it
I think however you are still mixing up the local Mail provided by Kmail
default and the one that is offered by imap server. It took me also a while
back then to get it.
With imap you won't have to keep a local copy of the mail and you have
option to create filters etc and manage the individual mails.
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.
Its the really wrong that bothers me. I hope this helps
Perhaps. I'll install it and the docs and do some reading.
Does dovecot do a broadcast so that clients can find it, or is a complex
kmail setup required at the client side?
10:45 p.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Thursday 03 December 2015 06:56:53 deloptes wrote:
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
--
"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>
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
4 Dec
4 Dec
12:47 a.m.
Gene Heskett wrote:
mail_location = maildir:~/Mail
would be the correct one, as it says it is maildir format means anything
under Mail is your mail and imap will handle the rest
however this will impact Kmail if you try to read/write in same directory.
This is why my advise - rethink the whole setup.
Use
mail_location = maildir:/var/spool/dovecot/%u/Mail
or similar
You would use Kmail as imap client and not as local mailbox reader ;-)
Forget that local reader part - you will use whatever imap client to access
the mails from everywhere. This was your task correct?
log_path = /var/log/dovecot/dovecot.log
info_log_path = /var/log/dovecot/dovecot.info
etc
is set in /etc/dovecot/conf.d/10-logging.conf
regards
1:59 a.m.
New subject: [trinity-users] Re: Re: imaping an existing kmail maild atabase
On Thursday 03 December 2015 19:47:20 deloptes wrote:
Gene Heskett wrote:
I
should then remove those other defaults from 10-mail.conf then?
mail_location = maildir:~/Mail
would be the correct one, as it says it is maildir
format means
anything under Mail is your mail and imap will handle the rest
however this will impact Kmail if you try to read/write in same
directory. This is why my advise - rethink the whole setup.
This particular folder, TDE, is the only folder that would be setup for
write access because I keep sent-mail to this list in this folder, but
that can be redirected to sent-mail here, or even on the clients box.
I'd prefer here, but its convenience, not mandatory. Any other activity
would be read-only unless dovecot needs write just to mark a msg as
read.
Use
mail_location = maildir:/var/spool/dovecot/%u/Mail
or similar
You would use Kmail as imap client and not as local mailbox reader ;-)
Forget that local reader part - you will use whatever imap client to
access the mails from everywhere. This was your task correct?
log_path = /var/log/dovecot/dovecot.log
info_log_path = /var/log/dovecot/dovecot.info
etc
is set in /etc/dovecot/conf.d/10-logging.conf
These do not exist despite its running without apparent errors. Reading
the kmail handbook, the only imap service mentioned is kolab, so I
purged dovecot and installed kolabadmin since it appeared the rest of it
was installed. Unforch, the manpage is a 8 liner that doesn't say
squat, like what the heck is a "Dn" in the fill in the blanks
configurator?
So ATM that stuff has all been purged again, and I'm hoping someone can
tell me how to proceed. So far, when I've started kmail on one of the
remote machines and told it to check the mail, its stuck forever but not
locked up as it quits fairly normally, and my distribution switch's
led's say that no local traffic is being generated.
The terminal I start kmail in reports several kilobytes of errors for a
20 minute session trying to get a folder listing from this machine when
dovecot is running.
The first few are:
======================================
kmail
QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a
valid main component instead of a fake component, this usually means you
tried to call i18n related functions before your main component was
created. You should not do that since it most likely will not work
QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
"/usr/bin/kmail(19981)"
Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name
org.kde.nepomuk.services.nepomukstorage was not provided by any .service
files"
"/usr/bin/kmail(19981)" Soprano: "QLocalSocket::connectToServer: Invalid
name"
"/usr/bin/kmail(19981)"
Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name
org.kde.nepomuk.services.nepomukstorage was not provided by any .service
files"
"/usr/bin/kmail(19981)" Soprano: "QLocalSocket::connectToServer: Invalid
name"
"/usr/bin/kmail(19981)"
Soprano: "org.freedesktop.DBus.Error.ServiceUnknown - The name
org.kde.nepomuk.services.nepomukstorage was not provided by any .service
files"
"/usr/bin/kmail(19981)" Soprano: "QLocalSocket::connectToServer: Invalid
name"
kmail(19981) KMKernel::recoverDeadLetters: Autosave
directory "/home/gene/.kde/share/apps/kmail/autosave/cur" not found!
kmail(19981)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kmail(19981)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
gene@GO704:~$ kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
kmail(19981)/kdecore (KLibrary) kde4Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer a qt_plugin_instance
function.
kmail(19981)/kdecore (KLibrary) kde3Factory: The
library "/usr/lib/kde4/kcm_kmail.so" does not offer an
"init_kcm_kmail"
function.
[0xaf820af0] main input error: ES_OUT_RESET_PCR called
gpgconf: warning: can not open config file /home/gene/.gnupg/gpg.conf: No
such file or directory
gpgconf: warning: can not open config
file /home/gene/.gnupg/gpg-agent.conf: No such file or directory
gpgconf: warning: can not open config
file /home/gene/.gnupg/scdaemon.conf: No such file or directory
gpgconf: warning: can not open config file /home/gene/.gnupg/gpgsm.conf:
No such file or directory
gpgconf: warning: can not open config
file /home/gene/.gnupg/dirmngr.conf: No such file or directory
gpgconf: warning: can not open list
file /home/gene/.gnupg/dirmngr_ldapservers.conf: No such file or
directory
[0x8839430] main input error: ES_OUT_RESET_PCR called
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x62001b1
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x6200216
==============================
And it gets even more verbose but also repeats itself at length.
I feel the answer is likely dovecot related, and I'm just not holding my
mouth right, or something equally silly.
regards
Thanks.
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>
7:50 a.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
Am Donnerstag, 3. Dezember 2015 schrieb Gene Heskett:
On Thursday 03 December 2015 06:56:53 deloptes wrote:
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
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
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
10:59 a.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Friday 04 December 2015 02:50:02 Dr. Nikolaus Klepp wrote:
Am Donnerstag, 3. Dezember 2015 schrieb Gene Heskett:
That would imply, I believe, that I have the /sshnet/machine network
using sshfs set up to function both ways. Presently I do not but have
been trying to figure out a way to do that.
Refresh me on how I can make that work from the individual machines.
Currently its only from this machine /to/ the other 3. EG, I have a dir
called /sshnet here, that when the whole net is up and connected, looks
like this:
gene@coyote:/etc/dovecot/conf.d$ ls -l /sshnet
total 12
drwxr-xr-x 1 root root 4096 Nov 10 13:37 GO704
drwxr-xr-x 1 root root 4096 Sep 24 11:30 lathe
drwxr-xr-x 1 root root 4096 Sep 24 11:44 shop
gene@coyote:/etc/dovecot/conf.d$
And as me, gene, I can do anything to those machines that gene has perms
to do. But its not mirrored at those machines, something I would like
to do.
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>
On Thursday 03 December 2015 06:56:53 deloptes
wrote:
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 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 
11:25 a.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Friday 04 December 2015 10:59:52 Gene Heskett wrote:
On Friday 04 December 2015 02:50:02 Dr. Nikolaus Klepp
wrote:
Have you got openssh-client and openssh-server installed on all the machines?
Lisi
Am Donnerstag, 3. Dezember 2015 schrieb Gene
Heskett:
That would imply, I believe, that I have the /sshnet/machine network
using sshfs set up to function both ways. Presently I do not but have
been trying to figure out a way to do that.
Refresh me on how I can make that work from the individual machines.
Currently its only from this machine /to/ the other 3. EG, I have a dir
called /sshnet here, that when the whole net is up and connected, looks
like this:
gene@coyote:/etc/dovecot/conf.d$ ls -l /sshnet
total 12
drwxr-xr-x 1 root root 4096 Nov 10 13:37 GO704
drwxr-xr-x 1 root root 4096 Sep 24 11:30 lathe
drwxr-xr-x 1 root root 4096 Sep 24 11:44 shop
gene@coyote:/etc/dovecot/conf.d$
And as me, gene, I can do anything to those machines that gene has perms
to do. But its not mirrored at those machines, something I would like
to do.
Thanks Nic.
Cheers, Gene Heskett On Thursday 03 December 2015 06:56:53 deloptes
wrote:
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 > 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
11:39 a.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Friday 04 December 2015 02:50:02 Dr. Nikolaus Klepp wrote:
Am Donnerstag, 3. Dezember 2015 schrieb Gene Heskett:
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>
On Thursday 03 December 2015 06:56:53 deloptes
wrote:
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 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
11:49 a.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Friday 04 December 2015 06:25:10 Lisi Reisz wrote:
On Friday 04 December 2015 10:59:52 Gene Heskett
wrote:
On the machine (GO704.coyote.den) I am currently trying to work with,
yes. And likely on all 3, which would include lathe.coyote.den and
shop.coyote.den. If not, its certainly fixable.
And the keys have been imported, apparently w/o error on that machine,
but that was not done from its own console, it was done via an
"ssh -Y GO704" login from here on coyote. I think that makes a
difference.
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>
On Friday 04 December 2015 02:50:02 Dr. Nikolaus
Klepp wrote:
Have you got openssh-client and openssh-server installed on all the
machines?
Lisi Am Donnerstag, 3. Dezember 2015 schrieb Gene
Heskett:
That would imply, I believe, that I have the /sshnet/machine network
using sshfs set up to function both ways. Presently I do not but
have been trying to figure out a way to do that.
Refresh me on how I can make that work from the individual machines.
Currently its only from this machine /to/ the other 3. EG, I have a
dir called /sshnet here, that when the whole net is up and
connected, looks like this:
gene@coyote:/etc/dovecot/conf.d$ ls -l /sshnet
total 12
drwxr-xr-x 1 root root 4096 Nov 10 13:37 GO704
drwxr-xr-x 1 root root 4096 Sep 24 11:30 lathe
drwxr-xr-x 1 root root 4096 Sep 24 11:44 shop
gene@coyote:/etc/dovecot/conf.d$
And as me, gene, I can do anything to those machines that gene has
perms to do. But its not mirrored at those machines, something I
would like to do.
Thanks Nic.
Cheers, 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
12:20 p.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
Am Freitag, 4. Dezember 2015 schrieb Gene Heskett:
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
Hi Gene!
There is a misunderstanding I think. I was assuming you use this scenario:
- you have a machine that fetches your mail. On that machine you do nothing, you are not
logged in, kmail is not running. let's call it "remote"
- you sit in front of a second machine, where TDE is running, but not kmail. let's
call it "here"
- you do "$ ssh -X gene@remote /opt/trinity/bin/kmail". kmail (running on
"remote") sends the GUI over to "here"
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
3:39 p.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Friday 04 December 2015 07:20:20 Dr. Nikolaus Klepp wrote:
Am Freitag, 4. Dezember 2015 schrieb Gene Heskett:
No, this machine does it all, and kmail runs 24/7 on this machine as it
is what gets the mail that procmail usually delivers
to /var/spool/mail/gene, on this machine. Because kmail is single
threaded, it has huge freezes of the user gui, including the composer,
while its going out on the net to check/fetch new mail from the 2
mailservers I have access to. So all that has been offloaded to a
fetchmail/procmail setup. So all kmail has to do is go get it from the
local /var/spool/mail/mailfile, sort it and write it to the correct
folder. This its can do in a fraction of a second, reducing the frozen
time from 20 or more seconds to just noticeable.
Then, while kmail remains running to do all that, I want to access what
it has pulled in, from a 2nd session of kmail running from the remote
machine while I am at its keyboard/monitor.
As I see it, its one of telling the remote copy where the email corpus
is, and some method of file locking to keep the two copies from stepping
on each others toes.
I thought maybe dovecot could serve it, but have not been able to make an
imap setup connect, and with no logs being made by dovecot, no means of
determining why they can't connect.
Dovecot has currently been purged, but that is of course fixable, if I
knew what the heck I was doing, but I've no previous experience with
dovecot.
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
Hi Gene!
There is a misunderstanding I think. I was assuming you use this
scenario:
- you have a machine that fetches your mail. On that machine you do
nothing, you are not logged in, kmail is not running. let's call it
"remote" - you sit in front of a second machine, where TDE is
running, but not
kmail. let's call it "here"
I would if I was 'there' yes.
- you do "$ ssh -X gene@remote
/opt/trinity/bin/kmail". kmail (running
on "remote") sends the GUI over to "here"
But as the error comes back, kmail is already running and objects.
So what I want is to serve up the kmail email corpus that exists on this
machine, with a large fraction of a million mailfiles in 42 directories,
using something like dovecot, to a second copy of kmail running on the
remote machine I am working with/on from its own keyboard at the
instant, without shutting down the copy of kmail running on this machine
that is doing all the incoming mail housekeeping. Sure, I can't be two
places at once, but the scripts that drive all this never sleep, even if
I am. That means new mail needs to be processed anytime it arrives,
regardless of which machine I am on at the instant. Shutting down this
copy of kmail means no new mail will be processed until its restarted.
Shutting it down so dcop has no receiver eventually constipates dcop and
that seems to take a reboot to fix.
And I don't want to have dovecot make a copy of whats here just to get it
all in one directory for dovecots convenience. One folder alone, the
biggest, is at 90,000 msgs now. And kmail takes about 10 seconds to
find a new message in all that. I do expire the majority of the folders
in a week or so, but keep several for archival purposes too.
I can reinstall dovecot, and set the source path up as it was before, but
I think my 'failure to communicate' from the remote machine was in not
telling dovecot who might come calling.
So, how should I proceed? Or should I continue to come to this machine
to do all the email?
Nik
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>
5 p.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
Hi Gene!
Let's see if I get it right this time:
incomming mail:
external mailserver --> fetchmail --> local mailbox --> kmail --> kmail
mailbox in ~
You have kmail running 24/7, because it should transfer "local mailbox --> kmail
--> kmail mailbox in ~"
If this is correct, then imap will not be your solution, because there is no mailbox with
mail in it, that a imap sever could deliver. Reason: "kmail mailbox in ~" is not
compatible with any imap server.
The easy solution:
Do not run kmail 24/7, but only when you want to use email on the machine in front of you.
Then you can use kmail over the ssh, no more work needed.
The more complex solution:
incomming mail:
external mailserver --> fetchmail --> local mailbox --> dovecot --> local
dovecot mailbox in ~
kmail has to be configured for imap only, that has to be done for all kmails on all other
machines that would like access to the mails. Be aware that there was an error with kmail
and imap some time ago, I don't know if it still exists.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office(a)klepp.biz
Hi Gene!
There is a misunderstanding I think. I was assuming you use this
scenario:
- you have a machine that fetches your mail. On that machine you do
nothing, you are not logged in, kmail is not running. let's call it
"remote"
No, this machine does it all, and kmail runs 24/7 on this machine as it
is what gets the mail that procmail usually delivers
to /var/spool/mail/gene, on this machine. Because kmail is single
threaded, it has huge freezes of the user gui, including the composer,
while its going out on the net to check/fetch new mail from the 2
mailservers I have access to. So all that has been offloaded to a
fetchmail/procmail setup. So all kmail has to do is go get it from the
local /var/spool/mail/mailfile, sort it and write it to the correct
folder. This its can do in a fraction of a second, reducing the frozen
time from 20 or more seconds to just noticeable.
Then, while kmail remains running to do all that, I want to access what
it has pulled in, from a 2nd session of kmail running from the remote
machine while I am at its keyboard/monitor.
As I see it, its one of telling the remote copy where the email corpus
is, and some method of file locking to keep the two copies from stepping
on each others toes.
I thought maybe dovecot could serve it, but have not been able to make an
imap setup connect, and with no logs being made by dovecot, no means of
determining why they can't connect.
Dovecot has currently been purged, but that is of course fixable, if I
knew what the heck I was doing, but I've no previous experience with
dovecot.
- you sit in front of a second machine, where TDE
is running, but not
kmail. let's call it "here"
I would if I was 'there' yes.
- you do "$ ssh -X gene@remote
/opt/trinity/bin/kmail". kmail (running
on "remote") sends the GUI over to "here"
But as the error comes back, kmail is already running and objects.
So what I want is to serve up the kmail email corpus that exists on this
machine, with a large fraction of a million mailfiles in 42 directories,
using something like dovecot, to a second copy of kmail running on the
remote machine I am working with/on from its own keyboard at the
instant, without shutting down the copy of kmail running on this machine
that is doing all the incoming mail housekeeping. Sure, I can't be two
places at once, but the scripts that drive all this never sleep, even if
I am. That means new mail needs to be processed anytime it arrives,
regardless of which machine I am on at the instant. Shutting down this
copy of kmail means no new mail will be processed until its restarted.
Shutting it down so dcop has no receiver eventually constipates dcop and
that seems to take a reboot to fix.
And I don't want to have dovecot make a copy of whats here just to get it
all in one directory for dovecots convenience. One folder alone, the
biggest, is at 90,000 msgs now. And kmail takes about 10 seconds to
find a new message in all that. I do expire the majority of the folders
in a week or so, but keep several for archival purposes too.
I can reinstall dovecot, and set the source path up as it was before, but
I think my 'failure to communicate' from the remote machine was in not
telling dovecot who might come calling.
So, how should I proceed? Or should I continue to come to this machine
to do all the email?
Nik
Cheers, Gene Heskett
5:25 p.m.
Gene Heskett wrote:
And I don't want to have dovecot make a copy of whats here just to get it
all in one directory for dovecots convenience. One folder alone, the
biggest, is at 90,000 msgs now. And kmail takes about 10 seconds to
find a new message in all that. I do expire the majority of the folders
in a week or so, but keep several for archival purposes too.
I can reinstall dovecot, and set the source path up as it was before, but
I think my 'failure to communicate' from the remote machine was in not
telling dovecot who might come calling.
Gene,
again you are mixing the local mail directory on the machine you have the
mail (~/Mail). This is local mailbox - it is meant to be for end user.
What you are trying to do is serve the mailbox to other clients. For this
the best would be to movie your ~/Mail in /var/spool/dovecot/%u/Mail and
configure your KMail on all machines to use IMAP to access the mail via
user <user>. You just replace <user> with whatever user
I think it is straight forward and simple as it is supposed to be used that
way.
You can also protect that with custom SSL and configure IMAP to use your
certs, which will round it up to professional level.
I hope this helps
regards
5:32 p.m.
New subject: [trinity-users] Re: imaping an existing kmail maild atabase
On Friday 04 December 2015 12:00:54 Dr. Nikolaus Klepp wrote:
Hi Gene!
Let's see if I get it right this time:
incomming mail:
external mailserver --> fetchmail --> local mailbox --> kmail -->
kmail mailbox in ~
You have kmail running 24/7, because it should transfer "local mailbox
--> kmail --> kmail mailbox in ~"
If this is correct, then imap will not be your solution, because there
is no mailbox with mail in it, that a imap sever could deliver.
Reason: "kmail mailbox in ~" is not compatible with any imap server.
The easy solution:
Do not run kmail 24/7, but only when you want to use email on the
machine in front of you. Then you can use kmail over the ssh, no more
work needed.
That would constipate dcop, eventually crashing this machine.>
The more complex solution:
incomming mail:
external mailserver --> fetchmail --> local mailbox --> dovecot -->
local dovecot mailbox in ~ kmail has to be configured for imap only,
that has to be done for all kmails on all other machines that would
like access to the mails. Be aware that there was an error with kmail
and imap some time ago, I don't know if it still exists.
Nik
I see. But does that not also imply that I would have to write a script
that would merge each "cur" directory's contents back into a file, say
10 at a time, write that file to the spool dir, wait for sieve or
pidgeonhole to sort and process it for dovecots use?
I can easily see that taking most of a day, while fetchmail is shut down
so I could sort the files to make that merge, assuming I can get the
sorter properly programmed in the first place.
That sounds rather like the present configuration will need to be carried
on till I am done. No clue when that will be. :(
But it also begs the question as to why does dovecot not report this
violation of its rules when I tell the server
in /etc/dovecot/10-mail.conf that the mail its to serve resides
at /home/gene/Mail/*/cur? And so that is the only place it looks, the
additional stuff defining sent/junk etc has been commented out
of /etc/dovecot/15-mailbox.conf?
That, as has been said, doesn't compute. It won't launch other than as
root, so it can make a logfile any place it wants, but it doesn't in the
usual suspects path, /var/log/.
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>
3092
days inactive
3094
days old
17 comments
4 participants
participants (4)
-
deloptes -
Dr. Nikolaus Klepp -
Gene Heskett -
Lisi Reisz