From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] RFC: MailFS-NG
Date: Tue, 8 Jan 2008 18:44:53 +0100 [thread overview]
Message-ID: <20080108174453.GA10899@nibiru.local> (raw)
In-Reply-To: <82c890d00801080004s6f191fcbsdfa6f870e585edef@mail.gmail.com>
* Gabriel Diaz <gabidiaz@gmail.com> 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/
---------------------------------------------------------------------
next prev parent reply other threads:[~2008-01-08 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 20:53 Enrico Weigelt
2008-01-07 17:01 ` Gabriel Diaz
2008-01-07 18:42 ` Enrico Weigelt
2008-01-08 8:04 ` Gabriel Diaz
2008-01-08 17:44 ` Enrico Weigelt [this message]
2008-01-09 6:20 ` Gabriel Diaz Lopez de la Llave
2008-01-10 2:38 ` Enrico Weigelt
2008-01-09 6:38 ` ron minnich
2008-01-07 18:05 ` Francisco J Ballesteros
[not found] ` <f4d8fa40801100520v6560731dnfd481b4e80237d7d@mail.gmail.com>
2008-01-10 13:39 ` Fwd: " hiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080108174453.GA10899@nibiru.local \
--to=weigelt@metux.de \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).