From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.187.5 with SMTP id fo5cs225618vdc; Wed, 11 May 2011 05:37:15 -0700 (PDT) Received: by 10.224.214.65 with SMTP id gz1mr7078877qab.277.1305117435183; Wed, 11 May 2011 05:37:15 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id g3si199619qcq.1.2011.05.11.05.37.15; Wed, 11 May 2011 05:37:15 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id DE59815B8035; Wed, 11 May 2011 08:37:14 -0400 (EDT) Received: from fmmailgate03.web.de (fmmailgate03.web.de [217.72.192.234]) by rubyforge.org (Postfix) with ESMTP id D09E618583A2 for ; Wed, 11 May 2011 08:11:11 -0400 (EDT) Received: from smtp05.web.de ( [172.20.4.166]) by fmmailgate03.web.de (Postfix) with ESMTP id B87D918E5B544 for ; Wed, 11 May 2011 14:10:45 +0200 (CEST) Received: from [79.231.120.141] (helo=localhost) by smtp05.web.de with esmtp (WEB.DE 4.110 #2) id 1QK8FZ-0005su-00 for sup-talk@rubyforge.org; Wed, 11 May 2011 14:10:45 +0200 From: Ruthard Baudach To: sup-talk In-reply-to: <1305058093-sup-1016@minibox> References: <1305058093-sup-1016@minibox> Date: Wed, 11 May 2011 14:10:25 +0200 Message-Id: <1305115211-sup-2468@PrxServer3> User-Agent: Sup/git X-Sender: rthrd@web.de X-Provags-ID: V01U2FsdGVkX1+czATloGVyEcCToa7vQ7nAnUvYKcmKs1+2CPVc rWIXE39j6gpPN/AF6lMHA3v/BsfcX2qkAxpsOkmejv2tpbK7Ob wOSwCvtV4= Subject: Re: [sup-talk] multiple accounts X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org > === 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