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