On Friday Jan 17 2014, [email protected] wrote: > Hi, > > I have some Maildir questions I hope people can help with. I'm new to > Maildir and trying to figure out how to best set it up for use with > mu4e. > > My existing email workflow with alpine is about 30-40 folders that > things get CC'd to. Generally by person, sometimes by project. Pine > has best performance with smaller mailboxes, which is why I have many > of them. This made searching non-optimal (unless you know which > mailbox to start in). mu has best performance with few messages, > suggesting frequent archiving and setting ".noupdate". If I switch to > mu4e it seems like it'll be easiest/best if I reduce this to only one > (sent), or perhaps just a few that are 'active', and the rest with a > ".noupdate".
Hmmm, I'm using mu/mu4e with >50K messages, and it's very fast; I'm 30-40 mailboxes; and that works just fine (indexing takes ~ a second or so, and it's in the background anyway so I rarely even see it); searching is much faster % time mu find hello 0.05s user 0.03s system 13% cpu 0.591 total (with 2097 results) I'm not using .noupdate nor .noindex. I think you mentioned you had a bit over 100K message, do you see any performance problems? > Right now I have Maildir/INBOX and Maildir/foo and Maildir/bar and > many others. Is this even correct, or should it be ".foo" and ".bar"? That's just fine, no need to change. > To archive, do I just make Maildir/Archive-pre-2014 and move > everything inside it? Or is it Maildir/Archive-pre-2014.foo and > Maildir/Archive-pre-2014.bar, or Maildir/.archive/.2004/.foo, or > Maildir/.archive.2004.foo? I'd go with with the first one (you can use 'mu mkdir' to create maildirs). > If I email someone replying / following up to an old message, and > everything is now getting Fcc'd (or is the terminology "archived"?) to > "sent", does this break threading? How do people handle this? It seems > like threading might still work, since this thread says org-links work > even after things get archived > https://groups.google.com/forum/#!searchin/mu-discuss/archive$20/mu-discuss/GLDx_Udh5wo/ZCKvGEv8s50J Threading should still work, since it uses message-ids, which are constant even if you move. > Perhaps I'm overthinking this whole thing, but I'd be curious to hear > some best-practices for people with >100k emails that don't want to > wait 30 seconds for 'mu index' each time they update. 30 secs? That seems extremely long; after the first indexing, it only updates messages that have changed, ie. % time mu index indexing messages under /home/djcb/Maildir [/home/djcb/.mu/xapian] - processing mail; processed: 53325; updated/new: 0, cleaned-up: 0 cleaning up messages [/home/djcb/.mu/xapian] - processing mail; processed: 53339; updated/new: 0, cleaned-up: 0 elapsed: 1 second(s), ~ 53339 msg/s \ processing mail; processed: 53339; updated/new: 0, cleaned-up: 0 elapsed: 1 second(s), ~ 53339 msg/s /home/djcb/Sources/mu/mu/mu index 0.32s user 0.48s system 82% cpu 0.974 total This is on an i5-2500 CPU @ 3.30GHz with 8G memory, and Fedora 20 (kernel 3.12). Cheers, Dirk. -- Dirk-Jan C. Binnema Helsinki, Finland e:[email protected] w:www.djcbsoftware.nl pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C -- You received this message because you are subscribed to the Google Groups "mu-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
