Converting MH to KMail (maildir)
I currently am using Sylpheed Claws that uses MH folders. While I am
happy with Sylpheed Claws, I may want to use KMail, but I don't want to
have to define all my directories individually. I have been using Linux
at home for several years, having used exmh, and converted to Sylpheed
Claws a while back. I switched to Sylpheed when there was a serious
problem with exmh. I have nearly 500 mail folders that I have set up
over the years.
1. is there an existing utility (script or otherwise) that will update
MH folders to maildir?
2. If not, what mechanism does KMail use to recognize maildir folders,
other than the existence of the cur, tmp, and new subdirectories?
--
Jerry Feldman
On Sunday 23 May 2004 16.30, Jerry Feldman wrote:
I currently am using Sylpheed Claws that uses MH folders. While I am happy with Sylpheed Claws, I may want to use KMail, but I don't want to have to define all my directories individually. I have been using Linux at home for several years, having used exmh, and converted to Sylpheed Claws a while back. I switched to Sylpheed when there was a serious problem with exmh. I have nearly 500 mail folders that I have set up over the years.
1. is there an existing utility (script or otherwise) that will update MH folders to maildir?
2. If not, what mechanism does KMail use to recognize maildir folders, other than the existence of the cur, tmp, and new subdirectories?
I can't find anything specific to maildir, but sylpheed has an "export to mbox" feature, and kmail can handle mbox files. In kmail, you can then convert from mbox to maildir
On Sunday 23 May 2004 09:45, Anders Johansson wrote:
On Sunday 23 May 2004 16.30, Jerry Feldman wrote:
I currently am using Sylpheed Claws that uses MH folders. While I am happy with Sylpheed Claws, I may want to use KMail, but I don't want to have to define all my directories individually. I have been using Linux at home for several years, having used exmh, and converted to Sylpheed Claws a while back. I switched to Sylpheed when there was a serious problem with exmh. I have nearly 500 mail folders that I have set up over the years.
1. is there an existing utility (script or otherwise) that will update MH folders to maildir?
2. If not, what mechanism does KMail use to recognize maildir folders, other than the existence of the cur, tmp, and new subdirectories?
I can't find anything specific to maildir, but sylpheed has an "export to mbox" feature, and kmail can handle mbox files. In kmail, you can then convert from mbox to maildir
I used kmail to convert mbox files to maildir and had to do each file individually. Time consuming and error prone! If someone knows how to do the whole thing in an automated fashion it could be a big help! (Not to me, I've already done it.) -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Sunday 23 May 2004 16.55, Robert Paulsen wrote:
I used kmail to convert mbox files to maildir and had to do each file individually. Time consuming and error prone!
If someone knows how to do the whole thing in an automated fashion it could be a big help! (Not to me, I've already done it.)
I posted this link the last time someone asked about that, perhaps you missed it http://batleth.sapienti-sat.org/projects/mb2md/
On Sunday 23 May 2004 09:58, Anders Johansson wrote:
On Sunday 23 May 2004 16.55, Robert Paulsen wrote:
I used kmail to convert mbox files to maildir and had to do each file individually. Time consuming and error prone!
If someone knows how to do the whole thing in an automated fashion it could be a big help! (Not to me, I've already done it.)
I posted this link the last time someone asked about that, perhaps you missed it
Yup -- missed it before. Thanks -- Robert C. Paulsen, Jr. robert@paulsenonline.net
On Sun, 23 May 2004 16:45:18 +0200
Anders Johansson
I can't find anything specific to maildir, but sylpheed has an "export to mbox" feature, and kmail can handle mbox files. In kmail, you can then convert from mbox to maildir
Yes, but that could also be tedious since I have nearly 500 mh
directories. I can easily write a script to create the maildir
subdirectories (such as new, cur, tmp). The issue is to create the index
files:
eg.
.inbox.index and .inbox.index.ids
I've found a couple of tools:
Sylpheed2Maildir and mh2maildir transformator
These are apparently simple shell scripts.
The other issue is to convert my .procmailrc. Currently it delivers
email to the appropriate mh directory using rcvstore, but this should be
relatively simple since maildir is designed to handle multiple
concurrent inputs.
--
Jerry Feldman
* Jerry Feldman
Yes, but that could also be tedious since I have nearly 500 mh directories. I can easily write a script to create the maildir subdirectories (such as new, cur, tmp). The issue is to create the index files: eg. .inbox.index and .inbox.index.ids
No, the index files are not an issue. KMail will recreate them automagically. In face, when the kmail directory display becomes corrupted, the solution is to delete the index files. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711
On Sun, 23 May 2004 10:39:19 -0500
Patrick Shanahan
No, the index files are not an issue. KMail will recreate them automagically. In face, when the kmail directory display becomes corrupted, the solution is to delete the index files. You are correct. I tried the script, sylpheed2maildir, which did a reasonably good job. I created the Kmail ~/Mail directory on my laptop so I could test kmail without affecting Sylpheed. This way I can evaluate KMail and make a decision.
The tools are from: http://kmail.kde.org/tools.html.
Additionally, WRT: Procmail. I think it might be better to use kmail's
internal filters since converting from the way I currently use procmail
to deliver into the specific folder. This will cause problems in kmail.
--
Jerry Feldman
Hi All I was working on a website and suddenly had to reboot due to a problem with the kernel. I have this in my warn log May 23 19:27:22 dev kernel: Bad page state at free_hot_cold_page (in process 'httpd2-prefork', page c11c7d60) May 23 19:27:22 dev kernel: flags:0x2002001c mapping:cf9555e4 mapped:0 count:0 private:0x00000000 May 23 19:27:22 dev kernel: Backtrace: May 23 19:27:22 dev kernel: Call Trace: May 23 19:27:22 dev kernel: [bad_page+92/144] bad_page+0x5c/0x90 May 23 19:27:22 dev kernel: [<c013d45c>] bad_page+0x5c/0x90 May 23 19:27:22 dev kernel: [free_hot_cold_page+97/240] free_hot_cold_page+0x61/0xf0 May 23 19:27:22 dev kernel: [<c013d781>] free_hot_cold_page+0x61/0xf0 May 23 19:27:22 dev kernel: [unmap_page_range+423/688] unmap_page_range+0x1a7/0x2b0 May 23 19:27:22 dev kernel: [<c0146317>] unmap_page_range+0x1a7/0x2b0 May 23 19:27:22 dev kernel: [unmap_vmas+299/640] unmap_vmas+0x12b/0x280 May 23 19:27:22 dev kernel: [<c014654b>] unmap_vmas+0x12b/0x280 May 23 19:27:22 dev kernel: [exit_mmap+89/384] exit_mmap+0x59/0x180 May 23 19:27:22 dev kernel: [<c0148a49>] exit_mmap+0x59/0x180 May 23 19:27:22 dev kernel: [mmput+69/96] mmput+0x45/0x60 May 23 19:27:22 dev kernel: [<c011de35>] mmput+0x45/0x60 May 23 19:27:22 dev kernel: [do_exit+305/2576] do_exit+0x131/0xa10 May 23 19:27:22 dev kernel: [<c01213d1>] do_exit+0x131/0xa10 May 23 19:27:22 dev kernel: [__dequeue_signal+293/384] __dequeue_signal+0x125/0x180 May 23 19:27:22 dev kernel: [<c0127d45>] __dequeue_signal+0x125/0x180 May 23 19:27:22 dev kernel: [do_group_exit+39/112] do_group_exit+0x27/0x70 May 23 19:27:22 dev kernel: [<c0121cd7>] do_group_exit+0x27/0x70 May 23 19:27:23 dev kernel: [get_signal_to_deliver+517/736] get_signal_to_deliver+0x205/0x2e0 May 23 19:27:23 dev kernel: [<c0129c85>] get_signal_to_deliver+0x205/0x2e0 May 23 19:27:23 dev kernel: [do_signal+94/1488] do_signal+0x5e/0x5d0 May 23 19:27:23 dev kernel: [<c01071ae>] do_signal+0x5e/0x5d0 May 23 19:27:23 dev kernel: [kill_proc_info+33/48] kill_proc_info+0x21/0x30 May 23 19:27:23 dev kernel: [<c0128611>] kill_proc_info+0x21/0x30 May 23 19:27:23 dev kernel: [__crc_cdev_put+3507986/7473407] search_by_key+0x71d/0x1210 [reiserfs] May 23 19:27:23 dev kernel: [<e28741ed>] search_by_key+0x71d/0x1210 [reiserfs] May 23 19:27:23 dev kernel: [convert_fxsr_from_user+21/240] convert_fxsr_from_user+0x15/0xf0 May 23 19:27:23 dev kernel: [<c010ebc5>] convert_fxsr_from_user+0x15/0xf0 May 23 19:27:23 dev kernel: [restore_i387+201/208] restore_i387+0xc9/0xd0 May 23 19:27:23 dev kernel: [<c010ef59>] restore_i387+0xc9/0xd0 May 23 19:27:23 dev kernel: [restore_sigcontext+286/320] restore_sigcontext+0x11e/0x140 May 23 19:27:23 dev kernel: [<c010789e>] restore_sigcontext+0x11e/0x140 May 23 19:27:23 dev kernel: [sys_sigreturn+148/176] sys_sigreturn+0x94/0xb0 May 23 19:27:23 dev kernel: [<c0107a24>] sys_sigreturn+0x94/0xb0 May 23 19:27:23 dev kernel: [do_notify_resume+55/64] do_notify_resume+0x37/0x40 May 23 19:27:23 dev kernel: [<c0107757>] do_notify_resume+0x37/0x40 May 23 19:27:23 dev kernel: [work_notifysig+19/21] work_notifysig+0x13/0x15 May 23 19:27:23 dev kernel: [<c0107e7e>] work_notifysig+0x13/0x15 May 23 19:27:23 dev kernel: May 23 19:27:23 dev kernel: Trying to fix it up, but a reboot is needed May 23 19:28:34 dev kernel: Unable to handle kernel paging request at virtual address 00200200 May 23 19:28:34 dev kernel: printing eip: May 23 19:28:34 dev kernel: c013dae6 May 23 19:28:34 dev kernel: *pde = 00000000 May 23 19:28:34 dev kernel: Oops: 0002 [#1] May 23 19:28:34 dev kernel: CPU: 0 May 23 19:28:34 dev kernel: EIP: 0060:[buffered_rmqueue+150/656] Not tainted May 23 19:28:34 dev kernel: EIP: 0060:[<c013dae6>] Not tainted May 23 19:28:34 dev kernel: EFLAGS: 00010002 (2.6.4-54.5-default) May 23 19:28:34 dev kernel: EIP is at buffered_rmqueue+0x96/0x290 May 23 19:28:34 dev kernel: eax: c11c7d70 ebx: c0342418 ecx: 00200200 edx: 00100100 May 23 19:28:34 dev kernel: esi: 0000015d edi: c03424e8 ebp: 00000246 esp: dbe0ddb0 May 23 19:28:34 dev kernel: ds: 007b es: 007b ss: 0068 May 23 19:28:35 dev kernel: Process shutdown (pid: 24078, threadinfo=dbe0c000 task=ddec78b0) May 23 19:28:35 dev kernel: Stack: 00020000 00000002 dff19b80 dbe0ddfc c11c7d60 00000000 00000000 c0342418 May 23 19:28:35 dev kernel: 0000015d dbe0df60 00000ff1 c013dd8b 00000000 00000000 ddec78b0 00000010 May 23 19:28:35 dev kernel: c0342668 00000000 000000d2 c01cc04f 00000000 0000001f dbe0df60 00000ff1 May 23 19:28:35 dev kernel: Call Trace: May 23 19:28:35 dev kernel: [__alloc_pages+171/864] __alloc_pages+0xab/0x360 May 23 19:28:35 dev kernel: [<c013dd8b>] __alloc_pages+0xab/0x360 May 23 19:28:35 dev kernel: [selinux_bprm_set_security+287/368] selinux_bprm_set_security+0x11f/0x170 May 23 19:28:35 dev kernel: [<c01cc04f>] selinux_bprm_set_security+0x11f/0x170 May 23 19:28:35 dev kernel: [copy_strings+554/608] copy_strings+0x22a/0x260 May 23 19:28:35 dev kernel: [<c015ef0a>] copy_strings+0x22a/0x260 May 23 19:28:35 dev kernel: [copy_strings_kernel+24/32] copy_strings_kernel+0x18/0x20 May 23 19:28:35 dev kernel: [<c015ef58>] copy_strings_kernel+0x18/0x20 May 23 19:28:35 dev kernel: [do_execve+329/592] do_execve+0x149/0x250 May 23 19:28:35 dev kernel: [<c015f0a9>] do_execve+0x149/0x250 May 23 19:28:35 dev kernel: [sys_execve+42/96] sys_execve+0x2a/0x60 May 23 19:28:35 dev kernel: [<c010663a>] sys_execve+0x2a/0x60 May 23 19:28:35 dev kernel: [sysenter_past_esp+82/121] sysenter_past_esp+0x52/0x79 May 23 19:28:35 dev kernel: [<c0107dc9>] sysenter_past_esp+0x52/0x79 May 23 19:28:35 dev kernel: May 23 19:28:35 dev kernel: Code: 89 11 89 4a 04 c7 00 00 01 10 00 c7 40 04 00 02 20 00 8b 07 Anyone got any idea on whats going on? Thanks Mark
On Sunday 23 May 2004 19.42, Mark Evans wrote:
Anyone got any idea on whats going on?
For bug reports on kernel crashes, you should report it to http://www.suse.com/cgi-bin/feedback.cgi And include the stacktrace in your report Note that suse's kernels are so heavily patched, for example in 9.1 they use an entirely different memory managent subsystem (which seems to be involved here, considering that the stack trace is full of memory management functions), that reporting to suse is probably a better idea than reporting to the linux kernel mailing list
* Jerry Feldman
The tools are from: http://kmail.kde.org/tools.html.
Additionally, WRT: Procmail. I think it might be better to use kmail's internal filters since converting from the way I currently use procmail to deliver into the specific folder. This will cause problems in kmail.
Yes, for filtering to directories. Procmail can still be used for spamassassin and virus-scan, etc, and you can deliver the result of these scans to mbox directories under /var/mail/.... and import them as additional acc'ts into kmail w/o a problem. My wife likes to do her mail on kmail on my computer and I handle it that way. Then she plays with her paf, etc, on her windoz 98se box. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711
On a related note .... Does anyone know the mail format used by the old XFmail program? What is the format used by the Mozilla reader? Is it possible to convert an old XFmail mailbox to one readable by Mozilla? Where does Mozilla put its mail folders? Thanks john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
BTW: I forgot to say thanks for the feedback, and I also need to decide whether I want to do this or not.
participants (6)
-
Anders Johansson
-
Jerry Feldman
-
John N. Alegre
-
Mark Evans
-
Patrick Shanahan
-
Robert Paulsen