* Gabriel Diaz <[EMAIL PROTECTED]> wrote: > > Just downloading isn't enough, would require sync back (and that's > > gonna be difficult). And having to download several Gig is not > > an option for me. > > > > I don't know what kind of storages are you talking about,
Evrything that can store mail-like messages. > but the way > is done by the mail system is just a read-fs and a smtp client, you do > not write into /mail/fs/mbox to send mail :-?, Ugh, that's a *big* blocker for me. I *need* to write into certain boxes. > > It has to be an synthetic filesystem, since the server should do > > most things. As already said: clients should only speak mailfs-ng, > > and not doing their own storage handling anymore. This also includes > > things lke filtering, searching, etc. > > why do not start with what we have now? making upasfs to use the > remote storage, making it able to order mailbox and move messages > between them and those things? I just want to make some clean concepts, and then let's see if mailfs is enough or could be easily extendet. But my feeling is: mailfs won't be enough - I need much more functionality. Remember: mailfs-ng should handle all the mail storage for commonly used MUAs (eg. Mozilla or Mutt) - the individual MUA should do nothing more than just operating within mailfs-ng. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------
