From: dtk <d.t.k@gmx.de>
To: Ruthard Baudach <rthrd@web.de>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Maildir support
Date: Mon, 11 Apr 2011 23:58:26 +0200 [thread overview]
Message-ID: <1302558306-sup-4515@minibox> (raw)
In-Reply-To: <1302526640-sup-7095@PrxServer3>
Hi Ruthard,
thanks for your explanation!
Excerpts from Ruthard Baudach's message of Mon Apr 11 15:05:09 +0200 2011:
> Thou shalt not have another e-mail client beside of sup -- because sup
> does not change the e-mail sources, and if other mail clients change
> sources, sup won't be able to find the emails any longer.
hmm, that feels like a rather basic ability of a MUA. Or am I mistaken? :/
> There are some workarounds for this, I installed sup on a PC I can
> access via dyndns, run sup there and log in with ssh to read my mail
> from different locations.
yeah, obviously many people use mutt that way, running in a screen. But that
really ruins the whole offline reading thingy for me... ;P
> William Morgan is working on a server - client based solution that will
> solve this problem, but I don't dare to try it yet - being not work in
> progress, but yet in development.
k, I have to admit that I don't quite get yet why we need a distributed
architecture to properly flag our mails (ok, maybe solving that problem is just
a byproduct), but it sure sounds nice. Thunderbird, Claws, mutt et al make do
without tough, me thinks :|
I am just wondering if merging aforementioned branch into master wouldn't make
for a proper, fast and low-effort solution till the server-client refactoring
has been put together and been thorougly tested?
Or am I missing something?
Thanks for your help!
dtk
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-04-11 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 8:08 dtk
2011-04-11 9:22 ` Damien Leone
2011-04-11 21:44 ` dtk
2011-04-12 7:34 ` Damien Leone
2011-04-12 20:41 ` dtk
2011-04-12 21:43 ` Matthieu Rakotojaona
2011-04-12 22:18 ` dtk
2011-04-11 13:05 ` Ruthard Baudach
2011-04-11 21:58 ` dtk [this message]
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=1302558306-sup-4515@minibox \
--to=d.t.k@gmx.de \
--cc=rthrd@web.de \
--cc=sup-talk@rubyforge.org \
/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