Re: [sup-talk] multiple accounts

From: dtk <d.t.k@gmx.de>
To: Ruthard Baudach <rthrd@web.de>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] multiple accounts
Date: Wed, 11 May 2011 15:50:02 +0200	[thread overview]
Message-ID: <1305120470-sup-4951@minibox> (raw)
In-Reply-To: <1305115211-sup-2468@PrxServer3>

Excerpts from Ruthard Baudach's message of Mi Mai 11 14:10:25 +0200 2011:
> > === dtk schrieb am 2011-05-10 22:17: === <
> > Hey folks,
> >
> > I've been test driving sup with my main mail account for some weeks now, and
> > have to admit that my other accounts didn't get too much love during that time,
> > due to the clunky handling of thunderbird. So I'd like to manage my other
> > accounts in sup now as well.
> >
> > I do have a problem, though, since I can't seem to find a way to define seperate
> > :sent_sources per account. And I really don't want to get private/work mails to
> > get mixed up :|
> >
> > Is there a way to define :sent_source: entries per account?
>
> This sounds sort of "unsupish".
I know what you mean. It deals with folders, and sup doesn't. And still I tend
to regard that kind of behavior rather as an extension, an improvement than a
contradiction. Here's why:

> The main idea of sup is to separate
> the physical storage of emails [...]
> from the logical structure needed to archive (and access) the emails.
>
> This separation of physical storage and logical structure is [...] the reason
> why sup is so good organizing emails.
true

> The downside is, that it's almost impossible to use other email clients
> beside of sup.
false. As you say

> Sup organizes emails by indexing them and searching the index, so it's
> completely unimportant where the emails are stored.
So why not store it in a folder that makes it compatible with all those plain
old MUAs (like that webmail client I need when not at my machine or that stupid
GUI MUA my boss forces me to use so he can send me exchange invites)?

> Actually, the mere existence of an :sent_source: is astonishing
I wouldn't call it so much 'astonishing' but rather a well founded compromise,
since first it makes sup compatible with plain old MUAs and second
> sup could store sent messages anywhere, it would not matter to the sup user.

> OK, this is not really helpfull, but might help to understand, why sup
> does not do things which seem to be natural for a MUA - like deleting
> or copying emails
it doesn't!? o_O
I've been using Damien's branch[0] for basically what is the entire time I'm
using sup and it plays really, really nice with all my other MUAs without losing
/any/ of the great innovative advantages of a plain sup, at least as far as I
can tell. So I really fail to see how that would be considered a bad thing ;)

> It's just not necessary.
As you can probably see from my argumentation so far, I'd beg to differ ;P

> One idea, that might help: there is an "sendmail" hook and an
> "before-edit" hook. "before-edit" might be used to automize the creation
> of a bcc to oneself, and the sendmail hook could probably be used
> intercept the message and store it in an additional sent-source before
> calling the actual sendmail command.
yeah, thx for the hints!! Bs as I already stated, not only do I consider that a
rather hacky work around, but I also have other applications in mind plus I would
prefer to just do it the right way^TM ;)

Thanks for your clarifications
dtk


----------
[0]http://rubyforge.org/pipermail/sup-devel/2010-July/000631.html
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk