From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.187.5 with SMTP id fo5cs231528vdc; Wed, 11 May 2011 07:15:50 -0700 (PDT) Received: by 10.224.71.12 with SMTP id f12mr7740877qaj.306.1305123350580; Wed, 11 May 2011 07:15:50 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id m15si361474qcu.33.2011.05.11.07.15.50; Wed, 11 May 2011 07:15:50 -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 4B0FC3C8086; Wed, 11 May 2011 10:15:50 -0400 (EDT) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by rubyforge.org (Postfix) with SMTP id 4DE501858376 for ; Wed, 11 May 2011 09:50:35 -0400 (EDT) Received: (qmail invoked by alias); 11 May 2011 13:50:28 -0000 Received: from hmbg-4d06d0fe.pool.mediaWays.net (EHLO localhost) [77.6.208.254] by mail.gmx.net (mp039) with SMTP; 11 May 2011 15:50:28 +0200 X-Authenticated: #67991182 X-Provags-ID: V01U2FsdGVkX1+dYc8DU1WdwUbb8w18OMFY/P4isowRGxSlc2RfVe eun2nnHCSVILUt From: dtk To: Ruthard Baudach In-reply-to: <1305115211-sup-2468@PrxServer3> References: <1305058093-sup-1016@minibox> <1305115211-sup-2468@PrxServer3> Date: Wed, 11 May 2011 15:50:02 +0200 Message-Id: <1305120470-sup-4951@minibox> User-Agent: Sup/git X-Y-GMX-Trusted: 0 Cc: sup-talk 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 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