Hi,
I've been looking at James as a replacement for our legacy
Windows-based email setup, at which point my hopes of a maildir-based
message store were dashed (because of a filesystem reserved character
(colon) in the spec).
Moving to maildir appealed to me because the legacy software uses mbox
but the local spool is now up to nearly 2GB and the risk of corruption
is starting to bother me (well, that and the next Windows update could
render that abandonware unusable). I daresay it would improve
performance somewhat as well.
I've had a look at the source, and from what I can see, the edits
required to use an alternative character (eg semicolon) in message
file naming only amount to a couple of lines, or a bit more to make it
a configurable option.
I'm ready to try building and testing a patch myself, but before I
fling myself into that I felt it sensible to ask:
1. Has this been proposed before, and if so, are there technical
reasons why it was decided against? (No sense in going over old ground)
2. Should I be looking further afield in the source than the specific
Maildir code, i.e. the contents of [1], for potential conflicts? (I
guess in theory the answer should be "no", but y'all know the codebase
better than I!)
Any advice would be very welcome.
Regards,
Robin Bankhead
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
