9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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: Thu, 10 Jan 2008 03:38:16 +0100	[thread overview]
Message-ID: <20080110023816.GB26347@nibiru.local> (raw)
In-Reply-To: <28198663-0D8D-467B-A89B-96FDC8647C3B@9grid.es>

* Gabriel Diaz Lopez de la Llave <gdiaz@9grid.es> wrote:

> isn't that just mail messages? you can transform whatever you need to  
> look like a mail message, but i don't think thats the way to go. . .  

Well, evrything that fits into rfc2822 can be served by mailfs-ng ;-P
Where the messages actually coming from should not be relevant to
the client.

The client also needs an generic interface for configuring storages 
(ie. subscribing to imap folders, feeds, ...). Managing namespaces
and caching/sync'ing would also be nice. But evrysthing step by step ...

> it is like make everything to look like a webpage, that way you only  
> need a browser :?

in a way ... ;-o

> >Ugh, that's a *big* blocker for me. I *need* to write into
> >certain boxes.
> >
> 
> i would love upasfs to be able to move/copy messages between mailboxes  
> and the like, i don't see the advantage of creating new mails with it

can upasfs be extended for my requirements ?

> >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.
> >
> 
> and how do you plan to make mozilla or mutt talk to that fs server?  

I'll rewrite the appropriate parts (same as I currently doing
w/ bookmark handling).

> wouldn't be easier to use imap? 

maybe easier, but doesn't fit my needs.


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/
---------------------------------------------------------------------


  reply	other threads:[~2008-01-10  2:38 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
2008-01-09  6:20         ` Gabriel Diaz Lopez de la Llave
2008-01-10  2:38           ` Enrico Weigelt [this message]
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=20080110023816.GB26347@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).