From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <71e2269bef3018364eaf1a9ec3a4e4f1@quanstro.net> From: erik quanstrom Date: Sat, 15 Dec 2007 15:08:03 -0500 To: 9fans@cse.psu.edu Subject: Re: [9fans] imap4d and upas/fs In-Reply-To: <82c890d00712150945x4a023f91k5ba2678ae7a54fd9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 19f9fc28-ead3-11e9-9d60-3106f5b1d025 On Sat Dec 15 12:47:08 EST 2007, gabidiaz@gmail.com wrote: > hello > > oh, so upas/fs is the one which transforms the mailbox format to what > imap clients expect, i thought that would be done by the imap4d. . . > > thanks > > gabi not exactly. upas/fs turns its inport fmt into a directory containing 1 directory per message. this is the standard format that programs like imap4d, nedmail and acme Mail can understand. imap4d upas/fs's filesystem into imap4 commands. inport fmt can be an mbox, imap4 or pop3. i've added support for mail directories somewhat similar to mdir format. unfortunately that's not quite finished. p9p upas/fs can only read imap4 and the directory format is somewhat different. - erik