Re: [sup-talk] multiple accounts

From: Ruthard Baudach <rthrd@web.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] multiple accounts
Date: Wed, 11 May 2011 14:10:25 +0200	[thread overview]
Message-ID: <1305115211-sup-2468@PrxServer3> (raw)
In-Reply-To: <1305058093-sup-1016@minibox>

> === 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". The main idea of sup is to separate
the physical storage of emails (maildirs, imap folders, mbox and so on)
from the logical structure needed to archive (and access) the emails.

Sup organizes emails by indexing them and searching the index, so it's
completely unimportant where the emails are stored. An email labeled
"inbox" will be shown in the inbox regardless where it is stored, and
the same is true for emails labeled "draft" or "sent".

This means, that, according to sup's philosophy, if you want to
differentiate between private and business mail, you would tag the
threads the mail belongs to with the label "private" resp. "business"
(or even both).

Actually, the mere existence of an :sent_source: is astonishing, as sup
could store sent messages anywhere, it would not matter to the sup user.

This separation of physical storage and logical structure is ingenial,
and the reason why sup is so good organizing emails.

The downside is, that it's almost impossible to use other email clients
beside of sup.

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 or storing sent emails in different sources.
It's just not necessary.

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. But I'm affraid my Ruby is not
good enough to do that.

Ruthard Baudach
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk