Hi, I would not worry about windows here. Maildir was not designed to work at windows, so why should we try to do so ? IMHO, we should just not support windows with this backend.
Bye, Norman 2010/8/15 Tim-Christian Mundt <[email protected]>: > Eric, > > Maildir is indeed - originally - not intended for Windows. I don't know > of any other implementation supporting it. There is one main blocker: > Windows doesn't allow colons in filenames. By instead using a different > character (e.g. ";") we could support Maildir. Another problem could be > that rename is not atomic on Windows and thus could leave the system > with an inconsistent state. Anyways, it would work. I'll add Windows > support and we should maybe add a note about this problem so that people > are warned. James has so many nice(r) backends people can use on Win. At > least from my point of view Maildir was mainly added to make migration > from or interoperation with other software easier. > Our Maildir is Maildir++, yes. We do not yet have quotas, however. > > Best, > Tim > > Am Samstag, den 14.08.2010, 12:09 +0200 schrieb Eric Charles: >> btw, this is the first james store not portable on windows. >> Did you discover any maildir ports on windows during your GSOC ? >> Can we consider your impl as a Maildir++ one >> (http://en.wikipedia.org/wiki/Maildir) ? >> Tks, >> Eric >> >> >> On 08/14/2010 11:46 AM, Eric Charles wrote: >> > Hi Tim, >> > >> > I checked-out, compiled, deployed and tested without any problem. >> > Your MailDir store is working :) and generates the cur, new, tmp in my >> > user directory. >> > >> > Last but not least, your code is really well structured and readable. >> > You really made great job! >> > >> > Btw, we knew that James architecture was great open to alternative >> > store, and you proved it. >> > >> > Quick comments: >> > - I renamed /var/james/Maildirs/%user to ../var/Maildirs/%user (maybe >> > should be file://var/...) to have relative paths to james deployment >> > (more coherent with other stores) >> > - I configured with JDBCDomainList and defined [email protected] >> > user. The created dir is "/var/Maildirs/eric/...". We may have user >> > clash if let's say [email protected] is defined. >> > >> > Tks, >> > >> > Eric >> > >> > >> > On 08/13/2010 10:48 PM, Tim-Christian Mundt wrote: >> >> Hi guys, >> >> >> >> last Monday was "pencils down" for the Google Summer of Code project. >> >> The days till next Monday - the final dead line - are meant as time for >> >> wrap up, testing, documentation and so on. >> >> >> >> Well, the new Maildir backend works. Until now it has just one parameter >> >> which is the path (with variables) where the Maildir folders should >> >> reside. It works with pre-existing data from other servers or can build >> >> up the data from scratch. The functional tests work with the exception >> >> of "testSearchCombinations*" which is due to the fact that Maildir only >> >> stores the _current_ date as internal date, not the one that is given >> >> during append (which is perfectly valid for the RFC but not for the >> >> tests). >> >> >> >> The code is attached to this mail and you can also find it in my >> >> repository: svn://tim-erwin.de/maildir/trunk/maildir >> >> Although GSOC is officially over, I'm still open to c&c and as soon as >> >> the code is in the James SVN it's open to be teared apart anyways. >> >> >> >> Thanks for having me in this project. Special thanks to Norman who has >> >> been a very helpful and nice to work with mentor. I'm sure this will not >> >> be the end of my James activities. >> >> >> >> Regards >> >> Tim >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
